Making the destination volume writeable

You need to make the destination volume writeable before you can serve data from the volume to clients. You can use the snapmirror quiesce command to stop scheduled transfers to the destination, the snapmirror abort command to stop ongoing transfers, and the snapmirror break command to make the destination writeable.

1. Stop scheduled transfers to the destination: snapmirror quiesce -source-path SVM:volume|cluster://SVM/volume, ... -destination-path SVM:volume|cluster://SVM/volume, ...

   For complete command syntax, see the man page.

   Example

   The following example stops scheduled transfers between the source volume volA on svm1 and the destination volume volA_dst on svm_backup :

   cluster_dst::> snapmirror quiesce -source-path <span className="ph">svm1:volA</span> -destination-path svm_backup:volA_dst
   
2. Stop ongoing transfers to the destination: snapmirror abort -source-path SVM:volume|cluster://SVM/volume, ... -destination-path SVM:volume|cluster://SVM/volume, ...

   For complete command syntax, see the man page.

   Note

   This step is not required for SnapMirror Synchronous relationships (supported starting with ONTAP 9.5).

   Example

   The following example stops ongoing transfers between the source volume volA on svm1 and the destination volume volA_dst on svm_backup :

   cluster_dst::> snapmirror abort -source-path <span className="ph">svm1:volA</span> -destination-path svm_backup:volA_dst
   
3. Break the SnapMirror DR relationship: snapmirror break -source-path SVM:volume|cluster://SVM/volume, ... -destination-path SVM:volume|cluster://SVM/volume, ...

   For complete command syntax, see the man page.

   Example

   The following example breaks the relationship between the source volume volA on svm1 and the destination volume volA_dst on svm_backup and the destination volume volA_dst on svm_backup :

   cluster_dst::> snapmirror break -source-path <span className="ph">svm1:volA</span> -destination-path svm_backup:volA_dst