What is a typical DR topology using SnapMirror and SnapVault?

• A. Source ONTAP replicates snapshots to a remote ONTAP system via SnapMirror; backups can be retained on a SnapVault target.
• B. Snapshots are only stored locally at the primary site.
• C. SnapMirror handles backups while SnapVault provides on-site caching.
• D. SnapMirror and SnapVault are not used together in DR.

Answer: (A)

The main idea is using SnapMirror to keep a near-time copy of your data and Snapshot history at a remote site, while SnapVault provides long-term backup copies of those Snapshots. In a DR scenario, you replicate data from the primary ONTAP system to a remote ONTAP system so you can fail over with minimal data loss. At the same time, you back up those Snapshot copies to a SnapVault target so you have retained, recoverable backups over a longer period. This combination gives both quick disaster recovery and durable retention.

This is why the described approach is correct: the primary system sends Snapshot copies to a remote system via SnapMirror, and the backups are retained on a SnapVault target. The other options don’t reflect how SnapMirror and SnapVault work together—SnapMirror isn’t just local, isn’t about on-site caching, and these two tools are indeed used in tandem for DR.