You have set up a SnapMirror relationship between two SVMs for data protection. The data in the source volume is unavailable due to an event related…

In a disaster recovery scenario where the source SnapMirror volume is corrupted, the primary goal is to failover to the destination volume. The correct procedure involves three main stages. First, you must verify the status of the SnapMirror relationship to understand its current state (e.g., lag time, last successful update). Second, you execute a snapmirror break operation, which severs the replication relationship and transitions the destination volume from a read-only Data Protection (DP) type to a read/write (RW) type. Finally, once the volume is writable, you must configure it for data access by mounting it and ensuring client protocols (NFS/SMB) are correctly set up so users can connect to the data.

A. Perform a SnapMirror quiesce operation.

A quiesce operation is used to pause transfers for planned activities, not for an unplanned disaster recovery where the source is already unavailable.

B. Disable the source volume by taking it offline.

The source volume is already described as unavailable and corrupted. This action is not required to activate the destination volume for client access.

1. NetApp ONTAP Documentation, Data protection, "Break a SnapMirror relationship": This document outlines the procedure for failing over to a destination volume. It states, "You must break the SnapMirror relationship to fail over to the destination volume. Breaking the relationship makes the destination volume read/write and enables clients to access data from the destination volume." This directly supports options E (break) and C (configure for data access).

Source: NetApp ONTAP 9 Documentation Center.

2. NetApp ONTAP Documentation, Data protection, "Displaying the status of SnapMirror relationships": This section details the use of the snapmirror show command. It emphasizes that before performing administrative actions like a break, an administrator should check the relationship's status to ensure it is in an expected state. This supports option D (verify the status).

Source: NetApp ONTAP 9 Documentation Center.

3. TR-4015: SnapMirror Configuration and Best Practices Guide for ONTAP 9.7, Section 5.1 "Disaster Recovery": This technical report describes the disaster recovery workflow. The process explicitly involves breaking the SnapMirror relationship to make the destination volume writable and then re-configuring client access to point to the new active volume. The initial step in any operational procedure is to verify the current state.

Source: NetApp Technical Report TR-4015.