Network and Storage Protocols

Question about moving a snapmirror destination (Physically and Logically)


Hey all,

I am looking for some advice on how to properly move a SnapMirror destination from one location to another.

Here is some background.

I have a source filer in a remote data center.  I need to snapmirror one very large CIFS volume (10.5 TB) to another remote data center.

Going across the WAN is going to take forever.

What I would like to do is take the disk shelf ( 1 aggregate) from the destination filer and physically connect it to the source filer and do a SnapMirror locally.  This way I can seed all 10.5 TB of data quickly.

Once I have completed the SnapMirror...I want to take the destination shelf back to the destination filer and reconect it.

What is the best procedure for re-syncing the SnapMirror to the new destination filer?   Is this possible?




Theres always SMtape


It depends if you create the aggregate on the destination filer first, if you do then steps are as follows:

1) Remove the shelf from dstfiler and connect to srcfiler

2) On srcfiler run the command disk reassign -s <dstfiler sysid> -d <srcfiler sysid>

3) The destination aggregate and volume should now be visible. If they have the same name as an already existing aggregate/volume then they'll have been marked as foreign and offlined.

4) On srcfiler issue the command `snapmirror initialize -S srcvolume srcfiler:dstvolume`

5) When complete issue `snapmirror break dstvolume` Issue `snap list` on both srcvol & dstvol to confirm a common snapmirror snapshot exists.

6) Remove the shelf from srcfiler and connect to dstfiler

7) On dstfiler run the command disk reassign -s <srcfiler sysid> -d <dstfiler sysid> The destination aggregate and volume should now be visible.

😎 Add an entry into /etc/snapmirror.conf on dstfiler such as `srcfiler:srcvolume dstfiler:dstvolume restart=always 05 * * *` (For snapmirror.conf syntax see

9) On dstfiler issue the command `snapmirror resync dstvolume` You should get a message stating which snapshot will be used as per the  common snapshot in step 5.

10) Once complete resyncs should take place as per schedule in snapmirror.conf or in Protection Manager.

This is from memory so I may have missed a couple of minor things that will be obvious, the basics should be correct though.

NetApp on Discord Image

We're on Discord, are you?

Live Chat, Watch Parties, and More!

Explore Banner

Meet Explore, NetApp’s digital sales platform

Engage digitally throughout the sales process, from product discovery to configuration, and handle all your post-purchase needs.

NetApp Insights to Action
I2A Banner