Exit VMware to Resilient HCI
Integrated data protection, faster recovery, and built-in DR. The exit rebuilds every layer beneath your virtual machines, which makes it the one moment to fix how the data center recovers.
Three Questions Worth Answering Honestly
Answer these for your own data center, not for the vendor slide. The rest of the session follows from what you just admitted.
Resiliency Is Not Protection
These two words get used as if they mean the same thing. They describe opposite sides of a single moment, and the whole architecture conversation turns on which side of it you are standing.
Resiliency Has a Price
Three-Tier
The array does one job extremely well and leaves the other four to products you buy separately. Score it against the five things a recovery plan has to cover.
| Data resiliency | Excellent | The array was built for exactly this. RAID and replication protect the blocks. |
| Server and application resiliency | Limited | An array cannot restart an application on a healthy server. |
| Backup and recovery | Limited | A separate product, on separate hardware, under a separate license and console. |
| Disaster recovery | Data only | Replication moves the blocks. Applications and networking get rebuilt by hand. |
| Backup still required | Yes | Application recovery, archiving, exceeding resiliency, and single file picks. |
First-Generation HCI
The same five rows, a better middle, and an unchanged bottom. HCI fixed the server problem the array could not touch, and it left recovery where it found it.
| Data resiliency | Good | Solid, and tuned by a replication factor rather than a dedicated array. |
| Server and application resiliency | Good | Workloads restart on surviving nodes. This is the real advance over three-tier. |
| Backup and recovery | Limited | Still a separate product sitting beside the cluster with its own infrastructure. |
| Disaster recovery | Data and apps | Better for workloads. Networking stays limited, or it gets expensive. |
| Backup still required | Yes | The same four jobs. Nothing about the bottom row moved. |
Both Still Need a Second Product to Recover
First-generation HCI improved server and application resiliency. It did not change what happens once the limit is exceeded. These four jobs still fall to a backup product that lives outside the platform, on its own hardware, under its own license.
The Private Cloud OS
VergeOS was designed for cloud service providers and optimized for the enterprise private cloud. Compute, storage, networking, and data protection run in one code base, and the same rows answer differently.
| Data resiliency | Excellent | RF2 and RF3, set per workload rather than per array. |
| Server resiliency | Excellent | ioGuardian holds data online when failures exceed RF2 or RF3, and repairs the system. |
| Backup and recovery | Excellent | Unlimited snapshots, no retention limit beyond capacity, instant recovery, file-based recovery. |
| Application recovery | Excellent | A server fails and the applications move on their own. |
| Disaster recovery | Excellent | Virtual data centers encapsulate the entire data center, which is what DR actually needs. |
| Backup product | Optional | Its remaining role is GUI-based single file recovery and long term archiving. |
Data and Server Resiliency
Nothing Gets Restored, Because Nothing Was Lost
RF2 and RF3 protect the data at the workload level. A failing drive changes nothing the application can see. When a whole server goes down, the workloads it was running come up somewhere else on their own.
- RF2 and RF3 set per workload, not per array
- No array console anywhere in the recovery path
- Applications move without an operator in the loop
Pull a Drive. Kill a Server.
The easy end of the demo, and the one that sets the baseline for everything after it.
- Pull a drive from a running node. The application keeps serving.
- Kill a server outright. Watch the workloads land on the survivors.
- No restore job runs. Recovery time never starts counting.
Past the Limit
ioGuardian Picks Up Where RF3 Stops
This is the moment every resiliency conversation avoids. Two drives fail, the redundancy you purchased is spent, and the plan hands the problem to a restore. ioGuardian keeps the data online and repairs the system instead.
- A repair server that engages past RF2 and RF3
- Data stays readable through the failure window
- Recovery time still never starts
Fail Two Drives
The hard version of the same test, run against a workload that stays up on screen.
- Fail a second drive and go straight past the resiliency factor.
- ioGuardian holds the data online while the failure stands.
- The system repairs itself with the workload still running.
Backup and Recovery
Recovery Without a Second Product
Snapshots are unlimited and retention is bounded only by the capacity you have. Recovery runs instantly at the virtual machine level and granularly at the file level, from the same interface that runs the workloads.
- Unlimited snapshots on a schedule you set
- Instant recovery of a deleted virtual machine
- File-based recovery with no restore job to queue
Snapshot, Delete, Recover VM
The destructive part of the demo, run live against the same environment.
- Take a snapshot and walk through the scheduler.
- Delete a virtual machine, then bring it straight back.
Disaster Recovery
DR Is a Data Center Problem, Not a Data Problem
Array replication moves blocks and leaves the applications and the network to be rebuilt by hand at the far site. A virtual data center carries the whole environment across, including its networking, which is the part that decides whether a failover survives contact with production.
- Tenancy encapsulates the entire data center
- Networking crosses with the workloads it serves
- The DR site is a running copy, not a staging area
Fail Over the Data Center
The last and hardest test, and the one the whole session has been building toward.
- Fail over a virtual data center to the second site.
- Applications and their networks arrive together.
- Recover, then fail back, with the workload live throughout.
Resilient on the Hardware You Already Own
RF2 and RF3, ioGuardian, unlimited snapshots, instant recovery, and DR orchestration carry no additional software cost. VergeOS runs on the servers already on your floor, and on refurbished hardware, which is where the economics of the exit actually land.