Products

AECP Compute Edition (VCFS) vs. Nutanix NCI-C: External Storage and Array Flexibility

Published on by Arcfra Team
Last edited on

Key Takeaway

VCFS gives AECP Compute Edition a VM-native shared datastore with snapshots, clones, thin and thick provisioning, and no per-host controller VM. Nutanix NCI-C uses Volume Groups and delegates storage features to the array partner. For existing SAN deployments, AECP also supports FC and iSCSI, multiple arrays per cluster, and live storage migration across arrays, unlike the Nutanix and Pure FlashArray integration compared here.

VM-Native Datastores vs. Nutanix Volume Groups

Arcfra Enterprise Cloud Platform (AECP) Compute Edition runs the AVE hypervisor on existing Fibre Channel or iSCSI arrays. VCFS turns their LUNs into shared VM datastores, allowing teams to keep their fabric, zoning, and storage runbooks.

VCFS (Virtualization Cluster File System) is Arcfra’s independently developed clustered filesystem, built for virtualization on shared block storage. Each host accesses VM disks through its own FC or iSCSI path. Hosts coordinate through on-disk locks and heartbeats, without a controller VM on every host.

The table below compares VCFS with the Volume Groups storage model used by Nutanix NCI-C.

Arcfra VCFSNutanix NCI-C (Volume Groups)
Designed for
virtualization
Yes, purpose-built
as a VM datastore
No shared datastore at all
Execution contextUser space; upgrades
independently of the
host kernel
Controller VM on every host
LockingNative and stable, designed
for VM disk access
No filesystem-level locking
to provide
Storage featuresNative at the datastore
layer: snapshots, clones,
thin and thick provisioning,
space reclamation
Delegated to the array
partner
Supported scale64 hosts per volumeNot applicable

VCFS provides snapshots, clones, thin and thick provisioning, and space reclamation at the datastore layer. Nutanix NCI-C uses Volume Groups rather than a shared datastore and delegates storage features to the array partner.

With no per-host storage appliance, AECP leaves more host CPU and memory available for workloads. VCFS also runs as a user-space service with a hot-standby monitor that takes over VM I/O if the main service restarts, supporting upgrades independently of the host kernel.

External Storage Support: Nutanix with Pure FlashArray

Nutanix also offers compute-only AHV clusters backed by external arrays. The comparison below covers its Pure Storage FlashArray integration, where protocol support, array mapping, and migration constraints affect how an existing SAN can be reused.

On external storageAECP Compute Edition (VCFS)Nutanix compute-only
with Pure FlashArray
Storage protocolsFibre Channel and iSCSINVMe/TCP only;
no FC or iSCSI
Arrays per clusterMany: one cluster can
use LUNs from several arrays
One external storage
array per compute cluster
Live storage migrationBetween datastores,
including across arrays
No live migration between
storage containers
Cross-cluster live
migration
Yes for compute; storage
too in the next release
Not supported
Synchronous replication
and stretch clusters
Synchronous replication
(RPO=0) with ABDR 2.5
Depends on the array:
some support it, others do
not, subject to Nutanix and
array-vendor co-engineering
Minimum cluster size3 nodes; 2 nodes in the
next release
3 nodes minimum
ManagementOne AOC console for AECP
Compute Edition and
converged clusters
Managed through
Prism Central
NetworkYour existing FC or iSCSI fabric10 GbE end to end, storage
layer-2 adjacent, jumbo frames

The Nutanix limitations above describe the Pure Storage FlashArray integration as documented in December 2025. Other Nutanix external-storage options have their own requirements.

Why Array Flexibility Matters

With AECP Compute Edition, one cluster can use multiple LUNs from several arrays, and one array can serve several clusters. Teams can move a running VM’s disks between arrays during a refresh, a tiering change, or a lease expiry.

The one-to-one cluster-to-array mapping in the Nutanix and Pure FlashArray integration limits that flexibility. Without live storage migration between storage containers or clusters, the storage change becomes a separate migration project.

What This Means for VMware Replacement

For an existing FC or iSCSI SAN, protocol support determines whether the current fabric can carry over. Array mapping and live storage migration then determine how the team handles the next storage refresh.

AECP Compute Edition allows one cluster to use several arrays and supports live storage migration across them. In the Nutanix and Pure FlashArray integration compared here, one array serves each compute cluster and live migration across storage containers is unavailable. For teams managing mixed arrays or upcoming lease expiries, that difference affects how much migration work they must plan after replacing VMware.

To learn more about AECP Compute Edition and the other updates in this release, read the AECP 7.0 launch article.

References

  1. AECP Compute Edition
  2. Arcfra Operation Center
  1. Arcfra Releases AECP 7.0 with AECP Compute Edition, Extending VMware Migration to Existing SANs
  2. AECP 7.0: Elevating One Platform Beyond VMware, Ready for Cloud and AI
  3. Best 4 VMware Alternatives for Enterprises in 2026–2027
  4. Arcfra Virtualization Engine vs. VMware vSphere: Higher Availability with Optimized Performance
About Arcfra

Arcfra simplifies enterprise cloud infrastructure with a full-stack, software-defined platform built for the AI era. We deliver computing, storage, networking, security, Kubernetes, and more — all in one streamlined solution. Supporting VMs, containers, and AI workloads, Arcfra offers future-proof infrastructure trusted by enterprises across e-commerce, finance, and manufacturing. Arcfra is recognized by Gartner as a Representative Vendor in full-stack hyperconverged infrastructure. Learn more at www.arcfra.com.