Leave VMware. Keep Veeam.
VergeOS is now a fully supported hypervisor in Veeam Backup & Replication 13.1, delivered through the Veeam Universal Hypervisor API. Keep the backup product, the licensing, the policies, and the people who run them. Change only the platform underneath.
13.1
Veeam Backup & Replication release with native VergeOS support, shipped July 29, 2026
5
Infrastructure products VergeOS consolidates into one code base on standard servers
93 to 98%
Rise in conventional DRAM contract prices, quarter over quarter, Q1 2026 (TrendForce)
Backup continuity is what stalls a VMware exit
The backup layer stays exactly where it is. Only the platform underneath changes.
Two projects, two vendors, two recovery plans
What stops the VMware Exit project is operational risk, and data protection sits at the center of it. Replacing a virtualization platform is one project with a defined scope. Replacing the platform and the backup infrastructure wrapped around it is two projects running at the same time against production workloads, with two vendors, two migration plans, and two sets of recovery assumptions to prove again.
The backup team holds veto power over that plan, and until now they had every reason to use it.
One project. The backup layer stays.
Veeam Backup & Replication 13.1 takes the second project off the plan. VergeOS appears under Virtualization Platforms in the Veeam console and is added as a VergeOS Manager, the same way any other supported platform gets added. In Veeam’s own words, VergeOS “has been integrated into the Veeam Universal Hypervisor API and is now a fully supported hypervisor in Veeam Backup & Replication.”
A support ticket has a place to go. The backup administrator becomes an ally in the evaluation, and the decision returns to the merits of the platform.
Three things official support changes
Supported, in the product, with a name on it. Here is what that buys a team planning a platform change.
Officially supported, not merely compatible
VergeOS is integrated into the Veeam Universal Hypervisor API and Veeam ships it in the product. The distinction matters to a backup administrator who has been burned by a vendor’s “works with” claim. Supported means the route from evaluation to protected production workload runs through an interface the customer already operates.
Your backup investment survives the migration
A customer running Veeam today keeps the product, the licensing, the retention schedules they defend in audits, and the operational knowledge. The existing deployment adds a platform. The platform change stops being a data protection decision.
Veeam moves workloads in both directions
Entire VM Restore brings machines into VergeOS from any supported hypervisor, from AWS, Azure, or GCP, and from Veeam Agent backups of physical servers. The same feature moves VergeOS backups out to any other supported hypervisor or cloud target. The tool that moves workloads onto VergeOS is the tool that would move them off, so the decision gets evaluated on merit rather than on fear of being locked in.
Two layers of protection, one decision
VergeOS delivers Data Resiliency at infrastructure scale as a core function. Veeam delivers workload and application recovery. The layers answer different failures, and organizations running both get depth neither produces alone.
VergeOS Data Resiliency
Availability and large-scale recovery. VergeOS absorbs node loss, replicates across sites through ioReplicate, holds immutable checkpoints through ioFortify, and rolls an entire Virtual Data Center back in minutes. ioGuardian sits outside the production instance as a third copy and delivers missing data segments inline to a VM that keeps running on production hardware. Recovery point is minutes, set by snapshot frequency.
Veeam Backup & Replication
Granular recovery and long-term retention. Changed Block Tracking backups, file-level restore into a running guest, application-item recovery through Veeam Explorers for SQL Server, Exchange, SharePoint, Active Directory, and Oracle, and the seven-year copy that satisfies the auditor. Entire VM Restore in both directions, and Instant Recovery of a VergeOS workload onto vSphere, Hyper-V, or Nutanix AHV.
Both have a role. Veeam Instant Recovery is how you recover a VergeOS workload onto another platform. VergeOS snapshots and ioGuardian are how you recover inside VergeOS, inline, without stopping the VM.
From console to first backup in four steps
On the Veeam side it is a native platform selection. On the VergeOS side one package gets turned on.
Prepare VergeOS
Run VergeOS 26.1.7 or later. 26.1.8 is the current production release. Turn on the oVirt-engine package, listed as oVirt API compatibility, through system updates. For tenant protection, extend the provider’s External network into each tenant you plan to protect.
Add the platform in Veeam
On Veeam Backup & Replication 13.1 or later, choose Add Server, then Virtualization Platforms, then VergeOS, and add the system as a VergeOS Manager. Each tenant is added as its own VergeOS Manager with its own engine ID, so jobs, retention, and reporting stay separated.
Configure repositories and workers
VergeOS is a source platform in the Veeam model. Configure repositories separately as you would for any platform. A hardened Linux repository VM can run on VergeOS. Veeam deploys Workers, auxiliary Linux VMs, onto the protected VergeOS system to move data.
Run the first job and prove the restore
Run a backup job with Changed Block Tracking, then a file-level restore into a running guest. For application-aware backup, prepare the guest with the Veeam Deployment Toolkit and Veeam installs its own agent during the first job. Then rehearse Entire VM Restore into VergeOS from another platform.
Supported, in the product, with a name on it
Official support shipped in Veeam Backup & Replication 13.1, initial release build 13.1.0.411, on July 29, 2026. The Veeam Plug-in for Verge OS, version 1.0, build 13.1.0.191, released the same day and is bundled with 13.1. VergeOS and Platform9 are the first two platforms integrated through the Universal Hypervisor API.
“Organizations modernizing their virtual infrastructure need confidence that their data remains resilient wherever workloads run. VergeOS support through the Veeam Universal Hypervisor API helps customers protect and recover VergeOS workloads with Veeam Backup & Replication, supporting freedom of choice while maintaining trusted recovery operations.”
Rick W. Vanover, Product Strategy, Office of the CTO, Veeam Software
| Capability | Detail |
|---|---|
| Backup jobs | Changed Block Tracking for incremental processing |
| Backup Scan | Health verification, Threat Hunter, YARA content scanning |
| Entire VM Restore into VergeOS | From any supported hypervisor, AWS, Azure, GCP, or a Veeam Agent physical server backup |
| Entire VM Restore out of VergeOS | To any other supported hypervisor or cloud target |
| Instant Recovery from VergeOS | To vSphere, Hyper-V, Nutanix AHV. Proxmox VE experimental |
| File Level Restore | Direct guest file restore, no full VM recovery needed |
| Disk Mount and Export | Read-only mount, Windows and Linux. Export to VHD, VHDX, VMDK |
| Application-aware backup | Once the guest is prepared with the Veeam Deployment Toolkit, Windows and Linux |
| Application-item restore | SQL Server, Exchange, SharePoint, Active Directory, Oracle through Veeam Explorers |
| Scope | Provider system and individual tenants, each as its own VergeOS Manager |
Five questions to settle before the first backup job
The answers a backup administrator needs before VergeOS goes into the evaluation plan.
Which versions do I need?
Veeam Backup & Replication 13.1 or later, initial release build 13.1.0.411, current patch 13.1.1.18. VergeOS 26.1.7 or later with the oVirt-engine package turned on. VergeOS 26.1.8 is current production. Support is native in Veeam, so there is no driver to configure. On the VergeOS side, one package gets turned on.
What does Veeam protect on VergeOS?
Backup jobs with Changed Block Tracking, Backup Scan with health verification and Threat Hunter and YARA content scanning, and application-aware backup once the guest has been prepared with the Veeam Deployment Toolkit. Without that preparation, the platform-level backup is crash-consistent, so name which case you are describing in an evaluation plan.
Which restore paths run, and in which direction?
File-level restore, read-only Disk Mount, export to VHD, VHDX, and VMDK, and application-item restore through Veeam Explorers. Entire VM Restore runs in both directions, into VergeOS from any supported platform and out to any other. Instant Recovery runs from a VergeOS backup to vSphere, Hyper-V, or Nutanix AHV, with Proxmox VE experimental. Recovery inside VergeOS is a Data Resiliency function, through snapshots and ioGuardian.
How does a multi-tenant environment get protected?
Veeam supports both the provider system and individual tenants. Each tenant is added as its own VergeOS Manager with its own engine ID, so jobs, retention, and reporting stay separated per tenant. The provider’s External network must be extended into each protected tenant.
What operational constraints apply?
These come from Veeam’s Universal Hypervisor API documentation and none is a deal-breaker. IPv6 is not supported. The Universal Hypervisor Manager needs a direct IP connection to the backup server, so connections through a NAT gateway do not work. Deduplication is on and block size is fixed at 1 MB. One backup job runs per VM at a time, and a VM being restored cannot be backed up concurrently. Backup encryption is set at the repository level. Backups cannot be stored directly in a Veeam Cloud Connect repository, though Backup Copy jobs can place copies there.
Replication jobs and Continuous Data Protection are VergeOS functions, delivered through ioReplicate and checkpoints, rather than Veeam functions on this platform.
Veeam’s Role in a VMware Exit
Sixty minutes, most of it live demonstration. Four moves in one console, then open questions.
Rick Vanover from Veeam’s Office of the CTO explains what the Universal Hypervisor API changes for a customer. Dave Vincent then adds VergeOS to a Veeam console, runs a first backup, and recovers a workload, with both presenters staying on for open questions.
Thursday, September 3, 2026
2:00 PM ET / 1:00 PM CT / 11:00 AM PT | No cost | Recording sent to all registrants
What you will see
- Add VergeOS to Veeam under Virtualization Platforms, as a VergeOS Manager
- A backup job with Changed Block Tracking, then a file-level restore into a running guest
- Entire VM Restore bringing a workload into VergeOS from another platform
- Instant Recovery of a VergeOS backup out to vSphere, Hyper-V, or Nutanix AHV
- Open question and answer on prerequisites, restore paths, and the two-layer model
Go deeper
Press release
VergeIO Announces VergeOS Support in Veeam Backup & Replication. The announcement, the Veeam and VergeIO quotes, and the availability statement.
Read the releaseBlog
Beyond the VMware Exit: Consolidate Every Platform onto VergeOS with Veeam. How Entire VM Restore turns the backup console into a consolidation console.
Read the blogIntegration documentation
VergeOS Veeam integration guide. Prerequisites, the oVirt-engine package, worker networking, and tenant configuration.
Open the docsQuestions a backup administrator asks first
Is VergeOS certified by Veeam?
VergeOS is officially supported in Veeam Backup & Replication 13.1. Veeam’s own description is that VergeOS “has been integrated into the Veeam Universal Hypervisor API and is now a fully supported hypervisor in Veeam Backup & Replication.” That is the language to use.
Do I need a new backup product or new licenses?
The existing Veeam deployment adds a platform. The product, the licensing, the policies, and the retention schedules stay as they are. The staff who know the console keep running it.
What is different from the earlier oVirt-driver path?
In April 2026 VergeOS implemented the oVirt API and Veeam protected VergeOS workloads through its existing oVirt KVM driver. Veeam now recognizes VergeOS on its own terms as a selectable platform in the console. The oVirt-engine package remains the component that gets turned on in VergeOS, and Veeam connects to it through the Universal Hypervisor API plug-in.
Can I use Veeam to migrate onto VergeOS?
Yes. Entire VM Restore brings a protected machine into VergeOS from any hypervisor Veeam supports, from AWS, Azure, or GCP, and from a physical server running Veeam Agent. Each move is a restore job the backup team has already rehearsed.
Does Veeam Instant Recovery work with VergeOS?
Instant Recovery recovers a VergeOS backup onto vSphere, Hyper-V, or Nutanix AHV, with Proxmox VE experimental. Recovery inside VergeOS is a Data Resiliency function. Snapshots run as often as you want, and ioGuardian delivers missing data segments inline to a VM that keeps running on production hardware. Both have a role.
Are Veeam backups of VergeOS VMs application-consistent?
Once the guest is prepared with the Veeam Deployment Toolkit, Veeam installs its own agent during the first backup and performs application-aware backup on Windows and Linux guests. Without that preparation, the platform-level backup is crash-consistent. Application-item restore through Veeam Explorers works in either case.
Can VergeOS be a Veeam backup repository?
VergeOS is a source platform in the Veeam model. Standard Veeam repositories hold the backups, and a hardened Linux repository VM can run on VergeOS, which Veeam sees as an ordinary Linux repository.
See it run before you plan it
The September 3 session walks from an empty Virtualization Platforms list to a protected, restored workload. Bring the backup team.