Before You Begin

Before you create a backup job, consider the following limitations:

You can back up each VM with one backup job at a time. If a VM is already being processed by a backup job, another backup job will not start processing this VM until the currently running backup operation completes.
You cannot back up a VM created as a linked clone of a template — use full clones instead.

You cannot back up a VM being restored. Wait for the restore process to complete, and then start the backup job.

You cannot include into a backup job a VM that is being backed up by 3rd party software. Wait for the backup process to complete or stop the currently running job manually, and then add the VM to the necessary backup job.

You cannot include into a backup job a resource pool that does not contain any VMs. Note that after you update a resource pool in the Proxmox VE administration portal, it may take up to 15 minutes for Veeam Backup for Proxmox VE to synchronize data between Proxmox VE and Veeam Backup & Replication.
Veeam Backup 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 Backup for Proxmox VE does not support backup of VM permissions granted to users, user groups and API tokens.
By default, Veeam Backup for Proxmox VE enables deduplication for backed-up data. Due to technical limitations, you cannot disable it while configuring backup jobs.

By default, backup encryption is disabled for backed-up data. However, you can enable encryption at the repository level as described in the Veeam Backup & Replication User Guide, section Access Permissions.
VM guest OS file indexing is not supported for backups created with Veeam Backup for Proxmox VE.

Since Veeam Backup & Replication does not allow you to assign information about locations to the Proxmox VE server and workers, job statistics do not include information on the Proxmox VE VM data migration between different geographic regions.