NetApp ONTAP Disaster Recovery & Replication — MetroCluster, SnapMirror & SVM DR
Choosing a DR architecture means trading RPO, RTO, distance, and automation. MetroCluster covers synchronous campus DR, SnapMirror spans async replication with version-flexible topologies, and SVM DR moves whole namespaces. These guides walk the decision, the setup, the failover — and the failback nobody practices.
DR strategy comparison
MetroCluster vs SnapMirror vs SVM DR vs SnapVault: RPO/RTO table and decision flow.
MetroCluster fundamentals
Mediators, FC/IP fabrics, switchover/switchback, stretched vs fabric-attached.
MetroCluster troubleshooting
Triage: mediator quorum, broken disks, switchover failures, forced quorum risk.
SnapMirror async fundamentals
The replication engine under most DR designs: policies, lag, seeding.
SnapMirror active sync
Synchronous active-active replication for zero-RPO clusters.
SVM DR guide
Replicating SVMs across clusters, failover and failback.
Cluster & SVM peering
Peering prerequisites, IPspaces, authentication and troubleshooting.
Volume move & storage mobility
Non-disruptive volume migration between aggregates/clusters.
FlexCache remote cache
Read caching across sites — a cheaper DR/remote-access layer.