SVM DR relationship fails to update or resync with error No common Snapshot copy found for volume
Applies to
- Ontap 9.x
- SnapMirror
- SVM DR
Issue
- Attempt to
update
/resync
fails to establish SVM DR SnapMirror relationship. - SnapMirror reports no common snapshot copies are found:
Transfer for volume "<volume>" failed. Reason: No common Snapshot copy found between <SVM>:<volume> and <SVM-DR>:<volume>. Delete the volume using the (privilege: advanced) "volume delete -force" command. Then, perform a SnapMirror resync using the "snapmirror resync" command. Execute "snapmirror show -destination-vserver <SVM-DR> -fields last-transfer-error,unhealthy-reason -expand" to check if the constituent volumes have encountered errors.
- Sometimes, the destination volume can not be deleted.
Example:
cluster_dst::*>set advanced
cluster_dst::*> volume delete -vserver SVM1 -volume volume1 -force true
Error: command failed: Volume volume1 in Vserver SVM1 must be offline to be deleted.
cluster_dst::*> volume offline -vserver SVM1 -volume volume1 -force true
Warning: Forcing offline volume volume1 in Vserver SVM1 can potentially disrupt access to files in other volumes.
Do you want to continue? {y|n}: y
vol offline: Error off lining volume "SVM1:volume1". Error while deleting junction.