Convert an ONTAP volume DR relationship to an SVM DR relationship
You can convert replication relationships between volumes to a replication relationship between the storage virtual machines (SVMs) that own the volumes, provided that each volume on the source (except the root volume) is being replicated, and each volume on the source (including the root volume) has the same name as the volume on the destination.
Use the volume rename
command when the SnapMirror relationship is idle to rename destination volumes if necessary.
-
From the destination SVM or the destination cluster, run the following command to resync the source and destination volumes:
snapmirror resync -source-path <SVM:volume> -destination-path <SVM:volume> -type DP|XDP -policy <policy>
For complete command syntax, see the man page.
Although resync does not require a baseline transfer, it can be time-consuming. You might want to run the resync in off-peak hours.
The following example resyncs the relationship between the source volume
volA
onsvm1
and the destination volumevolA
onsvm_backup
:cluster_dst::> snapmirror resync -source-path svm1:volA -destination-path svm_backup:volA
-
Create an SVM replication relationship between the source and destination SVMs, as described in Replicating SVM configurations.
You must use the
-identity-preserve true
option of thesnapmirror create
command when you create your replication relationship. -
Stop the destination SVM:
vserver stop -vserver SVM
For complete command syntax, see the man page.
The following example stops the destination SVM
svm_backup
:cluster_dst::> vserver stop svm_backup
-
From the destination SVM or the destination cluster, run the following command to resync the source and destination SVMs:
snapmirror resync -source-path <SVM>: -destination-path <SVM>: -type DP|XDP -policy <policy>
For complete command syntax, see the man page.
You must enter a colon (:) after the SVM name in the
-source-path
and-destination-path
options. See the example below.Although resync does not require a baseline transfer, it can be time-consuming. You might want to run the resync in off-peak hours.
The following example resyncs the relationship between the source SVM
svm1
and the destination SVMsvm_backup
:cluster_dst::> snapmirror resync -source-path svm1: -destination-path svm_backup: