Source boundary: Intelligent CIO reported the announcement on 2026-10-15. The integration is planned for an upcoming Nutanix Cloud Infrastructure release; this is not a claim that the configuration is generally available today.
Virtualisation Nutanix AHV ONTAP NFS 2026-10-15What was announced
Nutanix plans to let Nutanix Cloud Infrastructure (NCI), including the AHV hypervisor, use external NetApp ONTAP storage over NFS. The stated target is supported NetApp AFF and FAS systems, giving customers a way to change the compute and virtualisation layer without making storage replacement part of the same project.
The architectural change is separation. Nutanix compute and ONTAP capacity can be expanded on different schedules, Prism remains the virtual-machine management surface, and storage teams retain their ONTAP operating model. That is materially different from requiring every migrated workload to land on storage inside a hyperconverged node.
Availability and migration are two separate promises
The publisher says Nutanix Cloud Infrastructure for External Storage is planned for an upcoming NCI release. It does not identify a release number, exact date, support matrix, minimum ONTAP version or licensing bundle. Until those appear in product documentation, teams should treat the design as announced rather than deployable.
Nutanix Move is the identified migration tool for workload moves, network mapping and validation. NetApp and Nutanix are also working toward NetApp Shift Toolkit support for zero-copy virtual-disk conversion. That Shift integration is future work in the announcement, not a currently documented migration path. “Zero-copy” refers to avoiding a full movement of the underlying virtual-disk data; it does not remove application testing, rollback planning or downtime analysis.
Why NFS is the critical design boundary
The announced attachment is NFS, so an existing AFF or FAS deployment is not automatically ready just because it runs ONTAP. Teams need a supported NFS configuration, storage virtual machine and data LIF design, export-policy rules, network capacity and failure-domain plan. The site’s ONTAP NFS reference explains the protocol and SVM boundary; the protocol-selection guide helps distinguish this file-based datastore path from existing SAN designs.
The announcement does not specify NFSv3 versus NFSv4.1, datastore limits, multipathing behavior, Prism provisioning integration, snapshot orchestration or how existing protection workflows surface in Nutanix. VMware-specific ONTAP guidance cannot simply be copied to AHV: the storage may be the same, but the hypervisor, management plug-ins and supported failover behavior are not.
What reuse does—and does not—save
Keeping a supported array can defer a storage refresh and preserve established ONTAP operations. It can also reduce the number of variables in a virtualisation migration. It does not make the storage layer free: controller headroom, NFS throughput, port and switch capacity, support contracts, data protection and operational ownership still belong in the business case.
Independent scaling can be useful when compute demand and capacity demand diverge, but it also restores a dependency between two separately managed platforms. A production design needs one jointly supported compatibility matrix and an escalation path that covers Nutanix, the server and network stack, and NetApp.
A validation plan before adoption
- Support: wait for the named NCI release and confirm the exact AFF/FAS, ONTAP, NFS and firmware combinations in vendor documentation.
- Baseline: record latency, throughput, IOPS, capacity efficiency and controller utilization for representative workloads before migration.
- Network: validate NFS VLANs, MTU end to end, link redundancy, export-policy scope and recovery after LIF, port, switch and controller failures.
- Migration: pilot Nutanix Move separately from any future Shift workflow; measure cutover time, application consistency and rollback rather than treating “zero-copy” as “zero-risk.”
- Protection: prove snapshot, replication, backup and restore procedures from the new operating model, including who owns each recovery action.
- Operations: define the handoff between Prism and ONTAP monitoring and capture a joint vendor escalation path before production cutover.
The announcement creates a credible option for organisations whose storage still has useful life while their virtualisation strategy changes. The decisive evidence will be the release-specific support matrix and measured behavior under failure, migration and recovery—not the architectural diagram alone.
Sources: Intelligent CIO Middle East, 2026-10-15 · iTWire parallel coverage, 2026-10-09 · NetApp ONTAP NFS setup overview