During a DR test, an administrator activates the SnapMirror destination for an SVM to serve data. When the primary site returns online, the administrator needs to reverse the relationship and resume replication from the new primary site back to the original cluster. Which action should the administrator perform?

During a DR test, an administrator activates the SnapMirror destination for an SVM to serve data. When the primary site returns online, the administrator needs to reverse the relationship and resume replication from the new primary site back to the original cluster. Which action should the administrator perform?

• A. Delete and recreate the SVM replication relationship
• B. Break the SnapMirror relationship and reinitialize the volumes
• C. Perform an SVM SnapMirror resync to reverse the data flow
• D. Disable LIF failover policies before reversing replication

Answer: (A)

Switching replication direction requires redefining which site is the source and which is the destination. SnapMirror relationships are bound to a specific source-destination pairing, so to resume replication from the new primary back to the original cluster you need to remove the existing relationship and establish a new one with the roles swapped. After deleting the old relationship, create a new SnapMirror relationship from the current primary (now the source) to the original cluster (now the destination) and initialize it so data starts flowing in the reverse direction. This approach ensures all state, mappings, and policies align for the reverse transfer and avoids carrying over any mismatched relationship metadata. The other options don’t achieve that clean direction reversal: breaking the relationship and reinitializing volumes would leave the pairing conceptually broken and require additional steps to re-create the relationship; a SnapMirror resync doesn’t reverse direction on its own; and disabling LIF failover policies is unrelated to reversing replication direction.

Switching replication direction requires redefining which site is the source and which is the destination. SnapMirror relationships are bound to a specific source-destination pairing, so to resume replication from the new primary back to the original cluster you need to remove the existing relationship and establish a new one with the roles swapped. After deleting the old relationship, create a new SnapMirror relationship from the current primary (now the source) to the original cluster (now the destination) and initialize it so data starts flowing in the reverse direction. This approach ensures all state, mappings, and policies align for the reverse transfer and avoids carrying over any mismatched relationship metadata.

The other options don’t achieve that clean direction reversal: breaking the relationship and reinitializing volumes would leave the pairing conceptually broken and require additional steps to re-create the relationship; a SnapMirror resync doesn’t reverse direction on its own; and disabling LIF failover policies is unrelated to reversing replication direction.