Skip to content

Latest commit

 

History

History
29 lines (25 loc) · 1.72 KB

task_redirecting_clients_to_clustered_ontap_secondary_volume.adoc

File metadata and controls

29 lines (25 loc) · 1.72 KB
Raw
permalink sidebar keywords summary
snapmirror/task_redirecting_clients_to_clustered_ontap_secondary_volume.html
sidebar
ontap, 7, mode, transition, snapmirror, redirect, clients, disaster, clustered, secondary, volume
If you have established a SnapMirror disaster recovery \(DR\) relationship between the 7-Mode primary volume and the clustered Data ONTAP secondary volume and if a disaster occurs at the 7-Mode primary site, you must redirect client access to the clustered Data ONTAP secondary volume.

Redirecting clients to the clustered Data ONTAP secondary volume after a disaster

If you have established a SnapMirror disaster recovery (DR) relationship between the 7-Mode primary volume and the clustered Data ONTAP secondary volume and if a disaster occurs at the 7-Mode primary site, you must redirect client access to the clustered Data ONTAP secondary volume.

Steps

  1. From the secondary cluster, use the snapmirror break command to break the SnapMirror relationship between the 7-Mode primary volume and the clustered Data ONTAP secondary volume.

    sec_cluster::> snapmirror break -destination-path dst_vserver:dst_c_vol

  2. From the secondary cluster, use the snapmirror delete command to delete the SnapMirror relationship between the 7-Mode primary volume and the clustered Data ONTAP secondary volume.

    sec_cluster::> snapmirror delete -destination-path dst_vserver:dst_c_vol

  3. Redirect client access to the clustered Data ONTAP secondary volume.

    For more information about setting up client access in clustered Data ONTAP, see the Clustered Data ONTAP File Access and Protocols Management Guide.