Backup after leaving VMware: Proxmox, Hyper-V and XCP-ng
What changes for your backup when you switch from VMware to Proxmox VE, Hyper-V or XCP-ng - Veeam support, old backups, planning and checklist.
If you move from VMware vSphere to Proxmox VE, Microsoft Hyper-V or XCP-ng, you have to rebuild your backup, because backup jobs, change tracking and recovery paths all depend on the hypervisor in use. Veeam Backup & Replication version 13.1 supports all three platforms, but to different depths: Hyper-V natively, Proxmox VE and XCP-ng via plug-ins with their own worker VMs. Existing VMware backups remain usable and, according to the Veeam documentation, can also be restored to the new platforms.
This guide shows what changes on each platform, where the limitations lie and how to plan the transition. We deliberately do not recommend any particular hypervisor. All information refers to Veeam Backup & Replication 13.1.1 (as of October 2026).
Why are many SMEs considering a switch?
The trigger is usually the change in licensing terms following Broadcom’s acquisition of VMware. Since December 2023, VMware licences have only been available as subscriptions, billed per CPU core with a minimum of 16 cores per processor. In addition, general support for vSphere 8 ends in October 2027, so many companies are facing a contract decision anyway.
Technically, vSphere remains a mature platform, and many companies deliberately renew. If you do switch, however, you should plan the backup from the outset and not only after the migration.
What fundamentally changes for your backup?
An image backup uses the hypervisor’s interfaces: snapshots, change tracking and data transport. That is why VMware backup jobs cannot simply be transferred to the new platform. You create new jobs there, and every new backup chain starts with a full backup.
The backup infrastructure changes as well. With Hyper-V, the host itself (on-host) or a separate off-host proxy handles data transport. For Proxmox VE and XCP-ng, Veeam installs a plug-in on the backup server and deploys so-called workers: small Linux VMs on the hosts that handle data transport. Veeam has supported Hyper-V since version 6 (2011), Proxmox VE since version 12.2 (August 2024) and XCP-ng since version 13.1 (July 2026).
Veeam support by platform compared
The table summarises the key information from the Veeam Help Center (build 13.1.1.18); details can be found in the vendor documentation.
| Feature | Hyper-V | Proxmox VE | XCP-ng |
|---|---|---|---|
| Integration | native | plug-in with worker VMs | plug-in with worker VMs |
| Supported versions | Windows Server 2016 to 2025, Azure Local | Proxmox VE 8.2 to 9.2 (official ISO, x86-64) | XCP-ng 8.3 and later |
| Change tracking | Resilient Change Tracking (RCT) | QEMU dirty bitmaps | hypervisor CBT |
| Application-consistent backup | yes (VSS, Integration Services) | yes (with QEMU Guest Agent) | no (no in-guest quiescing) |
| Instant Recovery | yes | yes; Proxmox VE as a target currently ‘experimental’ | Xen backups to vSphere, Hyper-V, Nutanix AHV or Proxmox VE; Xen as a target not documented |
| File-level restore | yes | yes | yes |
| Replication | yes | yes (since 13.1) | no |
| SureBackup | incl. boot test in a virtual lab | integrity and content checks only | integrity and content checks only |
| Veeam Cloud Connect as target | backup and backup copy | backup copy only | backup copy only |
Hyper-V: what to look out for
Veeam only uses RCT if the VMs run on Hyper-V 2016 or later, the VM configuration version is at least 8.x and, in clusters, all nodes have been upgraded and the cluster functional level 2016 has been reached. Otherwise, every incremental backup reads all data. Veeam does not back up pass-through disks or drives connected inside the guest via iSCSI or Fibre Channel at VM level; for these, the vendor points to the Veeam Agent. Application-consistent backup is not possible for shielded VMs.
Proxmox VE: what to look out for
The dirty bitmaps have one peculiarity: for disks in RAW or VMDK format, Proxmox VE discards them as soon as the VM is shut down or restarted. The next backup then reads all data. According to Veeam, this does not occur with QCOW2. The plug-in does not back up LXC containers, VM templates, passed-through disks or iSCSI disks attached to VMs. For application-consistent backups, the QEMU Guest Agent must be running in the VM. Cluster nodes are added individually and need a direct IP connection to the backup server (no NAT).
XCP-ng: what to look out for
The Xen plug-in is new and has more limitations. It backs up without in-guest quiescing, so the backups are crash-consistent. For databases and other transactional applications, you should therefore also consider application-native backups or the Veeam Agent in the guest system. RAW disks must be excluded from the job, and encryption in the backup job and replication are not supported. There is no CBT on GlusterFS and XOSTOR storage, so every backup there reads the entire disk. At least one worker is required per pool. After a restore to the original location, the next backup creates a full backup again.
Can VMware backups be restored on the new platform?
Yes. According to the Veeam Help Center, the ‘Restore to Proxmox VE’ and ‘Restore to Xen’ functions accept, among others, backups of vSphere VMs. For Hyper-V, the documented route is ‘Instant Recovery to Microsoft Hyper-V’: the VM starts directly from the backup and is then migrated to production storage. Veeam currently classifies Instant Recovery to Proxmox VE as experimental.
When restoring VMs from other platforms to Proxmox VE, Veeam attempts to install the VirtIO drivers; for VMs with VMDK disks and for Instant Recovery, you have to install the drivers yourself beforehand. With XCP-ng, a restore from other platforms can fail if no default VM template is defined for the target pool. Network configuration, boot mode and drivers therefore belong in every test plan.
What does this mean for the migration?
A restore from backup can be part of a migration, but it does not replace migration planning. Since 25 August 2026, Broadcom no longer offers the Virtual Disk Development Kit (VDDK) as a public download; according to Broadcom, only selected backup and recovery technology partners now receive it. This affects migration tools that obtained the VDDK separately. Check with the vendor whether your tool will continue to work. Backup products from technology partners ship the libraries themselves; according to its own documentation, Veeam installs them on the VMware backup proxies.
What happens to old backups when the VMware licence ends?
The backup files are not tied to a running vSphere environment. File-level restore or restore to the new platform remains possible, and according to Veeam, restores do not consume licences. You only need vSphere to restore back to vSphere. Retention is the critical point: Veeam applies the last valid retention rules to orphaned backups in the background as well and can delete them completely in the process. You should therefore define retention before you disable or delete VMware jobs. You can also export the restore points you need, as exported backups are excluded from this background retention. Also keep the passwords for encrypted backups safe.
What built-in tools do the platforms offer?
All three platforms offer their own backup tools. Proxmox VE has an integrated backup function and Proxmox Backup Server (currently version 4.2 from April 2026), which backs up incrementally via dirty bitmaps, deduplicates and supports single-file restore as well as live restore. For XCP-ng, Xen Orchestra is the tool officially supported by the project, with full and incremental backups, replication, file-level restore, encryption and CBT. Windows Server includes Windows Server Backup, which can back up and restore Hyper-V VMs at host level.
Which approach suits you depends on the number of systems, mixed environments, central monitoring and off-site requirements. In any case, also back up the platform configuration, for XCP-ng for example the pool metadata.
How do you plan the transition?
Parallel phase: Keep the VMware jobs running until every migrated VM has been successfully backed up on the new platform and restored as a test. Plan storage for the additional full backups.
Versions and licences: XCP-ng requires Veeam 13.1; version 12 is only supported until February 2027. Socket licences cover vSphere and Hyper-V hosts. For Proxmox VE and XCP-ng, you need instances of the Veeam Universal License (VUL), which according to Veeam can be used across platforms. A VM counts as protected and consumes instances if it has been backed up within the last 31 days. During the parallel phase, the old and new VM may therefore be counted separately until the period expires or you release the instance manually.
Test restores: For Proxmox VE and XCP-ng, SureBackup only offers integrity and content checks, not an automatic boot test in a virtual lab. You should therefore schedule regular test restores as a fixed task. How to go about this is explained in our guide Testing restores.
Off-site copy independent of the hypervisor: A copy outside your site protects you regardless of the platform. Proxmox and XCP-ng VMs only reach Veeam Cloud Connect via backup copy. For XCP-ng, the plug-in documentation lists this as supported, while the Cloud Connect documentation (as of September 2026) does not yet list Xen backups; with us, backup copies of XCP-ng backups work. Clarify this in advance with other providers. Which restores are possible directly from the cloud repository also depends on the platform; for Proxmox copies, Veeam only lists file-level restore on the customer side. You should therefore test the way back in advance.
Checklist for the transition
- Inventory created: VMs, applications, disk formats, storage types and RTO and RPO per system
- Veeam updated to version 13.1.x, plug-ins and workers set up
- Licensing model checked (VUL instances for Proxmox VE and XCP-ng, buffer for the parallel phase)
- Application consistency clarified: Guest Agent on Proxmox VE, alternatives for databases on XCP-ng
- Unsupported objects identified (e.g. LXC containers, RAW disks, pass-through disks)
- New jobs set up, first full backups successful
- Retention of VMware backups defined, required restore points exported if necessary
- Restore of every critical VM on the new platform tested and documented
- Off-site copy set up and restore from the off-site copy tested
- Configuration of the new platform backed up and disaster recovery manual updated
Frequently asked questions
Can I keep using my Veeam licence after the switch?
According to Veeam, Veeam Universal License instances can be used across platforms and reassigned. Socket licences apply to vSphere and Hyper-V hosts; for other platforms, they include a few additional instances at most.
Do I still need VMware to restore old backups?
No, only to restore back to vSphere. Files and entire VMs can also be restored on the new platform.
Are the backups as consistent as under VMware?
Under Hyper-V and Proxmox VE (with QEMU Guest Agent), application-consistent backups are possible. Under XCP-ng with Veeam 13.1.1 they are crash-consistent, so you should plan a supplementary solution for databases.
Can I back up Proxmox or XCP-ng VMs directly via Veeam Cloud Connect?
No. Veeam only provides direct backup jobs to a cloud repository for vSphere and Hyper-V. You back up locally first and then transfer a copy via a backup copy job.
Conclusion
Changing hypervisor is always a backup project too. Hyper-V, Proxmox VE and XCP-ng can all be backed up with Veeam, but they differ in change tracking, application consistency, Instant Recovery and cloud connectivity. If you know the limitations, deliberately retain old backups and restore every migrated VM once, you avoid gaps in protection.
As a Veeam Cloud & Service Provider, we support you along the way. With the Veeam Managed Service, we monitor your backup servers on site; this includes a maintenance contract with individually agreed response times and licensing via the Veeam Rental model. With Veeam Cloud Connect, you transfer encrypted backup copies to our cloud repository in an ISO/IEC 27001 certified data centre in Germany, with immutability and Insider Protection on request. Get in touch: hello@myveeam.cloud or +49 8106 928 9493.
Sources
- Veeam Backup & Replication 13.1 Release Notes (29 July 2026)
- Veeam Backup & Replication 12.2 Release Notes (28 August 2024)
- Veeam: Now available - Veeam Backup & Replication v6 (Hyper-V support) (30 November 2011)
- Veeam Help Center: Microsoft Hyper-V - Platform Support (9 September 2026)
- Veeam Help Center: Changed Block Tracking (Hyper-V) (3 December 2025)
- Veeam Help Center: Proxmox VE - Platform Support (18 September 2026)
- Veeam Help Center: Proxmox VE - Changed Block Tracking (16 July 2026)
- Veeam Help Center: Proxmox VE - Considerations and Limitations (25 September 2026)
- Veeam Help Center: Instant Recovery to Proxmox VE (21 August 2026)
- Veeam Help Center: XCP-ng and Citrix XenServer - Platform Support (25 September 2026)
- Veeam Help Center: Xen - Changed Block Tracking (7 August 2026)
- Veeam Help Center: Xen - Considerations and Limitations (5 August 2026)
- Veeam Help Center: Restore to Proxmox VE (15 July 2026)
- Veeam Help Center: Restore to Xen (11 August 2026)
- Veeam Help Center: Instant Recovery to Microsoft Hyper-V (15 July 2026)
- Veeam Help Center: Licensing (6 August 2026)
- Veeam Help Center: Background Retention (31 March 2026)
- Veeam Cloud Connect Guide: Tasks with Cloud Repository (2 February 2026)
- Veeam Cloud Connect Guide: Backup Copy to Cloud Repository (4 September 2026)
- Veeam Cloud Connect Guide: Veeam Cloud Connect Backup - Limitations (24 September 2026)
- Veeam: Universal License (accessed 5 October 2026)
- Veeam: Product Lifecycle Policy (accessed 5 October 2026)
- Veeam KB4523: VDDK libraries in Veeam Backup & Replication (1 July 2024)
- Microsoft Learn: Hyper-V Backup Approaches (17 June 2025)
- Microsoft Learn: Start-WBHyperVRecovery (Windows Server Backup) (accessed 5 October 2026)
- Proxmox VE Wiki: Backup and Restore (accessed 5 October 2026)
- Proxmox Forum: Proxmox Backup Server 4.2 released (29 April 2026)
- XCP-ng Documentation: Backup (15 August 2026)
- Xen Orchestra 5.96 (Changed Block Tracking) (July 2024)
- heise: Abozwang - Broadcom stellt Lizenzmodelle für VMware um (in German, 13 December 2023)
- heise: VMware backs down - companies can continue to license 16 cores (10 April 2025)
- heise: Broadcom erschwert den VMware-Ausstieg (in German, 22 September 2026)
- TechTarget: Broadcom confirms change in VMware migration tool access (9 September 2026)