Which sequence describes implementing two-site disaster recovery using SVM disaster recovery in ONTAP?

Which sequence describes implementing two-site disaster recovery using SVM disaster recovery in ONTAP?

• A. Create a new SVM at the DR site and manually copy data without SnapMirror.
• B. Disable replication, perform a full data reload at DR site, then re-enable replication.
• C. Establish SVM DR with SnapMirror for the SVM, replicate critical data to the DR site, test failover/failback, and coordinate client redirection.
• D. Rebuild the entire cluster at DR site and reconfigure SVM.

Answer: (C)

Two-site disaster recovery with SVM disaster recovery in ONTAP relies on pairing the source SVM with a DR SVM and using SnapMirror to keep data synchronized between sites. Establishing this relationship ensures that the SVM’s volumes and their data at the primary site are mirrored to the DR SVM at the remote site, providing a current copy of the critical data. After the SnapMirror relationship is in place, you replicate the essential data to the DR site so the DR SVM holds the required state and can take over if needed. You then test failover and failback to confirm that the DR path works and that operations can resume at the DR site, followed by coordinating client redirection to the DR SVM’s LIFs or endpoints so users and applications connect to the DR environment during a failover. This sequence avoids manual, ad-hoc data copying, eliminates the need for a full data reload, and sidesteps rebuilding entire clusters, delivering a controlled, repeatable DR workflow. Choosing a path that relies on manual data copying without SnapMirror misses the automated, synchronized replication that SVM DR provides and makes failover less reliable. Opting for a full reload at the DR site or rebuilding the entire cluster introduces lengthy downtimes and complexity, not the streamlined DR capability ONTAP offers with SVM DR and SnapMirror.

Two-site disaster recovery with SVM disaster recovery in ONTAP relies on pairing the source SVM with a DR SVM and using SnapMirror to keep data synchronized between sites. Establishing this relationship ensures that the SVM’s volumes and their data at the primary site are mirrored to the DR SVM at the remote site, providing a current copy of the critical data. After the SnapMirror relationship is in place, you replicate the essential data to the DR site so the DR SVM holds the required state and can take over if needed. You then test failover and failback to confirm that the DR path works and that operations can resume at the DR site, followed by coordinating client redirection to the DR SVM’s LIFs or endpoints so users and applications connect to the DR environment during a failover. This sequence avoids manual, ad-hoc data copying, eliminates the need for a full data reload, and sidesteps rebuilding entire clusters, delivering a controlled, repeatable DR workflow.

Choosing a path that relies on manual data copying without SnapMirror misses the automated, synchronized replication that SVM DR provides and makes failover less reliable. Opting for a full reload at the DR site or rebuilding the entire cluster introduces lengthy downtimes and complexity, not the streamlined DR capability ONTAP offers with SVM DR and SnapMirror.