How do SnapRestore and SnapMirror differ in their typical use?

• A. SnapRestore reverts a volume to a snapshot state; SnapMirror asynchronously replicates data to a remote site.
• B. SnapRestore synchronizes across time; SnapMirror backs up data.
• C. SnapRestore clones a new volume; SnapMirror stacks volumes.
• D. SnapRestore is for DR testing; SnapMirror is for backups.

Answer: (D)

The main idea is that these features serve two different data protection tasks: restoring a known good state quickly versus keeping a live copy at a remote site for disaster recovery. SnapRestore reverts a volume to the state captured by a snapshot, which lets you rapidly recover from data loss, corruption, or test a particular point in time. SnapMirror, on the other hand, continuously and asynchronously replicates data to a remote NetApp system, so you have an up-to-date copy offsite for DR readiness and protection. Because the replication is asynchronous, there can be a lag between the primary and the copy, which is acceptable for DR scenarios but not for synchronous hot-failover. The description that SnapRestore is for DR testing and SnapMirror is for backups doesn’t capture the primary functions: restoring to a snapshot versus replicating to a remote site for DR.