Re: vfiler dr resync failing

Thought so. I can create a new snapmirror relationship and transfer no problem. There is the error below on the source filer from the dr resync.

Transfer Status: resync to self not allowed

Re: vfiler dr resync failing

It looks like it thinks the mirror is the same volume source and target. Have not seen dr resync do this. Anything weird or different in snapmirror.conf or dns or hosts files pointing to the same controller?

Sent from my iPhone 5

Re: vfiler dr resync failing

I was having EXACTLY the same problem but was able to resolve it.  It had to do with the fact that the simulators all share a common sys_serial_num and sysid which was causing the resync to throw an error about syncing to itself.


I followed the procedure to change the System ID and ran through the setup again and it worked.

This is on Netapp's site but here's a c&p



Setting the System ID

IMPORTANT: You must enter the two following commands BEFORE the Simulate ONTAP node boots up for the first time.

Follow the steps below to change the System ID and System Serial Number for the second node:

1. Once you start the Simulate ONTAP node, the system will begin the boot up process in 10 seconds unless you interrupt it. You will see the following information on the console:

Hit [Enter] to boot immediately, or any other key for command prompt.
Booting in 10 seconds...

2. Press any key other than the Enter key to interrupt the boot process. You will see the following information:

Type '?' for a list of commands, 'help' for more detailed help.

3. Enter the following commands to set the Serial Number and System ID for this node:

SIMLOADER> setenv SYS_SERIAL_NUM 4034389-06-2
SIMLOADER> setenv bootarg.nvram.sysid 4034389062

4. Enter the following commands to verify that the information was saved correctly:

SIMLOADER> printenv bootarg.nvram.sysid

5. Now enter the "boot" command to boot up the node:





Re: vfiler dr resync failing

Thanks you Eric - that information was great and would have sorted the issue I came across, except it broke my SIM as it had already been booted Smiley Happy


Not to worry though, as least I now know why it was failing (the duplicate sysids - never would have figured that otherwise).


Thanks again.