Data Protection, Snapshots, and Disaster Recovery
Snapshots and replication
Nutanix snapshots are metadata-based and space-efficient. Protection domains group VMs and Volume Groups for local snapshots and remote replication. Files supports file server and share snapshots plus DR replication. Objects protects data with versioning and, in supported releases, bucket replication. Async replication is common; NearSync can tighten RPO for supported workloads.
DR planning
- Define RPO and RTO for each workload before choosing a mechanism.
- Protect the correct object: VM, Volume Group, file server, or bucket.
- Test failover and failback, not just snapshot creation.
- For Files, DNS, VIP, and Active Directory dependencies must exist at the recovery site.
- Snapshots are not backups by themselves; site loss requires a remote copy.
Worked example
A file server must survive a site loss with a one-hour RPO. Local snapshots on the same cluster do not meet that requirement. Configure file server replication to a remote cluster, verify the schedule and remote capacity, and test access after failover. Then confirm that DNS and AD are available at the recovery site so SMB clients can authenticate.
Traps
Do not assume a local snapshot protects against cluster or site loss. Do not mix crash-consistent Volume Group snapshots with application-consistent backups. Do not forget AD and DNS at the DR site. Do not treat replication as a substitute for tested restore procedures.
Key points
- Nutanix snapshots are metadata-based and space-efficient.
- Protection domains drive local snapshots and remote replication.
- Files DR depends on DNS, VIP, and AD at the recovery site.
- Objects uses versioning and supported replication features.
- RPO and RTO determine the protection design.