Considerations and Limitations

When you plan to use Veeam Plug-in for Proxmox VE, keep in mind the following limitations and considerations.

Configuration

When configuring Veeam Plug-in for Proxmox VE, consider the following:

Veeam Plug-in for Proxmox VE supports Proxmox Virtual Environment deployments created using the official ISO image provided by Proxmox only.
Veeam Plug-in for Proxmox VE supports only the /bin/bash shell to perform management operations with the Proxmox VE server.

Veeam Plug-in for Proxmox VE does not support credentials of the SSH Private Keys type to access the Proxmox VE server.
Veeam Plug-in for Proxmox VE does not support user accounts with multi-factor authentication to access the Proxmox VE server.
The Proxmox VE server must be able to establish a direct IP connection to the backup server. Connections through NAT gateways are not supported.

Before you add a Proxmox VE server to the backup infrastructure, ensure that it has been assigned a unique Proxmox VE system UUID and its name does not contain an FQDN.

If you want to protect VMs that reside in a Proxmox VE cluster, all nodes of these cluster must be added to the backup infrastructure separately. Adding clusters as standalone entities is not supported.
After you add nodes of a cluster to the backup infrastructure, you must not change the name of the cluster in the Proxmox VE administration portal.
After you make changes to your Proxmox VE environment (for example, you migrate a VM between cluster nodes), these changes may not appear in Veeam Backup & Replication immediately — the data synchronization process between the backup server and the Proxmox VE server may take up to 15 minutes to complete. You can speed up the data synchronization process by rescanning the Proxmox VE server.

Backup Repositories

When managing backup repositories, consider that Veeam Plug-in for Proxmox VE does not support storing backups in HPE Cloud Bank Storage repositories. However, you can use them for storing copies of backups created with Veeam Plug-in for Proxmox VE.

Workers

When configuring workers, consider the following:

The default local storage must be enabled on all hosts where worker VMs will be deployed. If you cannot use the default storage in your environment, contact Veeam Customer Support.
The storage where system files of workers will be stored must support snapshots.

Backup

When protecting Proxmox VE resources, consider the following:

Veeam Plug-in for Proxmox VE does not support backup of LXC containers.

Veeam Plug-in for Proxmox VE does not support backup of VM templates.
Veeam Plug-in for Proxmox VE does not support backup of VMs created from templates as linked clones. Backup of full clones is supported.
Veeam Plug-in for Proxmox VE does not support backup of VMs with the same BIOS UUID.

Veeam Plug-in for Proxmox VE does not support backup of iSCSI disks. If iSCSI disks are attached to a VM included into a backup job, these disks will be skipped from processing.
Veeam Plug-in for Proxmox VE does not support backup of directly attached (passthrough) disks. If such disks are attached to a VM included into a backup job, these disks will be skipped from processing.
Veeam Plug-in for Proxmox VE does not support backup of VM permissions granted to users, user groups and API tokens.

Veeam Plug-in for Proxmox VE does not support backup of VMs that store their disks in the BTRFS and custom storage. All other Proxmox VE storage types are supported.
The number of concurrent backup operations performed in each storage is limited to 4 to avoid excessive load on the production environment. To change the limit, contact Veeam Customer Support.

Veeam Plug-in for Proxmox VE does not support VM replication.

Restore

When restoring Proxmox VE resources, consider the following:

Veeam Plug-in for Proxmox VE does not support restore of VMs to the BTRFS and custom storage.
Veeam Plug-in for Proxmox VE does not support restore of VMs to Ceph/RBD storage if the krbd property is enabled.