# #Start Creating the "existing scnario", SRC and DST volumes, a file in the SRC volume and few snapshots that are snapvaulted accross # CLUSTER001::> vol create -vserver SVMTEST001 -volume Gidi_SV_SRC1 -aggregate NODETEST01_AGGR_01 -size 1g -state online -policy default Warning: The export-policy "default" has no rules in it. The volume will therefore be inaccessible. Do you want to continue? {y|n}: y [Job 10216] Job succeeded: Successful CLUSTER001::> vol create -vserver SVMTEST001 -volume Gidi_SV_DST1 -aggregate NODETEST02_AGGR_01 -size 1g -type DP Warning: The export-policy "default" has no rules in it. The volume will therefore be inaccessible. Do you want to continue? {y|n}: y [Job 10217] Job succeeded: Successful CLUSTER001::> snapmirror create -source-path SVMTEST001:Gidi_SV_SRC1 -destination-path SVMTEST001:Gidi_SV_DST1 -type XDP -policy Gidi_SV_Backups_STD_01 Operation succeeded: snapmirror create for the relationship with destination "SVMTEST001:Gidi_SV_DST1". CLUSTER001::> snapmirror initialize -source-path SVMTEST001:Gidi_SV_SRC1 -destination-path SVMTEST001:Gidi_SV_DST1 Operation is queued: snapmirror initialize of destination "SVMTEST001:Gidi_SV_DST1". CLUSTER001::> node run -node NODETEST01 Type 'exit' or 'Ctrl-D' to return to the CLI NODETEST01> priv set diag;wrfile /vol/Gidi_SV_SRC1/test.txt test 123 read: error reading standard input: Interrupted system call NODETEST01*> ls /vol/Gidi_SV_SRC1 . .. test.txt NODETEST01*> CLUSTER001::> snap create Gidi_SV_SRC1 VaultSnap1 -vserver SVMTEST001 CLUSTER001::> snapmirror update -source-path SVMTEST001:Gidi_SV_SRC1 -destination-path SVMTEST001:Gidi_SV_DST1 -source-snapshot VaultSnap1 Operation is queued: snapmirror update of destination "SVMTEST001:Gidi_SV_DST1". CLUSTER001::> snap create Gidi_SV_SRC1 VaultSnap2 -vserver SVMTEST001 CLUSTER001::> snapmirror update -source-path SVMTEST001:Gidi_SV_SRC1 -destination-path SVMTEST001:Gidi_SV_DST1 -source-snapshot VaultSnap2 Operation is queued: snapmirror update of destination "SVMTEST001:Gidi_SV_DST1". CLUSTER001::> snap show -volume Gidi_SV_* ---Blocks--- Vserver Volume Snapshot Size Total% Used% -------- -------- ------------------------------------- -------- ------ ----- SVMTEST001 Gidi_SV_DST1 VaultSnap1 148KB 0% 36% VaultSnap2 80KB 0% 23% Gidi_SV_SRC1 VaultSnap1 80KB 0% 20% VaultSnap2 76KB 0% 19% 4 entries were displayed. # #End Creating the "existing scnario", SRC and DST volumes, a file in the SRC volume and few snapshots that are snapvaulted accross #Start Creating the Volumes on the "new" SV's SRC and DST clusters, And mirror each site from it's old to new cluster using MirrorAllSnapshots and XDP(not DP as in the KB) # CLUSTER001::> vol create -vserver SVMTEST001 -volume Gidi_SV_DST2 -aggregate NODETEST02_AGGR_01 -size 1g -type DP Warning: The export-policy "default" has no rules in it. The volume will therefore be inaccessible. Do you want to continue? {y|n}: y [Job 10218] Job succeeded: Successful CLUSTER001::> vol create -vserver SVMTEST001 -volume Gidi_SV_SRC2 -aggregate NODETEST01_AGGR_01 -size 1g -type DP Warning: The export-policy "default" has no rules in it. The volume will therefore be inaccessible. Do you want to continue? {y|n}: y [Job 10219] Job succeeded: Successful CLUSTER001::> snapmirror create -source-path SVMTEST001:Gidi_SV_SRC1 -destination-path SVMTEST001:Gidi_SV_SRC2 -type XDP -policy MirrorAllSnapshots Operation succeeded: snapmirror create for the relationship with destination "SVMTEST001:Gidi_SV_SRC2". CLUSTER001::> snapmirror create -source-path SVMTEST001:Gidi_SV_DST1 -destination-path SVMTEST001:Gidi_SV_DST2 -type XDP -policy MirrorAllSnapshots Operation succeeded: snapmirror create for the relationship with destination "SVMTEST001:Gidi_SV_DST2". CLUSTER001::> snapmirror initialize -destination-path SVMTEST001:Gidi_SV_*2 Operation is queued: snapmirror initialize of destination "SVMTEST001:Gidi_SV_DST2". Operation is queued: snapmirror initialize of destination "SVMTEST001:Gidi_SV_SRC2". 2 entries were acted on. CLUSTER001::> snapmirror show -source-volume Gidi* Progress Source Destination Mirror Relationship Total Last Path Type Path State Status Progress Healthy Updated ----------- ---- ------------ ------- -------------- --------- ------- -------- SVMTEST001:Gidi_SV_DST1 XDP SVMTEST001:Gidi_SV_DST2 Snapmirrored Idle - true - SVMTEST001:Gidi_SV_SRC1 XDP SVMTEST001:Gidi_SV_SRC2 Snapmirrored Idle - true - SVMTEST001:Gidi_SV_SRC1 XDP SVMTEST001:Gidi_SV_DST1 Snapmirrored Idle - true - 3 entries were displayed. CLUSTER001::> CLUSTER001::> snap show -volume Gidi_SV_* ---Blocks--- Vserver Volume Snapshot Size Total% Used% -------- -------- ------------------------------------- -------- ------ ----- SVMTEST001 Gidi_SV_DST1 VaultSnap1 148KB 0% 37% VaultSnap2 92KB 0% 26% Gidi_SV_DST2 VaultSnap1 140KB 0% 35% VaultSnap2 92KB 0% 26% Gidi_SV_SRC1 VaultSnap1 80KB 0% 19% VaultSnap2 80KB 0% 19% snapmirror.d69754dc-2778-11e6-8a90-00a0981d7e92_2152483868.2018-06-04_210050 76KB 0% 18% Gidi_SV_SRC2 VaultSnap1 140KB 0% 35% VaultSnap2 148KB 0% 37% snapmirror.d69754dc-2778-11e6-8a90-00a0981d7e92_2152483868.2018-06-04_210050 92KB 0% 26% 10 entries were displayed. # #End Creating the Volumes on the "new" SV's SRC and DST clusters, And mirror each site from it's old to new cluster using MirrorAllSnapshots and XDP(not DP as in the KB) #Start once useres ready to move to the new clusters - release/break all 3 relationships to make the new source writable (you can start only with that one if you wish) # CLUSTER001::> snapmirror release -source-path SVMTEST001:Gidi_SV_SRC1 -destination-path SVMTEST001:Gidi_SV_DST1 Warning: Snapshot copies on source volume "SVMTEST001:Gidi_SV_SRC1" generated by SnapMirror for the purpose of mirroring to destination volume "SVMTEST001:Gidi_SV_DST1" will be deleted. Once these Snapshot copies are deleted, it will not be possible to re-establish a mirroring relationship between these two volumes unless there are other common Snapshot copies between the source and the destination volumes. Do you want to continue? {y|n}: y [Job 10220] Job succeeded: SnapMirror Release Succeeded CLUSTER001::> snapmirror break -destination-path SVMTEST001:Gidi_SV_*2 Operation succeeded: snapmirror break for destination "SVMTEST001:Gidi_SV_DST2". Operation succeeded: snapmirror break for destination "SVMTEST001:Gidi_SV_SRC2". 2 entries were acted on. CLUSTER001::> snapmirror release -destination-path SVMTEST001:Gidi_SV_*2 Warning: Snapshot copies on source volume "SVMTEST001:Gidi_SV_DST1" generated by SnapMirror for the purpose of mirroring to destination volume "SVMTEST001:Gidi_SV_DST2" will be deleted. Once these Snapshot copies are deleted, it will not be possible to re-establish a mirroring relationship between these two volumes unless there are other common Snapshot copies between the source and the destination volumes. Do you want to continue? {y|n}: y [Job 10221] Job succeeded: SnapMirror Release Succeeded Warning: Snapshot copies on source volume "SVMTEST001:Gidi_SV_SRC1" generated by SnapMirror for the purpose of mirroring to destination volume "SVMTEST001:Gidi_SV_SRC2" will be deleted. Once these Snapshot copies are deleted, it will not be possible to re-establish a mirroring relationship between these two volumes unless there are other common Snapshot copies between the source and the destination volumes. Do you want to continue? {y|n}: y [Job 10222] Job succeeded: SnapMirror Release Succeeded 2 entries were acted on. CLUSTER001::> snapmirror delete -destination-path SVMTEST001:Gidi_SV_*2 Operation succeeded: snapmirror delete for the relationship with destination "SVMTEST001:Gidi_SV_DST2". Operation succeeded: snapmirror delete for the relationship with destination "SVMTEST001:Gidi_SV_SRC2". 2 entries were acted on. CLUSTER001::> CLUSTER001::> snapmirror show -source-volume Gidi* There are no entries matching your query. # #End once useres ready to move to the new clusters - release/break all 3 relationships to make the new source writable (you can start only with that one if you wish) #Start take the old clusters volumes offline to make sure no one writes to them # CLUSTER001::> vol offline -vserver SVMTEST001 -volume Gidi_SV_ Gidi_SV_DST1 Gidi_SV_DST2 Gidi_SV_SRC1 Gidi_SV_SRC2 CLUSTER001::> vol offline -vserver SVMTEST001 -volume Gidi_SV_SRC1 Volume "SVMTEST001:Gidi_SV_SRC1" is now offline. CLUSTER001::> vol offline -vserver SVMTEST001 -volume Gidi_SV_DST1 Volume "SVMTEST001:Gidi_SV_DST1" is now offline. CLUSTER001::> vol show -volume Gidi_SV_* Vserver Volume Aggregate State Type Size Available Used% --------- ------------ ------------ ---------- ---- ---------- ---------- ----- SVMTEST001 Gidi_SV_DST1 NODETEST02_AGGR_01 offline DP 1GB - - SVMTEST001 Gidi_SV_DST2 NODETEST02_AGGR_01 online RW 1GB 1023MB 0% SVMTEST001 Gidi_SV_SRC1 NODETEST01_AGGR_01 offline RW 1GB - - SVMTEST001 Gidi_SV_SRC2 NODETEST01_AGGR_01 online RW 1GB 1023MB 0% 4 entries were displayed. # #End take the old clusters volumes offline to make sure no one writes to them #Start Create and resync the actual SV realtionship without running baseline on the WAN # CLUSTER001::> snapmirror create -source-path SVMTEST001:Gidi_SV_SRC2 -destination-path SVMTEST001:Gidi_SV_DST2 -type XDP -policy Gidi_SV_Backups_STD_01 Operation succeeded: snapmirror create for the relationship with destination "SVMTEST001:Gidi_SV_DST2". CLUSTER001::> snapmirror resync -source-path SVMTEST001:Gidi_SV_SRC2 -destination-path SVMTEST001:Gidi_SV_DST2 Warning: All data newer than Snapshot copy VaultSnap2 on volume SVMTEST001:Gidi_SV_DST2 will be deleted. Do you want to continue? {y|n}: y Operation is queued: initiate snapmirror resync to destination "SVMTEST001:Gidi_SV_DST2". CLUSTER001::> snapmirror show -source-volume Gidi* Progress Source Destination Mirror Relationship Total Last Path Type Path State Status Progress Healthy Updated ----------- ---- ------------ ------- -------------- --------- ------- -------- SVMTEST001:Gidi_SV_SRC2 XDP SVMTEST001:Gidi_SV_DST2 Snapmirrored Idle - true - # #End Create and resync the actual SV realtionship without running baseline on the WAN #Start verify that all the snaps exists and the file is intact # CLUSTER001::> snap show -volume Gidi_SV_* ---Blocks--- Vserver Volume Snapshot Size Total% Used% -------- -------- ------------------------------------- -------- ------ ----- Info: Unable to get information for Snapshot copies of volume "Gidi_SV_DST1" on Vserver "SVMTEST001". Reason: Volume not online. SVMTEST001 Gidi_SV_DST2 VaultSnap1 140KB 0% 33% VaultSnap2 88KB 0% 24% Info: Unable to get information for Snapshot copies of volume "Gidi_SV_SRC1" on Vserver "SVMTEST001". Reason: Volume not online. Gidi_SV_SRC2 VaultSnap1 140KB 0% 38% VaultSnap2 148KB 0% 39% snapmirror.d69754dc-2778-11e6-8a90-00a0981d7e92_2152483868.2018-06-04_210050 168KB 0% 42% 5 entries were displayed. CLUSTER001::> CLUSTER001::> node run -node NODETEST02 -command "priv set diag;ls /vol/Gidi_SV_DST2/.snapshot" Warning: These diagnostic commands are for use by NetApp personnel only. . .. VaultSnap1 VaultSnap2 CLUSTER001::> node run -node NODETEST02 -command "priv set diag;ls /vol/Gidi_SV_DST2/.snapshot/VaultSnap1" Warning: These diagnostic commands are for use by NetApp personnel only. . .. test.txt # #End verify that all the snaps exists and the file is intact #