Update a replication relationship manually
Contributors
-
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
-
-
-
Security and data encryption
-
Data protection and disaster recovery
-
![](https://docs.netapp.com/common/images/pdf-zip.png)
Collection of separate PDF docs
Creating your file...
This may take a few minutes. Thanks for your patience.
Your file is ready
You might need to update a replication relationship manually if an update fails because of a network error.
About this task
You must specify the Element source path in the form hostip:/lun/name
, where “lun” is the actual string “lun” and name
is the name of the Element volume.
Steps
-
Update a replication relationship manually:
snapmirror update -source-path hostip:/lun/name -destination-path SVM:volume|cluster://SVM/volume
For complete command syntax, see the man page.
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
0005
at IP address 10.0.0.11 and the destination volumevolA_dst
onsvm_backup
:cluster_src::> snapmirror update -source-path 10.0.0.11:/lun/0005 -destination-path svm_backup:volA_dst