Continuing our journey through Nutanix’s offerings, this post looks at Nutanix Unified Storage (NUS). In our previous post, we covered the Nutanix Cloud Platform and its role in reshaping infrastructure management. NUS is the part of that platform responsible for enterprise data services.
The short definition: NUS is a software-defined data services platform that consolidates file, object, and block storage into a single platform and is managed through Prism Central. Instead of running separate NAS appliances, object stores, and SAN arrays, the same cluster serves all three.
Applies to: Nutanix Unified Storage as of mid-2026. Feature availability varies by NUS, AOS, and Prism Central release — confirm against your own versions before planning a design.
Three Services, One Platform: NUS is built from three storage services. Each addresses a different access pattern, and most environments end up using more than one.
Nutanix Files: A software-defined, scale-out file service providing SMB and NFS shares. It replaces traditional filer and NAS deployments for departmental shares, home directories, user profiles, and application file data.
Files scales by adding file server VMs rather than replacing a controller pair, which is the practical difference from a traditional appliance: capacity and performance grow in the same increments as the cluster. On the access side, Access-Based Enumeration hides folders that a user has no permission to open, making large departmental shares far easier to navigate.
Nutanix Objects: S3-compatible object storage for unstructured data — backup targets, archives, media repositories, and increasingly analytics and AI training data.
Because the interface is S3, applications that already speak to public cloud object storage generally work without modification. Objects also provide the immutability controls that matter for backup and compliance work, WORM, Object Lock retention dates, and legal hold are distinct mechanisms, and knowing which one applies to a given record is worth settling before you enable any of them.
Nutanix Volumes: Block storage is presented over iSCSI, primarily for consumers that sit outside the AHV cluster — physical servers, or systems that need guest-managed block devices rather than virtual disks.
Volumes enable a Nutanix cluster to host a bare-metal database server alongside its virtualized workloads, often the step that lets an organization retire a legacy SAN. Storage is organized into Volume Groups, which can either be attached directly to an AHV VM or exposed over iSCSI depending on who needs to reach them.
Where Does “Unified” Actually Show Up? Running three services on one platform is only useful if they behave as one system. In practice, the integration shows up in a few specific places.
Tiering between services: Cold data on a file share can be transparently tiered to an object target: Nutanix Objects or an external endpoint such as Amazon S3, Azure Blob Storage, or Wasabi. Users continue to see the file in its original location, while the data itself resides on lower-capacity storage.
Shared Management: All three services are administered through Prism Central rather than three separate consoles, and they draw from the same cluster capacity rather than pre-carved pools.
Namespace Consolidation: More recent NUS releases added a federated namespace for file shares and a global namespace for object stores, so users and applications can access data through a single access point rather than tracking which server or store hosts it.
Data Lens: Nutanix Data Lens provides analytics, auditing, and ransomware defense across data held in Files, Objects, and Amazon S3. It monitors access patterns, flags anomalous behavior against a large and growing set of signatures, and maintains the audit trail you need when investigating an incident.
Two things are worth knowing if you last looked at this a while ago. Data Lens absorbed and replaced what was formerly called File Analytics. And while it began as a SaaS-only service, it can now also be deployed on-premises via the Prism Central Marketplace, which matters for dark sites and organizations with data residency requirements that rule out SaaS.
Data Lens is licensed separately from NUS. Treat it as part of the storage security design rather than an optional extra bolted on later.
Deployment and Licensing: This is the part most overview articles skip, and it is usually the first question that comes up in a real design conversation.
NUS is licensed per usable TiB, in Starter and Pro tiers. A cluster carries a single identity, so Starter and Pro cannot be mixed on the same cluster.
There are two deployment models:
- Mixed mode — applications and storage services share a cluster. NCI or NCP licensing is required alongside the NUS licenses.
- Dedicated mode — the cluster serves storage only, with applications running on external servers. Only NUS licenses are needed.
Two optional add-ons are available, both licensed per usable TiB: Advanced Replication, which adds Metro File Sync and near-sync file server replication and requires Pro; and a Security add-on covering data-at-rest encryption and microsegmentation.
One licensing detail worth remembering, because it surprises people: NUS licenses are not required for Volume Groups when storage is on an NCI Pro or Ultimate cluster. On NCI Starter, Volume Group access is supported only for VMs running inside that cluster.
For replication and disaster recovery, both source and target clusters need NUS licensing sized to the capacity consumed at each site.
Summary: NUS consolidates three storage services — Files for SMB and NFS, Objects for S3, and Volumes for block over iSCSI, into a single Prism Central-managed platform, with Data Lens providing analytics and ransomware defense across them.
The value is consolidation rather than any single feature: one platform to license per usable TiB, one place to administer, and capacity that moves between services rather than sitting stranded in a pre-carved pool. If you are still evaluating, the deployment mode and licensing tier are the decisions to settle first, because they shape everything downstream.
Official Resources
What Do You Think? Are you using all three NUS services, or did you adopt one, usually Files, and leave the others for later?
