2010-02-04 09:00 AM - last edited on 2014-09-26 08:08 PM by alissa
I've tried this on two different versions of the simulator (7.3.2 and 7.2.3).
netapp1 vol2 >> Snapmirrored to netapp2 vol2
Mirror configures okay, and can be quiesced fine (from Destination side). However, when I break the mirror (again from the destination side), and try to resync it fails with the following error:
netapp1> Thu Feb 4 16:57:41 GMT [snapmirror.src.resync.toSelf:error]: SnapMirror cannot resync volume vol2 to itself, operation not permitted.
netapp2> snapmirror resync vol2
Thu Feb 4 16:57:41 GMT [snapmirror.dst.resync.failed:error]: SnapMirror resync of vol2 to netapp1:vol2 : request refused by source filer; check configuration on source.
Snapmirror resynchronization of vol2 to netapp1:vol2 : request refused by source filer; check configuration on source
Host resolution is fine, /etc/snapmirror.conf from dest side is:
netapp2> rdfile /etc/snapmirror.conf
netapp1:vol2 netapp2:vol2 - * * * *
What's more annoying is that a colleague can make this work between two different simulator versions....
2010-02-04 07:36 PM
The destination volume must run under a major version of Data ONTAP the same as or later than that of the SnapMirror source volume; running different minor versions is allowed.
In your case,simulator running with 7.2.3 cannot be used as destination.It can be anything 7.3.x....or your source can be running with any 7.2.x
Can you check if this is the issue.
2010-02-04 10:40 PM
I have seen the same issue... the ONTAP versions are the same since it's the simulator...when I install 2 instances of the same 7.3.2 sim in the linux image, I can mirror from nodeA to nodeB. Breaking the mirror then resyncing back from nodeB to nodeA does not work and gives the same error you saw. ... even when the network is available, and snapmirror.access is set to *. It think I first saw this issue in the 7.3.1 sim...hopefully it gets resolved in a future 7.3.x sim. I haven't tested in the 8.0 7-mode sim yet...that will require 2 VMs since it's a single ontap sim per VM.
2010-02-05 12:26 AM
The ONTAP versions were the same:
7.3.2 >> 7.3.2
and then tested on
7.2.3 >> 7.2.3
Both gave the same errors on a resync command (both from the GUI - console flagged up the errors, and when resync from command line).
2010-02-05 12:27 AM
I've not tried the 8.0 version of the sim, but it seems theres an issue that's easily repeatable.
Just need someone to make sense of the logs now!
Thanks for the replies.
2010-02-05 01:37 AM
Can you have different names for the source and destination volumes and try.
This scenario happens if in snapmirror.conf file source filer and dst filer are the same.
Also,NVRAM no of source and dst host might be the same as you are using simulator.Inthat case you will not hit this issue on a real filer.
2010-02-05 02:53 AM
On 7.3.2 Test Filers were called "netapp3" and "netapp4"
On 7.2.3 Test filers were called "netapp1" and "netapp2"
Both tests failed on a resync with the same error.
2010-02-05 05:54 AM
This is the answer!
I created another pair of filers, this time on 7.3.0 Code. With snapmirror in place and running, the same error occured.
However, when I snapmirrored a pair of volumes (flex vols) with different names it works fine (initialize, quiesce, break, resync)
So to recap:
netapp1:vol1 >>>> netapp2:vol1 (can initialize, quiesce, break, but on resync command "snapmirror resync vol1" it fails)
netapp1:apples >>>>> netapp2:oranges (can initialize, quiesce, break, and resync on "snapmirror resync oranges" command)
Therefore I can only conclude that Snapmirror resync command does something with the volume name, and trips up when it sees the same volume name on the source box.
Is there something in the snapmirror documentation that indicates source and destination volumes need to be called something different for snapmirror to work?
P.S I've tried this on a number of simulator versions now (7.2.3 / 7.3.0 & 7.3.2), and mixed snapmirror between versions (low to high) and it all does the same.
2010-02-06 11:57 PM
Some check list
* Ideally you should keep both the volume in same size.
* Check if you have snapmirror access permitted for the re-sync.
* Look into Snapmirror.log for more details, it will help you to troubleshoot more.
2010-02-07 10:42 PM
Nice that using different vol names worked for you.I don't find any such thing documented for resync to work.Also,we have not seen this issue on real filers.Will update if this is reproduced and something else is known on this.