Study guide

12.4 Taking and Managing VM Snapshots in Prism

Nutanix Certified Associate NCA

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Nutanix Cloud Platform & HCI Foundations

1.1 Nutanix NCA Exam Overview, Format, and Objectives 1.2 Hyperconverged Infrastructure (HCI) vs. Traditional 3-Tier Architecture 1.3 The Nutanix Enterprise Cloud Portfolio (NCI, NUS, NCM, EUC, NC2)

2 Chapter 2: Platform Architecture & Distributed Core Services

2.1 Hardware Building Blocks: Nodes, Blocks, Clusters, and Quorum 2.2 Controller VM (CVM) Architecture, Datapath, and Autopathing 2.3 Core Distributed Services: Cassandra, Stargate, Curator, Zookeeper, and Genesis

3 Chapter 3: Prism Administration & Cluster Operations

3.1 Prism Element vs. Prism Central Architecture and Interface Navigation 3.2 Entity Management, Categories, and Role-Based Access Control 3.3 Nutanix Licensing Tiers, Add-ons, and Pulse Telemetry

4 Chapter 4: AOS Distributed Storage Fabric & Data Placement

4.1 Storage Pools, Storage Containers, and vDisk Virtual Architecture 4.2 Redundancy Factor (RF2 vs. RF3), Failure Domains, and Fault Tolerance 4.3 Data Locality Mechanics and Intelligent Lifecycle Management (ILM)

5 Chapter 5: Storage Optimization & Business Continuity

5.1 Storage Efficiency: Compression, Deduplication, and Erasure Coding (EC-X) 5.2 Space-Efficient Redirect-on-Write (ROW) Snapshots and Zero-Byte Clones 5.3 Protection Domains, Consistency Groups, and Disaster Recovery Replication

6 Chapter 6: AHV Virtual Machine Lifecycle Management

6.1 AHV VM Provisioning, Resource Allocation (vCPU, vRAM, Disks), and Boot Types 6.2 Nutanix Image Service and Virtual Machine Templates 6.3 Nutanix Guest Tools (NGT) Architecture, Features, and Deployment 6.4 AHV High Availability (HA), Acropolis Dynamic Scheduling (ADS), and Affinity Rules

7 Chapter 7: AHV Networking & Flow Security Fundamentals

7.1 AHV Virtual Networking Architecture, Open vSwitch (OVS), and Bridges 7.2 Host Network Uplinks, Virtual Switch Configuration, and NIC Bonding Modes 7.3 Virtual Networks: Managed vs. Unmanaged Networks and IPAM 7.4 Nutanix Flow Network Security & Microsegmentation Fundamentals

8 Chapter 8: Cluster Maintenance, Health Monitoring & Support

8.1 Nutanix Cluster Health Monitoring, Alerts, and Events Engine 8.2 Nutanix Cluster Check (NCC) Architecture and Execution 8.3 Life Cycle Manager (LCM) and Rolling Non-Disruptive Upgrades 8.4 Nutanix Support Ecosystem: Diagnostics, Log Gathering, and Support Bundles

9 Chapter 9: Recognizing Nutanix Solutions, Hypervisors & the Product Portfolio

9.1 Supported Hypervisors for NCI and Feature Supportability 9.2 NCI Core Components, Configurations, and Common Deployment Scenarios 9.3 Nutanix Unified Storage: Files, Objects, and Volumes Use Cases 9.4 Nutanix Database Service (NDB) and Database Automation 9.5 Nutanix Kubernetes Platform, Enterprise AI, and End-User Computing

10 Chapter 10: Nutanix Tools — Migration, Deployment, and Validation

10.1 Nutanix Move: Cross-Hypervisor and Cloud Migration 10.2 Foundation and Foundation Central: Imaging and Cluster Deployment 10.3 X-Ray, Collector, and the Objective 1.3 Tool Inventory

11 Chapter 11: Cluster Configuration, Security & Hardware Maintenance

11.1 Cluster Services Configuration: DNS, NTP, SMTP, and SNMP 11.2 Cluster Security Options: Lockdown, Encryption, and the Recycle Bin 11.3 Node Maintenance Mode, Host Shutdown, and Cluster Shutdown 11.4 Cluster Expansion: Node Types and In-Node Expansion Capabilities 11.5 Out-of-Band Management and Remote Console Access

12 Chapter 12: Storage, Network, and Software Administration Tasks

12.1 Volume Groups, vDisk Placement, and Live vDisk Migration 12.2 Network Visualizer, Physical Switch Monitoring, and Network Segmentation 12.3 The Software Compatibility Matrix and Upgrade Path Planning 12.4 Taking and Managing VM Snapshots in Prism 12.5 License Operations: State, Assignment, Reclamation, and Expiry

13 Chapter 13: Performance Analysis, Reporting & Support Operations

13.1 Prism Analysis: Metric Charts, Entity Charts, and Custom Reports 13.2 Custom Alert Policies and Behavioural Anomaly Detection 13.3 Interpreting Workload Performance: CPU Contention, CPU Ready, Memory, and I/O Latency 13.4 Creating Support Cases, Required Documentation, and Insights

12.4 Taking and Managing VM Snapshots in Prism

Key Takeaways Explain This Topic AI

Objective 2.1 lists "take a snapshot" as its own knowledge statement, which means the operational workflow matters, not only the redirect-on-write architecture behind it.

A manual VM snapshot taken from Prism is a local, on-demand point-in-time copy that is not replicated anywhere by itself.

Protection domain snapshots are scheduled and can be replicated to a remote site, which is what makes them a disaster recovery construct rather than a convenience.

Snapshots are crash-consistent by default; application-consistent snapshots require Nutanix Guest Tools to quiesce the guest.

Deleting a snapshot marks it for removal, and the capacity is reclaimed later by Curator rather than instantly.

Last updated: September 2026

12.4 Taking and Managing VM Snapshots in Prism

Objective 2.1 lists "take a snapshot" alongside deploying a VM and configuring its storage and networking, and the blueprint reference list names "Creating a VM Snapshot Manually" and "Deleting a VM Snapshot Manually" specifically. This is an operational item, distinct from the architecture covered in section 5.2.

Two Kinds of Snapshot

The most common confusion in this area is that Nutanix has more than one thing called a snapshot, and they serve different purposes.

  • Local VM snapshot Protection domain snapshot
  • Taken On demand , by an administrator On a schedule , by policy
  • Scope One VM Every VM in the protection domain
  • Replicated off-cluster No Yes , to configured remote sites
  • Purpose A quick undo point before a change Disaster recovery and retention
  • Configured in The VM dashboard Data Protection (section 5.3)

The distinction that gets tested: a local VM snapshot lives on the same cluster as the VM. It is excellent protection against a bad patch or a failed application upgrade, and no protection at all against losing the cluster. Only a protection domain snapshot replicated to a remote site — or a backup product, or Multicloud Snapshot Technology writing to object storage — protects against site loss.

Taking a Snapshot Manually

The workflow in Prism Element is short:

Open the VM dashboard and select the virtual machine.

Choose Take Snapshot .

Give it a meaningful name .

Confirm.

Because snapshots are redirect-on-write, the operation completes in seconds regardless of how large the VM is, and it consumes almost no capacity at the moment it is taken. Capacity grows afterwards as the live VM diverges from the snapshot.

Tip

Name snapshots for their reason, not their date. "pre-payroll-patch-v4.2" tells the next administrator whether it is still needed; "snapshot1" does not. Snapshots named badly are snapshots nobody dares delete, and undeleted snapshots are a common cause of unexplained capacity growth.

The single most common use is the pre-change undo point : take a snapshot immediately before patching, upgrading an application, or changing a configuration, so that reverting is a fast operation rather than a restore.

Crash-Consistent vs. Application-Consistent

This determines whether the snapshot is actually useful for a database.

Crash-consistent is the default. The snapshot captures the vDisks exactly as they are at that instant, with no coordination with the guest. Recovering from it is equivalent to the VM having lost power at that moment. A modern journaling filesystem recovers fine; a database may need to replay or repair, and in-flight transactions held only in memory are lost.

Application-consistent requires Nutanix Guest Tools (section 6.3). NGT quiesces the application before the snapshot is taken — through the VSS provider on Windows, or pre-freeze and post-freeze scripts on Linux — so that buffers are flushed and the on-disk state is transactionally coherent.

Important

If a scenario involves a database and asks for a reliable snapshot, the answer requires NGT. Application consistency is not a checkbox on the snapshot itself; it is a capability the in-guest agent provides.

Restoring and Cloning From a Snapshot

A snapshot gives you two recovery paths:

Restore the VM from the snapshot, returning it to that point in time. The current state is replaced, so this is the destructive option.

Clone a new VM from the snapshot, leaving the original untouched. Because clones are space-efficient (section 5.2), this is cheap, and it is usually the safer choice — you can inspect the recovered copy before deciding what to do with the original.

For file-level recovery, Self-Service Restore lets the VM owner browse a snapshot and recover individual files themselves, which also depends on NGT.

Deleting Snapshots and Reclaiming Capacity

Deleting a snapshot manually is done from the same VM view. What happens next is worth understanding because it explains a frequent support question.

Deletion marks the snapshot for removal ; it does not instantly free space. Curator (section 2.3) subsequently runs its background scan, determines which extents are no longer referenced by any snapshot or live vDisk, and reclaims them. Capacity therefore returns after a delay , not immediately.

Two practical consequences:

Do not expect an instant capacity change after deleting snapshots. If a cluster is critically full, deleting snapshots buys relief on Curator's timetable rather than at once.

Long snapshot chains consume real capacity. Every snapshot pins the extents it references, so a VM with months of forgotten snapshots holds every version of every block that changed in that period.

Snapshots Are Not Backups

Worth stating plainly because it is examinable and because it matters:

  • Risk Local snapshot Replicated PD snapshot Backup product
  • Bad patch or config change Yes Yes Yes
  • Accidental file deletion Yes (with SSR) Yes Yes
  • Whole cluster or site lost No Yes Yes
  • Long-term retention for compliance No Limited Yes

Related but distinct, from section 11.2: the Recycle Bin retains a deleted VM's configuration and vDisks for up to 24 hours. It protects against deleting the VM , whereas a snapshot protects against changing what is inside it .

Loading diagram... Snapshot Types, Consistency, and What Each Protects Against