I85PREP
⌘ K
Nutanix NCP-CI-Azure study materials
Nutanix NCP-CI-Azure study resources

Nutanix NCP-CI-Azure: Data Protection, Disaster Recovery, and Migration

Nutanix NCP-CI-Azure · Work through your exam, one topic at a time.

All guide sections

Data Protection, Disaster Recovery, and Migration

Domain 4: Data protection, disaster recovery, and migration

This domain tests protection of AHV workloads on NC2, DR between on-premises and Azure, and migration into and out of NC2.

Data protection

  • Nutanix snapshots are local point-in-time copies; protection domains group VMs and apply schedules. Snapshots are not backups-replicate them off-cluster for site loss.
  • Async replication can target another NC2 cluster, another Azure region, or an on-premises cluster. Replication needs network bandwidth, free capacity, and compatible AOS/PC versions.
  • Nutanix Leap orchestrates recovery plans and runbooks across clusters; it depends on Prism Central and tested network mapping.

DR design

  • Define RPO/RTO first. A 15-minute RPO with a 1 Gbps link and 500 GB of change per interval needs roughly 500 GB / 900 s ≈ 570 Mbps sustained, plus headroom.
  • Use ExpressRoute/VPN for replication; protect the replication path with NSGs and private addressing. Test failover and failback, not just replication status.

Migration

  • Nutanix Move is the standard lift-and-shift tool for supported source hypervisors to AHV; install the Move appliance, create a plan, test a VM, then cut over.
  • Do not assume every Azure IaaS VM is a supported Move source; verify source support or rebuild with Azure-native tools.
  • For large datasets, seed physically or use bandwidth throttling to avoid saturating production links.

Worked example

An on-prem VM needs to move to NC2 with a 30-minute cutover. Use Move: deploy the appliance, install guest tools, replicate the VM, test the converted VM on an isolated network, schedule final sync, then power off source and cut over. Keep the source until validation.

Traps

Treating snapshots as offsite backups; using Azure Backup for AHV guest disks; ignoring replication bandwidth; failing to test Leap runbooks; assuming Move supports all sources.