Will Your Backup Survive
the VMware Exit?

A Working Demo That Answers the Question

Paul Hodges (VergeIO Field CTO) and Rick Vanover (Veeam VP Product Strategy) run through a complete deployment from scratch — no slides, no pre-built shortcuts. George Crump (CMO) and Aaron Richman (Field Evangelist) round out the panel with context on the real-world decision process and what this means for organizations evaluating their VMware exit. Full live Q&A with all four panelists at the close.

For Infrastructure Admins with Veeam in Production

This session is built for the people who own the backup infrastructure. If you manage Veeam and you are being asked to evaluate VMware alternatives, you need to know whether your existing investment survives the platform change.

The short answer is yes. The longer answer is in this session — specifically how the connection works, how existing backup policies carry forward without modification, and what the full deployment looks like at production scale.

The Backup Standard That Already Supports VergeOS

Veeam built its oVirt driver as a deliberate architectural decision — support for KVM-based platforms through an open standard. That driver is already in your Veeam deployment. VergeOS 26.1.2 implements the oVirt API natively, which means the connection works on day one with no changes on the Veeam side.

The Private Cloud OS Built for the VMware Exit

VergeOS consolidates compute, storage, networking, and security into a single software layer that runs on the x86 hardware already in your data center. No server refresh required. No rip-and-replace. VergeOS 26.1.2 implements the oVirt API natively, connecting enterprise backup platforms through a standard, unmodified driver.