Nutanix Data Protection: Backup, DR, and ROBO
3.8 million files, restored in under 10 seconds
In 2022 DeepStorage tested HYCU against Nutanix Files. They backed up 3.8 million files. Restore took less than 10 seconds. That number matters because most file backup tools I have evaluated could not even list 3.8 million files in 10 seconds, much less restore them.
The reason it works is not that we are clever. It is that we built for Nutanix from the API level up, instead of adapting a generic VM backup tool to call Nutanix APIs. When we started in 2017, that was a bet. Generic backup vendors were the safer choice and they had the bigger sales teams. We thought customers running Nutanix wanted backup that understood Nutanix. That bet held.
This piece is about what "built for Nutanix" actually changes in practice. Where it matters, where it does not, and where we still have work to do.
What HYCU protects on Nutanix today
| Workload | What we cover |
| Nutanix AHV and ESXi-on-Nutanix VMs | Application-consistent backup using native Nutanix snapshots, granular file recovery, instant VM recovery |
| Nutanix Files | Native CFT integration, 20 million files in under a minute, granular share and folder recovery |
| Nutanix Objects | Auto-discovery of Objects clusters, native S3 API integration, ransomware-resilient WORM target |
| Nutanix Volume Groups | Application-consistent backup including independent volume groups not attached to VMs |
| Nutanix Era databases | Disk-inclusion-aware backup that skips temporary disks Era attaches during operations |
| Nutanix Karbon (NKE) | Kubernetes workloads on Nutanix, including persistent volumes and configuration |
| Nutanix Clusters on AWS / GCP | Same protection model extended to Nutanix running in hyperscaler infrastructure |
Why Cloud Files Tier (CFT) was the unlock for Nutanix Files
Backing up file servers is one of those problems that sounds easier than it is. Traditional file backup is built around walking the filesystem, finding changed files, and copying them. That works at small scale. At enterprise scale, the walk itself becomes the bottleneck. I have watched file backups take 18 hours to complete on environments where the actual changed data was 200GB.
Nutanix Files solves this with Cloud Files Tier, an API-level integration that lets the storage system tell us directly what changed. We do not walk the tree. We ask the API, "what is different since yesterday?" and back up only the answers. The 20-million-files-in-under-a-minute number above is what that architecture produces.
Restore inherits the same advantage. Because we know exactly where each file lives in the backup index, we do not need to scan to find it. We jump to it. That is where the 3.8 million file, 10-second restore number comes from.
The Gaming1 Group case worth understanding
Gaming1 Group runs gaming and betting operations across Europe. They moved to Nutanix to consolidate infrastructure and adopted HYCU for data protection. Their IT infrastructure manager Quentin Gillet summarized why:
"We needed backup that worked at Nutanix speed. With HYCU we have application-consistent backups across our entire Nutanix estate, recovery in minutes when we need it, and one tool to manage everything. The simplicity matters as much as the technical capability."
Our Net Promoter Score across Nutanix customers sits at 91. For context, the technology industry average is closer to 32. The simplicity Quentin describes is what produces that gap.
ROBO on Nutanix: the 'spare tire' approach
If you run Nutanix at the data center and need to extend protection to branch offices, the choice most vendors push is deploying backup infrastructure at every branch. That is expensive and operationally awful. We took a different approach we sometimes call the spare tire model.
Nutanix branches replicate to the data center as part of normal operations. We back up centrally from the replica. The branch consumes zero backup compute, zero backup storage, and zero additional WAN bandwidth beyond replication you are already doing. One management plane covers every branch. Recovery can run at either end.
For Nutanix specifically, this pairs with the 1-or-2-node clusters Nutanix ships for branch use. Cluster gets provisioned at headquarters, shipped to the site, runs autonomously, replicates back. We handle the rest.
Migration between hypervisors, including off VMware
This one has gotten attention since Broadcom acquired VMware in late 2023. We have been doing ESX-to-AHV migration through the same backup-and-restore mechanism for years, originally as a feature for customers consolidating after acquisitions. Since November 2023 it has become the most-discussed feature of HYCU for Nutanix in customer conversations.
The mechanism is simple. Back up a VM from ESXi, restore it to AHV. Format conversion, configuration translation, and recovery orchestration happen in the platform. Done correctly, the workload comes up with application consistency preserved. Done at scale, an entire VMware estate can move to Nutanix over months instead of years, one application at a time, with the same backup platform serving every individual migration.
What I tell teams evaluating data protection for Nutanix
Three questions usually surface what matters. First, does the backup tool use Nutanix native snapshots, or its own snapshot mechanism layered on top? Native snapshots mean zero production impact and no VM stun. Layered snapshots mean both, and the impact grows with VM size.
Second, can it protect Nutanix Files, Objects, Volume Groups, and Era databases natively? Most generic backup tools cover AHV VMs and stop there. The other workload classes get treated as afterthoughts or not at all.
Third, what does the cost model look like when you grow? Vendors that price per-VM or per-socket get expensive fast as Nutanix environments scale up. Capacity-based pricing aligned to source data actually backed up scales more predictably.
Common questions about Nutanix data protection
Why not just use Nutanix's native snapshot capability?
Native snapshots are part of the solution, not the whole solution. They give you point-in-time copies on the same cluster. They do not give you independent retention beyond cluster lifecycle, cross-site protection, application-aware backup for SQL or Oracle running inside VMs, or recovery to a different cluster or cloud. A complete strategy uses Nutanix snapshots as the first protection tier and layers durable backup on top.
How does HYCU compare to Veeam for Nutanix?
Veeam adapted its VMware-era architecture to support AHV. HYCU was built for Nutanix from the start. The practical differences show up in deployment complexity, native API usage, support for Nutanix-specific workloads like Files and Objects, and how the product evolves when Nutanix ships new capabilities. We ship support for new Nutanix releases at GA. Generic tools take quarters to catch up.
Can HYCU protect Nutanix running on AWS or GCP?
Yes. Nutanix Clusters on AWS and Nutanix Clusters on GCP use the same protection model as on-premises Nutanix. Same management plane, same policies, same recovery options. Workloads can be restored across the on-prem-to-cloud boundary or back.
What does HYCU cost compared to backing up Nutanix with native tools plus scripts?
If your environment is small and your team has time to write and maintain scripts, native tools may be sufficient. The economics flip somewhere around 50 VMs or when you need any workload class beyond AHV. The maintenance cost of homegrown solutions is usually invisible until someone leaves the team.
How to evaluate this yourself
HYCU is free for the first 60 days against any Nutanix environment. Real backups, real restores, your actual data. Most customers know within a week whether it fits. The trial download is at hycu.com/trial. If you want to talk through your specific Nutanix architecture before downloading, our SEs do this every day.
Get the newest insights and updates
By submitting, I agree to the HYCU Subscription Agreement , Terms of Usage , and Privacy Policy .