Before You Begin

Before you create a Veeam Agent backup job managed by the backup server in the Veeam Backup & Replication web UI, check the following prerequisites:

  • The Veeam Backup & Replication license must have a sufficient number of instances to process servers and workstations that you plan to add to the Veeam Agent backup job. To learn more, see Licensing Requirements.
  • The target location where you plan to store backup files must have enough free space.
  • Protection groups that you want to add to the job must be configured in advance.

Veeam Agent backup jobs have the following limitations:

  • If you want to perform a volume-level restore of a machine using Veeam Agent, the BIOS boot partition of this machine must be associated with a block device. Otherwise, Veeam Agent supports only file-level restore from the backup of the machine.
  • You can create Veeam Agent backups in a Veeam backup repository. If you want to save backups in other target locations, you must configure a Veeam Agent backup job managed by Veeam Agent (backup policy). To learn more, see Creating Policy for Linux Computers.

NOTE

The Veeam Cloud Connect repository is not supported as a backup destination in the Veeam Backup & Replication web UI.

  • Veeam Agent does not support backup of bind mount points. In the scope of the backup job, you must specify the path to the original mount point instead.

If you perform an entire machine backup of a system with bind mount points, Veeam Agent will back up only the data from the original mount points. Veeam Agent will not back up the bind mount points themselves and will not replicate the bind mount configuration in the backup. After restore, you may need to manually reconfigure any bind mounts that existed on the original system.

  • You cannot add a Veeam Agent computer protected by a Veeam Agent backup policy to a backup job managed by the backup server. To add such a computer to a backup job managed by the backup server, first remove the computer from the Veeam Agent backup policy.

Page updated 2026-07-14

Page content applies to build 13.1.0.411