Skip to main content

Make the destination volume writeable

Contributors netapp-lenida netapp-dbagwell netapp-thomi netapp-aherbin
PDFs

You need to make the destination volume writeable before you can serve data from the volume to clients. To serve data from a mirror destination when a source becomes unavailable, stop scheduled transfers to the destination, and then break the SnapMirror relationship to make the destination writable.

About this task

You must perform this task from the destination SVM or the destination cluster.

Steps

You can use System Manager or the ONTAP CLI to make a destination volume writable.

System Manager

  1. Select the protection relationship: click Protection > Relationships, and then click the desired volume name.

  2. Click Menu options icon.

  3. Stop scheduled transfers : click Pause.

  4. Make the destination writable: click Break.

  5. Go to the main Relationships page to verify that the relationship state displays as "broken off".

Next steps

You need to reverse resynchronize the replication relationship after you make a destination volume writeable.

When the disabled source volume is available again, you should reverse resynchronize the relationship again to copy the current data to the original source volume.

CLI

  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.

    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 svm1:volA -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 beginning with ONTAP 9.5).

    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 svm1:volA -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.

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

    cluster_dst::> snapmirror break -source-path svm1:volA -destination-path svm_backup:volA_dst
Next steps

You need to resynchronize the replication relationship after you make a destination volume writeable.

Other ways to do this in ONTAP

To perform these tasks with…​ See this content…​

System Manager Classic (available with ONTAP 9.7 and earlier)

Volume disaster recovery overview