SVM disaster recovery is the appropriate NetApp technology because the requirement includes replicating selected volumes and the SVM network configuration to another data center. SnapMirror Synchronous protects individual volumes synchronously but does not replicate the broader SVM configuration as the scenario requires. MetroCluster provides site-level high availability and disaster recovery but is not the selected technology for replicating a subset of volumes plus SVM configuration to another site. SVM peering is only a prerequisite relationship that allows replication; it is not the replication and recovery solution by itself. SVM DR uses SnapMirror to replicate SVM configuration and data so that the destination SVM can be activated during a disaster. Support engineers should recognize phrases such as network configuration, SVM identity, and multiple volumes as indicators of SVM DR rather than single-volume SnapMirror. References/topics: SVM disaster recovery, SnapMirror SVM replication, network configuration replication, DR activation, and multi-volume data protection.
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit