Veeam 13.1 and Proxmox: from backup to more comprehensive environment protection

Veeam Backup & Replication 13.1 significantly expands support for Proxmox VE. It no longer focuses primarily on backup and restore, but also includes native replication between Proxmox VE environments, expanded recovery options, and improvements in management and security. 

Among the more important new features are replication without the need for shared storage (shared storage) and the options for faster recovery and restore across different platforms (cross-platform restore). Both areas indicate that support for Proxmox VE is approaching the level that Veeam has long offered for VMware and Hyper-V. At the same time, some functionalities are still labeled as experimental, so additional verification and testing is advisable before using them in production environments. 

Backup remains the foundation 

Veeam supported backing up Proxmox VE virtual machines even before version 13.1. Administrators can use standard backup jobs, VeeamZIP for one-off copies of virtual machines, and Backup Copy Jobs to create additional copies of data at other locations, for example in line with the 3-2-1 rule. Backup windows and backup mapping are also available. 

Version 13.1 complements this foundation with expanded malware detection for workloads in the Proxmox VE environment. 

Backup is currently the most mature part of Veeam’s support for Proxmox VE and also the one organizations will most often need. Backups, retention policies, and protection against the effects of ransomware are the basic elements of protecting a production environment, so it is not sensible to wait here for the further development of other functionalities. 

Replication between Proxmox VE environments 

One of the more important new features in version 13.1 is native replication of virtual machines between Proxmox VE environments. It can run directly between hosts (host-to-host), without the need for shared storage, and replication between different data centers and different types of storage is also supported. 

This expands options when planning availability and recovery after an outage, as the target environment does not need to be designed as a mirror copy of the source. For organizations adopting Proxmox VE as an alternative to existing virtualization platforms, this is important primarily because Veeam can also become part of a broader strategy for environment protection and recovery. 

Replication in version 13.1 is still marked as experimental, so it needs to be thoroughly tested before use in critical DR scenarios. A gradual rollout makes sense: backup in production, replication first in a controlled environment. 

Recovery and cross-platform migration 

Veeam Backup & Replication 13.1 also expands the options for restoring Proxmox VE virtual machines. In addition to classic restore from backups back into the Proxmox VE environment, Instant VM Recovery is available, where a virtual machine can be started directly from a backup while the migration to production storage proceeds in the background. 

Cross-platform restore is also important. Virtual machines from VMware, Hyper-V, and other supported platforms can be restored directly into Proxmox VE, with Veeam automatically handling the inclusion of VirtIO drivers and configuration adjustments. The functionality is therefore interesting not only from a recovery perspective but also when planning a move to Proxmox VE. 

The same caveat applies to Instant VM Recovery as to replication: the functionality is still labeled as experimental, so it makes sense to test it thoroughly before using it in critical production scenarios. 

Management, networking, and security 

Version 13.1 also improves the management of Proxmox VE environments. Through the Veeam Web UI, backup jobs, restore operations, and infrastructure management are available, bringing the experience closer to working with VMware and Hyper-V environments. Advanced RBAC enables more granular assignment of permissions at the level of individual virtual machines, jobs, categories, and infrastructure components, however this functionality is still marked as experimental. 

VLAN tagging is also supported for restored virtual machines and worker servers, which is especially important in environments where network segmentation is based on VLANs. In the area of security, version 13.1 delivers unified worker images compliant with the FIPS and DISA STIG standards. 

These are less prominent updates, but precisely such functionalities are important when incorporating Proxmox VE into more demanding production environments, where not only backups and restore matter, but also the way management is handled, network segmentation, and compliance with security requirements. 

What Veeam 13.1 means for Proxmox VE in practice 

Broader support for Proxmox VE arrives at a time when some organizations, due to changes in the VMware ecosystem and higher licensing costs, are seeking alternatives to existing virtualization platforms. In such a transition, however, choosing a hypervisor is not enough. Equally important are proven data protection and the ability to recover effectively after an outage. 

An advantage of Veeam’s approach is also that organizations already using Veeam in VMware or Hyper-V environments do not need to introduce a completely new data protection system. A familiar environment, procedures, and way of management can reduce the need for additional training and the risk associated with adopting Proxmox VE. 

It therefore currently makes sense to clearly distinguish between mature functionalities and those still in an experimental phase. Backup can be included in production environments today, while for replication and Instant VM Recovery a pilot approach with clear expectations and prior testing is more appropriate. Both functionalities are still labeled as experimental. 

Veeam Backup & Replication 13.1 thus opens up more options for using Proxmox VE in more demanding production environments, but it does not yet make sense to treat all the new features the same. There is no reason to delay when it comes to backup, while more advanced DR scenarios should, for now, be introduced gradually and after prior testing.