Resynchronize a replication relationship
-
PDF of this doc site
- Cluster administration
-
Volume administration
- Logical storage management with the CLI
-
NAS storage management
- Configure NFS with the CLI
- Manage NFS with the CLI
-
Manage SMB with the CLI
- Manage file access using SMB
- SAN storage management
- Security and data encryption
-
Data protection and disaster recovery
- Data protection with the CLI
Collection of separate PDF docs
Creating your file...
You need to resynchronize a replication relationship after you make a destination volume writeable, after an update fails because a common Snapshot copy does not exist on the source and destination volumes, or if you want to change the replication policy for the relationship.
-
Although resync does not require a baseline transfer, it can be time-consuming. You might want to run the resync in off-peak hours.
-
Volumes that are part of a fan-out or cascade configuration can take longer to resynchronize. It is not uncommon to see the SnapMirror relationship reporting the status "preparing" for an extended time period.
-
Resync the source and destination volumes:
snapmirror resync -source-path SVM:volume|cluster://SVM/volume, … -destination-path SVM:volume|cluster://SVM/volume, … -type DP|XDP -schedule schedule -policy policy
For complete command syntax, see the man page.
You must run this command from the destination SVM or the destination cluster.
The following example resyncs the relationship between the source volume
volA
onsvm1
and the destination volumevolA_dst
onsvm_backup
:cluster_dst::> snapmirror resync -source-path svm1:volA -destination-path svm_backup:volA_dst