By George Crump
Publication Date: 2026-10-02 14:35:00
virtualization
PARTNER CONTENT: VergeIO says an exit is also an opportunity
Leaving VMware forces a fresh look at every layer of the datacenter, and data protection belongs near the top of that list. Most teams plan to move the backup design across as it stands and rebuild it on the new hypervisor. The better plan uses the exit to raise resiliency and recovery speed, keeps the backup application, and gives each layer the work it does best.
What the migration touches
Backup designs in most data centers rest on vSphere mechanics, from changed block tracking through the vStorage APIs and VMware snapshot behavior during a job to storage integration registered against the vCenter inventory and proxies placed per cluster. Many shops add an orchestration product such as Site Recovery Manager to drive the failover plan. Change the hypervisor and each of those assumptions gets a second look.
Backup vendors have done real work here, and support for the major KVM-based platforms has matured quickly over the past year. The bigger question sits upstream of the backup application. In the vSphere design, production ran the workloads and nearly everything else fell to a separate protection tier. Resilience past a drive failure, fast rollback, replication, site failover, and immutable copies each became another product with its own license, console, and…
