Veeam has integrated XCP-ng as a fully supported hypervisor in Veeam Backup & Replication 13.1, available since July 29, 2026. This update allows for VM protection, file and application recovery, threat scanning of backups, and restoring workloads from other platforms on XCP-ng. For companies considering reducing their reliance on VMware, this announcement addresses one of the most common concerns: how to maintain an enterprise backup platform during migration.
The key points of Veeam support for XCP-ng in 30 seconds
- Veeam Backup & Replication 13.1 recognizes XCP-ng as a fully supported hypervisor.
- The integration includes incremental backups with Changed Block Tracking, full restores, file recovery, and anti-malware analysis.
- Backups from VMware, Hyper-V, Nutanix AHV, public clouds, and physical servers can be restored on XCP-ng.
- XCP-ng backups can also be recovered on other hypervisors or in AWS, Azure, and Google Cloud.
- Operational limitations exist and should be reviewed before deploying in production.
Support does not automatically turn a complex migration into a one-click process. However, it enables maintaining a consistent layer of protection before, during, and after the hypervisor switch. This continuity is especially valuable for organizations already using Veeam and wanting to avoid redesigning their entire backup strategy while replacing VMware.
This update also strengthens XCP-ng’s position in the enterprise market. Born as an open platform based on Xen, it uses XAPI for managing hosts, pools, VMs, storage, and networks. Vates develops and maintains its commercial offerings around XCP-ng and Xen Orchestra, providing support, management, migration, and data protection services.
What Veeam Enables You to Do with XCP-ng
The integration in Veeam Backup & Replication 13.1 offers hypervisor-level backups. The software can identify virtual machines hosted on XCP-ng, create protection jobs, and store copies within Veeam’s repository infrastructure.
Jobs utilize Changed Block Tracking (CBT) to locate modified blocks since the last backup. This mechanism prevents reading and transferring entire virtual disks during incremental backups, provided that the configuration and platform effectively maintain this information.
Veeam also includes several functions related to recovery and cyber resilience:
- Full VM restoration.
- Direct file recovery without restoring the entire VM.
- Mounting backup disks in read-only mode.
- Export to VHD, VHDX, or VMDK formats.
- Backup integrity verification.
- Analysis with Veeam Threat Hunter.
- YARA rules for detecting indicators or suspicious patterns.
- Application recovery via Veeam Explorer.
Application-aware detection facilitates working with data from Microsoft Active Directory, Exchange, SharePoint, SQL Server, Oracle databases, and other compatible workloads. The specific scope depends on the guest OS, application, and backup method used.
Veeam presents these features as part of its strategy to extend protection beyond VMware, Hyper-V, and Nutanix AHV. Version 13.1 also adds support for Citrix XenServer, Sangfor aSV, Platform9, and VergeOS, expanding its hypervisor catalog.
Backup as a Bridge During Migration
One of the key aspects is cross-platform recovery capabilities.
Veeam allows restoring protected machines from other hypervisors, on AWS, Azure, Google Cloud, or physical servers backed up with Veeam Agent for Windows or Linux, directly onto XCP-ng. During recovery, necessary adjustments are made to ensure the guest OS can boot on the target platform.
This provides a practical way to migrate workloads from VMware:
- Back up the VM on the source platform.
- Validate the backup and, if necessary, scan for malware.
- Configure network, storage, and compute resources on XCP-ng.
- Restore the VM onto the new hypervisor.
- Check drivers, networking, applications, and performance.
- The restored workload then becomes protected as an XCP-ng VM.
This process reduces risk because the original copy remains available. It also allows testing restoration before fully decommissioning the source machine.
However, it does not necessarily constitute a hot migration. Recovery time depends on disk size, repository speed, network, target storage, and post-recovery checks. Workloads with high write activity might require a maintenance window or specific procedures to ensure data consistency.
The most relevant feature for this scenario is the full restore to XCP-ng. This should not be confused with Instant VM Recovery: Veeam’s documentation states that backups created in XCP-ng can be initiated via instant recovery onto VMware vSphere, Hyper-V, Nutanix AHV, and, with experimental support, Proxmox VE. It does not mention instant recovery support directly onto XCP-ng.
Greater Flexibility to Move Loads Post-Backup
Portability works in the opposite direction as well.
A backup created from an XCP-ng VM can be restored on compatible hypervisors or in cloud environments. This separates the protection strategy from being tied to a single virtualization platform and helps prepare contingency plans with different target environments.
For organizations leaving VMware, this capability offers two advantages. First, it preserves familiar Veeam processes and repositories. Second, it prevents the new hypervisor from becoming another silo with no exit route.
Technical differences remain. Restoring a VM to another platform may require new drivers, network interface adjustments, virtual CPU modifications, or boot method changes. Licenses, hardware integrations, and software tied to specific machine IDs may also need review and reconfiguration.
Therefore, a realistic backup strategy should include recovery testing, not just verifying that backups complete successfully.
XCP-ng Gains Enterprise Credibility While Maintaining Its Own Backup Solution
XCP-ng already offers built-in protection via Xen Orchestra. Its system allows scheduling full and incremental backups, VM replication, retention policies, and workload recovery within Vates’ ecosystem.
Veeam’s arrival does not necessarily replace these features. Instead, it provides an alternative particularly valuable for companies with standardized Veeam operations, hardened repositories, cross-platform recovery needs, or those seeking a single product for multiple hypervisors.
In some environments, combining both layers may be beneficial. Xen Orchestra can handle certain operational backups, while Veeam focuses on enterprise-grade retention, application recovery, or data portability. The approach should avoid unnecessary duplication and assign clear responsibilities to each tool.
XCP-ng is characterized as an open, Xen-based virtualization platform suitable for small setups and large data centers. Xen Orchestra acts as its central management and automation console.
Limitations to Review Before Deployment
Official support does not mean all VMware features are available identically in XCP-ng. Veeam Backup & Replication 13.1 notes several specific limitations.
One involves the pool coordinator. If that role is moved from the original registered node to another host, operations may be suspended until the coordinator is updated in the console and the new certificate accepted.
Veeam suggests preventive measures such as using certificates with alternative names covering all nodes or pre-accepting hosts. The company is working on simpler mechanisms for future releases.
Transport modes also differ:
- Storage repositories based on SMAPIv3 do not support Hot-Add due to platform limitations involving read-only snapshots.
- The NBD transport requires OpenSSL 3.0.9, included in XCP-ng 8.3 LTS from March 2026.
- NBD is disabled by default, and performance depends on network configuration.
- Veeam recommends dedicated workers per host to avoid transport issues.
Xen RAW disks do not support snapshots and cannot be included in backups without transformation to a compatible format prior to protection.
Restoring to the original location may not always preserve disk IDs. Consequently, incremental backups afterward could behave like full copies, and exclusions based on specific disks may need reconfiguration.
Additional documented limitations include loss of Xen Orchestra auxiliary metadata, truncation of long names to 80 characters when restoring elsewhere, and issues with Hot-Add on GFS2 storage.
What Organizations Should Test Before Migrating
Official support availability lowers a commercial barrier but does not replace proof-of-concept testing.
Before migrating critical workloads, organizations should verify at least four areas:
Machine compatibility: Review OS, UEFI/BIOS firmware, disk types, drivers, network interfaces, and application-specific requirements.
Backup performance: Measure actual backup windows, worker usage, CBT behavior, and repository throughput.
Recovery time: Conduct full restoration tests in lab environments to assess whether recovery objectives are achievable and identify manual steps.
Pool operation: Test coordinator changes, host failures, certificate renewals, and storage variations to ensure stability.
Veeam Backup & Replication 13.1 was launched on July 29, 2026. It is recommended to review requirements, known issues, and compatibility before installation or upgrade, especially in environments migrating from earlier versions.
An Additional Piece in Post-VMware Diversification
The shift in VMware’s business model has led many organizations to compare platforms like Proxmox VE, Nutanix AHV, Hyper-V, OpenShift Virtualization, HPE VM Essentials, XCP-ng, among others.
Choosing a hypervisor is only part of the decision. An enterprise solution also requires backup, monitoring, support, automation, compatible storage, disaster recovery, and skilled professionals.
Veeam’s official support does not by itself make XCP-ng the best choice for all companies. However, it completes an important piece of its broader offering and enables Veeam clients to evaluate it without abandoning existing protection infrastructure.
For Vates, this integration broadens the list of vendors endorsing their platform. For Veeam, it opens up a market of organizations seeking hypervisor diversification. For customers, it provides an additional route where backup is decoupled from the decision to stay with or leave VMware.
Frequently Asked Questions
From which version is XCP-ng officially supported by Veeam?
XCP-ng has been fully supported since Veeam Backup & Replication 13.1, released on July 29, 2026.
Can VMware VMs be restored directly onto XCP-ng?
Veeam allows restoring backups from other compatible hypervisors, including VMware, onto XCP-ng. Migration may require adjustments to drivers, networking, boot configurations, and applications.
Does Veeam replace Xen Orchestra’s backup functions?
Not necessarily. Xen Orchestra provides its own backup and replication features. Veeam offers an additional option, especially useful for organizations already using Veeam or needing cross-platform recovery and cloud portability.
Are all Veeam functions available in XCP-ng?
No. Version 13.1 offers broad protection and recovery features but retains limitations related to transport modes, storage types, pool coordinators, RAW disks, and certain metadata. It’s important to review official notes before deploying in production.
Sources:
