Study guide

4.3 Data Locality Mechanics and Intelligent Lifecycle Management (ILM)

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

4.3 Data Locality Mechanics and Intelligent Lifecycle Management (ILM)

Key Takeaways Explain This Topic AI

Data locality ensures that over 90-95% of virtual machine read requests are fulfilled directly by the local Controller VM from local high-performance NVMe/SSD media, bypassing top-of-rack switches entirely.

During write operations, writes are committed to the local CVM's OpLog and synchronously replicated across 1 (RF2) or 2 (RF3) remote CVMs before an acknowledgment is returned to the guest operating system.

Following a VM live migration, vDisk storage remains resident on the source node; the local CVM on the destination host fetches remote blocks on demand during read I/O and caches them locally to re-establish data locality without bulk migration penalties.

Intelligent Lifecycle Management (ILM) uses MapReduce analytics via the Curator service to continuously monitor extent access frequency, demoting cold extents to HDD tiers and promoting hot working sets to NVMe/flash.

Last updated: September 2026

Data Locality Mechanics and Intelligent Lifecycle Management (ILM)

Quick Summary: In traditional virtualization architectures, storage read and write traffic traverses external network switches to reach centralized storage controllers. Nutanix eliminates this network bottleneck through Data Locality —placing virtual machine data blocks directly on the physical storage media of the hypervisor node running that VM. Over 90% of read requests are satisfied locally over a private internal vSwitch. Write operations follow a low-latency synchronous replication pipeline through the local and remote OpLogs before acknowledging completion. When a VM live-migrates to another node, data locality dynamically re-establishes itself on the destination node as active blocks are read. Meanwhile, Intelligent Lifecycle Management (ILM) continuously migrates hot data to flash and demotes cold data to high-capacity storage tiers.

1. The Principle and Architectural Necessity of Data Locality

In conventional SAN and NAS architectures, 100% of storage traffic traverses the physical network. Every time a database performs a 4 KB read or an application writes a log file, the request travels across hypervisor network interfaces, physical Top-of-Rack (ToR) switches, storage array director ports, controller CPUs, and back again. Even with high-speed 25 GbE or 32 Gb Fibre Channel fabrics, network hops introduce packet serialization delays, buffer bloat, and contention during peak workload spikes.

Nutanix solves this through the principle of Data Locality :

Compute and Storage Collocation: In a Nutanix cluster, compute (hypervisor and VMs) and storage (CVM and direct-attached drives) reside inside the exact same physical server node.

Local Read Acceleration: The local Controller VM intercepts storage requests directly from the local hypervisor kernel via an internal private virtual network (vSwitch). Read operations for data residing on the local node are fulfilled directly from local NVMe or SSD media— zero storage traffic traverses the physical ToR switches .

Network Bandwidth Conservation: Because 90% to 95% of typical enterprise storage reads are served locally, physical 10/25/100 GbE network interfaces remain idle and unconstrained, reserving full switch backplane bandwidth exclusively for write replication, cluster management, and VM-to-VM application traffic. Traditional SAN Architecture (100% I/O Across Network Switches)

[VM on Host 1] ===> [Host HBA] ===> [ToR Switch] ===> [SAN Controller] ===> [Disk Shelf]

  • Nutanix HCI Architecture (Read I/O Stays 100% Local)
  • +-------------------------------------------------------------+
  • | Physical Node 1 |
  • | |
  • | [Guest VM] <=== (Internal vSwitch) ===> [Local CVM/Stargate]|
  • | | |
  • | v |
  • | [Local NVMe / SSD / HDD]|
  • +-------------------------------------------------------------+
  • (Zero physical network hops for local reads!)
  • 2. The AOS Write Pipeline: OpLog, Replication, and Extent Store Drain

While read operations benefit immediately from local media, write operations must guarantee data persistence, consistency, and fault tolerance across independent nodes to uphold the configured Redundancy Factor (RF2 or RF3).

Detailed Write Path Workflow

To provide both microsecond write response times and absolute crash consistency, AOS routes writes through a multi-stage distributed pipeline: Guest Virtual Machine

  • |
  • 1. SCSI Write Command
  • v
  • Local CVM (Stargate)
  • |
  • +--------------------+--------------------+
  • | | (Physical 25GbE Network)
  • 2. Write to Local OpLog 3. Synchronous Remote Replicas
  • | |
  • v v
  • [Local NVMe/SSD] [Remote CVM OpLog]
  • | |
  • +--------------------+--------------------+
  • |
  • 4. Remote & Local Ack
  • v
  • 5. Write Acknowledged to VM
  • |
  • (Asynchronous Background Drain via Stargate)
  • v
  • Extent Store (Local Persistent Flash/HDD)

SCSI Write Issuance: The guest virtual machine issues a SCSI write command to its virtual disk.

Local CVM Interception: The local hypervisor routes the write I/O over the internal loopback or private vSwitch directly to the local CVM's Stargate daemon.

Local OpLog Commitment: Stargate analyzes the write size. Random, small block writes (e.g., 4 KB to 32 KB database updates) are written immediately to the local OpLog . The OpLog is a high-speed, persistent write buffer allocated on ultra-fast NVMe or PCIe/SATA SSDs that acts like a distributed battery-backed NVRAM cache.

Synchronous Network Replication: Concurrently with the local write, Stargate replicates the exact same write payload across the physical network to the OpLog of one remote CVM (under RF2) or two remote CVMs (under RF3). Replicas are assigned to remote nodes according to failure domain rules (node-, block-, or rack-awareness).

Write Completion Acknowledgment (ACK): Once both the local OpLog and the remote OpLog(s) confirm the write has been successfully committed to persistent flash, Stargate returns a write completion acknowledgment to the guest VM. The entire synchronous loop typically executes in under 1 millisecond .

Sequential Direct-to-Extent Store Bypass: If the incoming write is a large, contiguous sequential write (e.g., streaming video or large file copy), Stargate intelligently bypasses the OpLog entirely and writes the data directly into the persistent Extent Store , avoiding unnecessary wear and cache pollution on the OpLog.

Asynchronous Extent Store Drain: In the background, Stargate aggregates, coalesces, and compresses writes held in the OpLog, draining them sequentially into the persistent Extent Store on local flash or hybrid media, freeing up OpLog space for incoming bursts.

3. VM Live Migration Dynamics and Restoring Data Locality

In modern virtualized datacenters, virtual machines frequently migrate across physical hosts for resource re-balancing (e.g., via VMware vSphere vMotion or Nutanix AHV Live Migration) or during non-disruptive rolling hypervisor upgrades.

A fundamental question arises: When a VM live-migrates from Node A to Node B, what happens to its multi-terabyte virtual disk?

The Problem with Bulk Storage Migration

If a storage platform attempted to copy an entire 2 TB virtual disk across the network during a live migration, the migration would take hours, saturate the Top-of-Rack network switches, create severe storage latency spikes, and completely negate the agility of dynamic workload mobility.

The Nutanix Solution: Storage Decoupling and On-Demand Locality

Nutanix decouples virtual machine memory migration from storage placement:

Zero Storage Migration at Handoff: During an AHV Live Migration or vMotion, only the VM's active CPU state, registers, and volatile RAM are transferred across the network. The vDisk data remains 100% untouched on Node A's physical drives. The migration finishes in seconds.

Immediate Remote Read State: Immediately following migration, the VM begins executing on Node B. When the VM executes a read request for an existing data block, Node B's local CVM intercepts the request. Recognizing that the requested extent resides on Node A, Node B's CVM requests the block from Node A's CVM over the physical network.

Dynamic Re-Establishment of Locality: Node A's CVM transmits the extent across the network to Node B's CVM. Node B's CVM returns the data to the VM and simultaneously writes a copy of that extent into its local Extent Store on Node B's SSD tier .

100% Local Subsequent Reads: The next time the VM reads that same extent, Node B's CVM serves the request directly from its own local SSD—data locality for that block has been restored!

Immediate Local Writes: Any new write operations issued by the VM on Node B are committed directly to Node B's local OpLog and replicated to a remote node. Node A is no longer involved in new write operations.

Preservation of Cold Data: Extents belonging to the VM that are never read or written (e.g., cold archival logs or dormant operating system binaries) are never pulled across the network. They remain safely on Node A or other cluster nodes, preventing unnecessary network traffic and saving local SSD capacity on Node B. VM Live Migration: Dynamic Locality Re-Establishment

  • Step 1: VM Migrates from Node A to Node B (Storage stays on Node A)
  • +-------------------------------+ +-------------------------------+
  • | Node A | | Node B |
  • | [vDisk Data Stays on Node A] | | [VM Starts Running on Node B] |
  • +-------------------------------+ +-------------------------------+
  • Step 2: VM on Node B Issues Read -> Node B CVM Pulls Block & Caches Locally
  • +-------------------------------+ +-------------------------------+
  • | Node A | | Node B |
  • | [Source Extent] |====>| [Local CVM Fetches Extent] |
  • | | | [Writes Extent to Local SSD] |
  • | | | [Returns Data to Guest VM] |
  • +-------------------------------+ +-------------------------------+
  • Step 3: Subsequent Reads Served 100% Locally from Node B's SSD
  • +-------------------------------+ +-------------------------------+
  • | Node A | | Node B |
  • | [Old Cold Extent Stays Idle] | | [Local CVM Serves Read] <=== |
  • | | | [Local SSD] |
  • +-------------------------------+ +-------------------------------+

Note

Shadow Clones: In scenarios where multiple virtual machines across different nodes read from the same base vDisk (such as Virtual Desktop Infrastructure / VDI linked clones or large container base images), Nutanix automatically activates Shadow Clones . The base vDisk is marked read-only and automatically cached across the local SSD tier of every node hosting a consumer VM, delivering instant local read performance without administrative intervention.

4. Intelligent Lifecycle Management (ILM) and Multi-Tier Storage

Modern hyperconverged infrastructure must balance extreme performance with economical storage density. To achieve this, Nutanix clusters support hybrid storage topologies combining high-performance solid-state media with high-capacity spinning disks or QLC flash.

The Storage Hierarchy Tiers

Tier 0 (Flash Tier): High-speed NVMe PCIe SSDs, SAS SSDs, and SATA SSDs. Delivers tens of thousands of IOPS with sub-millisecond latency.

Tier 1 (HDD / Capacity Tier): High-capacity SATA hard disk drives or dense QLC flash devices. Delivers cost-effective multi-terabyte capacity for archival and infrequently accessed data. +-------------------------------------------------------------------------+

  • | Intelligent Lifecycle Management (ILM) |
  • +-------------------------------------------------------------------------+
  • | Tier 0: Flash Tier (NVMe / SATA SSD) |
  • | +-------------------------------------------------------------------+ |
  • | | [Hot Working Set] [Active Database Tables] [Recently Written] | |
  • | +-------------------------------------------------------------------+ |
  • | ^ | |
  • | | (Promote Hot Data on Read) (Curator Demotes | |
  • | | Cold Extents) v |
  • | +-------------------------------------------------------------------+ |
  • | | [Cold Backups] [Dormant OS Files] [Archival Logs] | |
  • | +-------------------------------------------------------------------+ |
  • | Tier 1: Capacity Tier (High-Density HDD / QLC SSD) |
  • +-------------------------------------------------------------------------+
  • Real-Time vs. Background ILM

Nutanix manages data placement across tiers through two synchronized engines:

Real-Time Tiering (Stargate):

During active I/O, Stargate dynamically determines whether incoming writes should be committed to Tier 0 flash or streamed to capacity storage based on write size and tier utilization thresholds.

If the flash tier crosses a capacity threshold (e.g., 75% full), Stargate begins prioritizing real-time writes and pushes candidate extents to lower tiers.

Background ILM via Curator MapReduce:

Curator is the distributed cluster analytics coordinator that runs periodic background optimization passes across all nodes.

MapReduce Analytics: Curator inspects the Cassandra metadata database, evaluating access timestamps, read frequency, and write age for every extent in the cluster.

Cold Extent Demotion: Extents that have not been accessed within a defined period (e.g., cold data) are queued for background demotion. Stargate transfers these extents from the high-cost NVMe/SSD tier down to the high-capacity HDD tier, ensuring the flash tier retains ample free capacity for active working sets.

Hot Extent Promotion: If a previously cold extent residing in Tier 1 HDD is suddenly accessed by an application, Stargate serves the read request and immediately schedules the extent for promotion back into the Tier 0 flash tier. Subsequent reads and modifications occur at full solid-state speeds.

  • Operational Feature Real-Time Stargate Tiering Curator Background ILM
  • Execution Scope Inline with active I/O transactions Scheduled background batch passes (MapReduce)

Primary Decision Factor I/O size, write pattern, flash capacity threshold Extent temperature (read frequency and recency of access)

Movement Direction Direct-to-flash or direct-to-disk Demotion to HDD; batch organization and dedupe

Impact on Guest Latency Zero (executes inside Stargate I/O loop) Zero (throttled background tasks using idle I/O capacity)

By uniting data locality with automated Intelligent Lifecycle Management, Nutanix AOS guarantees that mission-critical virtual machines experience bare-metal NVMe and SSD performance while organizations benefit from the storage economics of high-density capacity media.

Loading diagram... AOS Synchronous Write Path and Asynchronous Extent Store Drain Pipeline