Updating the source volume
After resynchronizing the source volume, you might want to ensure that all the latest changes are updated on the source volume before activating the source volume.
About this task
You must perform this task from the source cluster.
This command behaves differently for data protection (DP), extended data protection (XDP), and load-sharing (LS) relationships. It performs an incremental transfer.
If the source volume is read-write, take a Snapshot copy on the source volume to capture the current image of the source volume.
Find the most recent Snapshot copy on the destination volume, and validate that the corresponding Snapshot copy is still present on the source.
Incrementally transfer Snapshot copies that are newer than the corresponding Snapshot copy to the destination volume.
For Vserver SnapMirror relationships, the snapmirror update command makes the destination Vserver an up-to-date mirror of the source Vserver. The snapmirror update command must be run from the destination Vserver or cluster.
Example
The following is an example for the destination volume to ensure that all the latest changes are updated on the source volume with unlimited throttle. This optional parameter throttle limits the network bandwidth used for the update transfer. It sets the maximum rate (in Kbytes/sec) at which data can be transferred during the operation. If this parameter is not specified, the throttle value configured for the relationship with the snapmirror create or snapmirror modify command will be used.
Also you can set other parameters, for example, adjust the transfer-priority and enable the storage-efficiency option for efficient data transfer to the destination volume.
Cluster1::> snapmirror update -destination-path vs1_dr:vol1 -throttle unlimited -transfer-
priority normal -enable-storage-efficiency true
Operation is queued: snapmirror update of destination "vs1_dr:vol1".
Cluster1::> snapmirror update -destination-path dvs1.example.com: