In DR planning, why would you choose SVM-level SnapMirror replication rather than volume-level replication?

In DR planning, why would you choose SVM-level SnapMirror replication rather than volume-level replication?

• A. To replicate only data inside volumes
• B. To replicate at the performance tier level
• C. To replicate the entire SVM including configuration, LIFs, and volumes
• D. To replicate across different clusters only with Metro

Answer: (C)

SVM-level SnapMirror replication is chosen when you want the destination to be a full, ready-to-run replica of the source SVM. It copies not only the data in the volumes but also the SVM’s configuration, including the logical interfaces (LIFs) and other environment settings. That means after failover you have the same network layout, policies, user access, and volume configuration, providing a seamless and quicker disaster recovery. If you use volume-level replication, you’re only copying the data inside each volume. The SVM’s configuration, LIFs, and other SVM-level settings aren’t guaranteed to be replicated in a consistent way, so you’d need to re-create or reconfigure those elements on the destination, which increases recovery time and the risk of misconfiguration. So, for DR readiness where you want a whole, operable replica of the SVM with its network and service configuration intact, replicating at the SVM level is the best approach.

SVM-level SnapMirror replication is chosen when you want the destination to be a full, ready-to-run replica of the source SVM. It copies not only the data in the volumes but also the SVM’s configuration, including the logical interfaces (LIFs) and other environment settings. That means after failover you have the same network layout, policies, user access, and volume configuration, providing a seamless and quicker disaster recovery.

If you use volume-level replication, you’re only copying the data inside each volume. The SVM’s configuration, LIFs, and other SVM-level settings aren’t guaranteed to be replicated in a consistent way, so you’d need to re-create or reconfigure those elements on the destination, which increases recovery time and the risk of misconfiguration.

So, for DR readiness where you want a whole, operable replica of the SVM with its network and service configuration intact, replicating at the SVM level is the best approach.