Study guide
12.1 Volume Groups, vDisk Placement, and Live vDisk Migration
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.1 Volume Groups, vDisk Placement, and Live vDisk Migration
Key Takeaways Explain This Topic AI
A volume group is a collection of virtual disks presented over iSCSI, used for shared-disk clusters, bare-metal servers, and VMs that need storage independent of their own configuration.
Volume groups can be directly attached to a guest VM without an in-guest iSCSI initiator, or exposed over the network to external initiators controlled by an access list.
Changing vDisk placement means migrating a virtual disk from one storage container to another so it inherits that container policies for replication factor and data efficiency.
Live vDisk migration across storage containers moves a disk while the VM keeps running, so a policy change no longer requires downtime.
The three storage types Objective 2.3 asks you to identify are the storage pool, the storage container, and the volume group.
Last updated: September 2026
12.1 Volume Groups, vDisk Placement, and Live vDisk Migration
Two knowledge statements land here. Objective 2.1 asks you to "configure storage for VMs" and to "change vDisk placement." Objective 2.3 asks you to "identify the different storage types." Both go beyond the storage-pool-and-container hierarchy covered in section 4.1.
The Storage Types You Must Distinguish
Type What it is Consumed as
Storage pool The aggregate of physical drives across the cluster Not consumed directly; it is the capacity substrate
Storage container A logical, policy-bearing subdivision of the pool Presented to hosts as a datastore; holds vDisks
Volume group A set of vDisks presented over iSCSI Attached to VMs or to external initiators as block devices
The distinction that matters: a normal VM disk lives in a storage container and is attached through the hypervisor. A volume group presents block storage over iSCSI , which is what lets consumers outside the normal VM disk model use Nutanix storage.
Volume Groups
A volume group is a container for one or more virtual disks, presented as an iSCSI target. It is the administrative unit of Nutanix Volumes (section 9.3).
Two ways to attach a volume group
Direct attachment to a VM. Prism can attach a volume group straight to a guest VM. The guest sees additional disks and needs no in-guest iSCSI initiator configuration — the platform handles the connection. This is the simpler path and the one used when a single VM needs storage that should exist independently of the VM's own configuration.
External initiators over the network. The volume group is exposed as an iSCSI target on the network, and consumers connect using their own iSCSI initiator identified by its IQN (iSCSI Qualified Name). An access list on the volume group controls which initiators are permitted to attach. This is how bare-metal physical servers and clustered applications consume Nutanix storage.
When to use a volume group instead of a normal VM disk
Shared-disk clustering. Windows Server Failover Clustering, Oracle RAC, and similar designs require several nodes to attach the same block device. A normal vDisk belongs to one VM; a volume group can be presented to several initiators.
Bare-metal servers. A physical server has no hypervisor to attach a vDisk through, so iSCSI is the route.
Storage whose lifecycle differs from the VM. Data that must survive the VM being rebuilt, or be reattached elsewhere, is cleaner as a volume group.
Large or numerous disks where managing capacity separately from the VM is preferable.
Container persistent volumes , where Kubernetes workloads consume Nutanix block storage.
Tip
Exam discriminator: "more than one host or server must attach the same block device" always points to a volume group. A standard vDisk cannot be shared that way.
Changing vDisk Placement
"Change vDisk placement" means moving a virtual disk from one storage container to another . To understand why anyone would, recall from section 4.1 that policies are set at the container level:
- Replication factor
- Compression
- Deduplication
- Erasure coding
- Reservations
A vDisk inherits the policies of the container it sits in. So if a database VM was provisioned into a container with deduplication enabled and that turns out to be wrong for its workload, the fix is not to change the container — that would affect every other vDisk in it — but to move this vDisk to a container with the right policies.
Common reasons to move a vDisk:
- Reason Move to a container with…
- Workload needs stronger protection RF3 instead of RF2
- Deduplication is costing more than it saves Deduplication disabled
- Cold archival data should be denser Erasure coding enabled
- Data must be separated for compliance or chargeback A dedicated container
- Live migration across storage containers
The capability that makes this practical is live vDisk migration across storage containers : the disk moves while the virtual machine keeps running . Historically, changing a disk's container meant powering off the VM, moving the data, and reattaching — a maintenance window for what is really a policy change.
With live migration:
The administrator initiates the migration in Prism, choosing the target container.
Data is copied to the target container in the background.
I/O continues to be served throughout.
When the copy completes, the vDisk is now governed by the target container's policies.
Important
Do not confuse the three "migrations." VM live migration moves a running VM between hosts — compute. vDisk migration moves a disk between storage containers — policy. Data locality is the automatic background movement of a VM's data to whichever node currently runs it, and requires no administrative action at all.
Configuring Storage for a VM: The Options
Pulling Objective 2.1 together, when adding storage to a VM in Prism you are choosing between:
- Option Result
- Allocate on container A new empty vDisk created in the selected storage container — the normal case
- Clone from image A disk created from an Image Service image (section 6.2)
- Clone from an existing vDisk A space-efficient copy of another disk
- Attach a volume group Block storage presented over iSCSI, shareable and independent of the VM
And after provisioning, the two adjustments that matter: resize the disk, or change its placement by migrating it to a different container.