HCI Data Protection: Backup Architecture
A logistics company in Cebu learned this lesson the hard way. They had a 5-node Nutanix cluster with synchronous replication — excellent HA. Then a ransomware attack encrypted their primary AND replica data within minutes. Their "backup" was the Nutanix replication, which the attackers also hit.
They lost 3 weeks of data. The recovery cost was $200,000 plus reputation damage. The root cause: they confused high availability with backup. HA protects against hardware failure. Backup protects against data corruption, ransomware, and human error.
Here's how to properly architect backup for HCI environments.
HA vs Backup: The Critical Difference
This distinction saves companies millions:
High Availability (HA): If a node fails, VMs restart on surviving nodes. Data is protected through replication. HA handles hardware failures, not data corruption.
Backup: Point-in-time copies of your data that survive even if the entire cluster is destroyed. Backup handles ransomware, accidental deletion, corruption, and site-wide disasters.
You need BOTH. HA for uptime. Backup for data protection. Don't let anyone tell you otherwise.
Backup Architecture for HCI
Here's the backup architecture we deploy for enterprise HCI environments:
Layer 1: Local Snapshots (RPO: 1-4 hours):
Use HCI's built-in snapshot capability (Nutanix Snapshots, Sangfor snapshots, vSphere snapshots).
Schedule hourly snapshots for critical VMs, daily for standard workloads.
Retain 24-48 hours of local snapshots.
This handles: accidental file deletion, VM configuration mistakes.
Layer 2: Backup Server (RPO: 4-24 hours):
Deploy a dedicated backup server (physical or VM) with its own storage.
Use Veeam, Commvault, or Acronis for HCI-aware backup.
Backup to local disk (fast recovery) and replicate to secondary storage.
This handles: VM-level recovery, file-level recovery, application-consistent backups.
Layer 3: Off-site/Cloud Replication (RPO: 24 hours):
Replicate backups to a secondary site or cloud storage (AWS S3, Azure Blob).
This protects against site-wide disasters (fire, flood, theft).
Use immutable storage (S3 Object Lock) to prevent ransomware from encrypting backups.
Layer 4: Air-gapped Backup (RPO: weekly):
Weekly full backup to a removable medium (tape or USB) that's physically disconnected.
Store off-site in a secure location.
This is your last line of defense against catastrophic ransomware.
Backup Strategies by Workload
Not all workloads need the same backup strategy:
Databases (SQL Server, MySQL, PostgreSQL):
Application-consistent snapshots (not just crash-consistent).
Transaction log backups every 15 minutes for critical databases.
Test restore monthly — a backup you can't restore is not a backup.
File Servers:
Daily incremental backups, weekly full backups.
Enable file-level versioning for key directories.
User-deleted files are the #1 recovery request.
Virtual Desktops (VDI):
Golden image backup only — don't back up individual user desktops.
User data should live on file shares or cloud storage, not local desktops.
Email (Exchange, Microsoft 365):
Microsoft 365 has limited native backup. Use Veeam for Microsoft 365 or similar.
Retention: 7 years for compliance, 1 year for operational recovery.
Ransomware Protection for HCI
Ransomware is the #1 data protection threat in 2025. Here's how to protect your HCI environment:
Immutable backups: Use S3 Object Lock or equivalent. Even if attackers access your backup server, they can't encrypt immutable backups.
Network isolation: Backup servers should be on a separate VLAN, accessible only from the backup console.
Least-privilege access: Backup admin credentials should be different from infrastructure admin credentials.
Regular restore testing: Test restoring from backups monthly. If you can't restore, you don't have a backup.
Monitoring: Set alerts for unusual backup job failures, large data deletions, or unauthorized access to backup storage.
The logistics company from the opening story now follows all five. Their annual ransomware test simulates an attack, and they practice restoring from air-gapped backups. It takes them 6 hours to recover — down from 3 weeks.
Backup Sizing and Retention
How much backup storage do you need? Here's our formula:
Daily change rate × retention days × compression ratio = backup storage needed.
Example: 500GB daily change rate × 30 days retention × 0.5 compression = 7.5TB backup storage.
Add 50% buffer for growth and unexpected spikes. For this example: 11.25TB.
For off-site/cloud backup: 30-50% of on-site backup (only keep recent data off-site).
Retention policy recommendations:
Local snapshots: 24-48 hours.
Backup server: 30 days.
Off-site/cloud: 90 days.
Air-gapped: 1 year (rotate media quarterly).
Best Practices
Follow the 3-2-1 rule: 3 copies of data, 2 different media types, 1 off-site.
Use application-consistent snapshots for databases, not just crash-consistent.
Test restores quarterly. A backup you can't restore is just wasted storage.
Separate backup admin from infrastructure admin. Different credentials, different access.
Monitor backup jobs daily. Failed backups that nobody notices are a silent time bomb.
Document your recovery procedures. When ransomware hits at 2am, you don't want to be figuring out recovery.
Conclusion
HCI gives you excellent high availability. But HA is not backup. Every HCI environment needs a layered backup strategy: local snapshots, a dedicated backup server, off-site replication, and air-gapped copies for ransomware protection.
If you're running HCI without proper backup, this is your wake-up call. Start with Layer 1 (snapshots) today. Add Layer 2 (backup server) this week. Layers 3 and 4 should be in place within 30 days.
Want to go deeper? Explore [VMware alternatives](/en/vmware-alternative), [Run infrastructure services](/en/products/run), or [platform comparison](/en/compare).
FAQ
Q: Can I use Nutanix's built-in replication as my only backup?
A: No. Nutanix replication provides HA, not backup. It replicates data corruption and ransomware along with everything else. You need a separate backup solution.
Q: What backup software works best with HCI?
A: Veeam Backup & Replication is the most popular choice. It's HCI-aware, supports Nutanix, VMware, and Sangfor, and integrates with cloud storage for off-site backup.
Q: How long does backup recovery take?
A: For local restore from snapshots: 5-15 minutes. For restore from backup server: 30 minutes to several hours depending on data volume. For off-site restore: hours to days.
Q: Is cloud backup secure enough for sensitive data?
A: Yes, if you use encryption (AES-256 at rest, TLS 1.3 in transit) and immutable storage. For regulated industries, verify your cloud provider meets compliance requirements (SOC 2, ISO 27001).
Sizing and Capacity Planning
Proper sizing is critical for HCI deployments. Start by inventorying your current workloads: CPU cores, memory per VM, storage per VM, and IOPS requirements. A general rule of thumb: each HCI node should run at 60-70% capacity to allow for growth and failover.
For a typical deployment of 50-100 VMs, we recommend starting with 4 nodes, each with: 2x 16-core CPUs, 256GB RAM, 4x 1.92TB NVMe SSDs, and 2x 25GbE NICs. This provides enough resources for most small-to-medium workloads with room to grow.
Migration Strategy from Traditional Infrastructure
Migrating from traditional SAN/NAS-based infrastructure to HCI requires careful planning. We recommend the following approach: First, identify non-critical workloads for initial migration (development, testing, staging environments). Second, use live migration tools (HCX for VMware, Xi Frame for Nutanix) to move VMs with zero downtime.
Third, validate performance on HCI before migrating production workloads. Monitor for 2-4 weeks to ensure IOPS, latency, and throughput meet requirements. Fourth, migrate production workloads in phases, starting with the least critical and progressing to mission-critical systems.
Disaster Recovery with HCI
HCI provides built-in high availability within a cluster, but you still need a disaster recovery plan for site-level failures. Options include: HCI-to-HCI replication between data centers (RPO as low as 5 minutes), cloud-based DR using HCI vendor cloud services, and hybrid DR with cloud object storage for backup.
We typically recommend a 3-2-1 backup strategy: 3 copies of data, on 2 different media types, with 1 copy offsite. With HCI, this translates to: local vSAN replication (copy 1), backup to secondary storage (copy 2), and cloud backup (copy 3).