Update a replication relationship manually
-
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 might need to update a replication relationship manually if an update fails because the source volume has been moved.
SnapMirror aborts any transfers from a moved source volume until you update the replication relationship manually.
Beginning with ONTAP 9.5, SnapMirror Synchronous relationships are supported. Although the source and destination volumes are in sync at all times in these relationships, the view from the secondary cluster is synchronized with the primary only on an hourly basis. If you want to view the point-in-time data at the destination, you should perform a manual update by running the snapmirror update
command.
-
Update a replication relationship manually:
snapmirror update -source-path SVM:volume|cluster://SVM/volume, … -destination-path SVM:volume|cluster://SVM/volume, …
For complete command syntax, see the man page.
You must run this command from the destination SVM or the destination cluster. The command fails if a common Snapshot copy does not exist on the source and destination. Use
snapmirror initialize
to re-initialize the relationship.The following example updates the relationship between the source volume
volA
onsvm1
and the destination volumevolA_dst
onsvm_backup
:cluster_src::> snapmirror update -source-path svm1:volA -destination-path svm_backup:volA_dst