What is SnapMirror primarily used for in ONTAP disaster recovery scenarios?

What is SnapMirror primarily used for in ONTAP disaster recovery scenarios?

• A. Replication of data from a source cluster to a target cluster for DR purposes
• B. Automatic volume resizing during failover
• C. Encrypting data at rest during replication
• D. Managing DNS failover between clusters

Answer: (A)

SnapMirror is about keeping a replica of your data on a separate ONTAP cluster so you can survive a disaster. In DR setups, you want an up-to-date standby copy that you can switch to if the primary site goes down. SnapMirror achieves this by copying data from the source cluster to a target cluster, using snapshot-based replication so changes are transferred and the target stays synchronized. This enables rapid recovery and testing of DR without impacting the production system. Other options describe capabilities that aren’t the primary purpose of SnapMirror: automatic volume resizing during failover isn’t what SnapMirror does; encryption at rest during replication is a separate ONTAP feature; and DNS failover is handled by networking/DNS, not by the data replication mechanism.

SnapMirror is about keeping a replica of your data on a separate ONTAP cluster so you can survive a disaster. In DR setups, you want an up-to-date standby copy that you can switch to if the primary site goes down. SnapMirror achieves this by copying data from the source cluster to a target cluster, using snapshot-based replication so changes are transferred and the target stays synchronized. This enables rapid recovery and testing of DR without impacting the production system.

Other options describe capabilities that aren’t the primary purpose of SnapMirror: automatic volume resizing during failover isn’t what SnapMirror does; encryption at rest during replication is a separate ONTAP feature; and DNS failover is handled by networking/DNS, not by the data replication mechanism.