VergeIOLive Webinar · September 3, 2026 · 2:00 PM ET
Veeam’s Role in a VMware Exit
It’s bigger than you think.
13.1
Veeam Backup & Replication release with native VergeOS support
2
Directions Entire VM Restore runs, onto VergeOS and back out
4
Live demonstration moves
0%
DRAM price increase year over year through 2027
Rick W. Vanover
Product Strategy, Office of the CTO, Veeam Software
Dave Vincent
Technical Solutions Strategist, VergeIO
George Crump
CMO, VergeIO
The question that filled the registration list
You’ve decided to leave VMware but you want to maintain your existing Veeam investment. What VMware alternatives are supported by Veeam, and how can Veeam help you migrate to them?
Why the project stalls
Two projects, not one
- The licensing math was settled more than a year ago
- Replacing a platform is one project with a defined scope
- Replacing the backup around it is a second project, same time, same production workloads
- Two vendors, two migration plans, two sets of recovery assumptions
The backup administrator holds veto power. That veto is where most evaluations died.
What changed on July 29
A fully supported hypervisor in Veeam Backup & Replication 13.1
VergeOS “has been integrated into the Veeam Universal Hypervisor API and is now a fully supported hypervisor in Veeam Backup & Replication.”
Veeam Backup & Replication 13.1, What’s New- Add Server › Virtualization Platforms › VergeOS
- VergeOS one of the first platforms through the API
The Veeam view
Why Veeam built the Universal Hypervisor API
- The platform landscape after Broadcom
- How many hypervisors a customer might reasonably run
- A first-party API instead of one-off drivers
- What a platform vendor has to do to get through it
The Veeam view
“Works with” versus supported
- A support ticket has a place to go
- The plug-in ships in the product
- The release notes carry the platform
- What happens when a backup admin calls Veeam support about a VergeOS job
The Veeam view
What stays the same
- The product and the licensing
- The policies defended in audits and the retention schedules
- The staff who know the console
- The platform underneath changes. The data protection decision does not reopen
What to watch for when VergeOS gets added to the console.
Live demonstration · Dave Vincent
Four moves, one console
Move one
Add the platform
- Add Server, Virtualization Platforms, VergeOS
- One package turned on at the VergeOS end
Move two
Protect a workload
- Backup job with Changed Block Tracking
- File level restore into the running guest
Move three
Onto VergeOS
- Entire VM Restore from another platform’s backup
- The migration motion
Move four
Back out
- Instant Recovery from a VergeOS backup to another hypervisor
- Same console, minutes later
Veeam Backup & Replication 13.1. VergeOS 26.1.7 or later. Rick stays on for the Veeam side.
What the demo proved
Same console. No second project.
Stayed
The product and the license
Veeam, as deployed today, adds a platform.
Stayed
The policies and retention
The schedules defended in audits keep running.
Stayed
The people
The team that knows the console keeps operating it.
The platform underneath changed. Nothing else did.
The merit case
The hardware math has not moved
0%
DRAM price increase year over year through 2027
55–60%
NAND flash contract price increase, Q1 2026
DDR4
Working life extended by global inline deduplication
- Most VMware alternatives force a server refresh alongside the platform change
- A software decision becomes a capital request in the worst pricing cycle in a decade
- VergeOS runs on the servers already carrying production load
The merit case
Five products. One code base.
0
Infrastructure products consolidated into a single software layer on standard servers
- Networking
- Virtualization
- Storage
- Data Resiliency
- Management
The reason to act now
The two-way door
- Entire VM Restore runs both directions
- The tool that carried the workload on is the tool that would carry it off
- A reversible decision gets evaluated on merit
- An irreversible one gets evaluated on fear, and fear favors the incumbent
Only one platform on Veeam’s list runs on the servers you already own.
It’s bigger than you think
Beyond the VMware exit
- The same restore path brings in everything Veeam protects
- A VMware exit is the first consolidation, not the only one
Hypervisors
VMware vSphere, Hyper-V, Nutanix AHV, Proxmox VE and other KVM platforms
Public cloud
AWS, Azure, Google Cloud
Physical
Servers protected by Veeam Agent
Destination
VergeOS
One code base. Compute, storage, networking, and Data Resiliency on the servers already in the rack.
Entire VM Restore into VergeOS, per Veeam’s 13.1 documentation.
Two layers, one environment
Where the layers divide
VergeOS
Continuous availability
- Absorb and self-heal during disruption
- Virtual Data Centers, sites, full environments
- Short-term operational checkpoints
- Node loss, site disruption, environment rollback
Veeam
Granular recovery
- Restore after disruption
- Files, database objects, application items, individual VMs
- Long-term, compliance-driven retention
- User error, corruption, deletion, compliance request
The layers answer different failures. Neither replaces the other.
Two layers, one environment
Data Resiliency inside VergeOS
Both have a role. Veeam Instant Recovery is how you recover a VergeOS workload onto another platform, vSphere, Hyper-V, or Nutanix AHV. VergeOS snapshots and ioGuardian are how you recover inside VergeOS, inline, without stopping the VM.
- Snapshots as often as you want. Recovery point in minutes, set by frequency
- ioGuardian holds a third copy and delivers missing segments inline to a running VM
- Replaced drives rebuild automatically
Open question and answer
Your questions
Veeam
Rick W. Vanover
Product Strategy, Office of the CTO
VergeIO
Dave Vincent
Technical Solutions Strategist
VergeIO
George Crump
Chief Marketing Officer
The recording and the slides go to every registrant.
The close
The last open question in a VMware exit has been answered.
One
Officially supported
VergeOS is a selectable platform in Veeam Backup & Replication 13.1.
Two
Your Veeam stays
Product, licensing, policies, and people, unchanged.
Three
Infrastructure-wide consolidation
Not just VMware. Hyper-V, KVM, public cloud, and physical servers onto one code base.