Before you create a backup copy job, check the following prerequisites:
- Backup infrastructure components that will take part in the backup copy process must be added to the backup infrastructure and properly configured. These include source and target backup repositories between which VM backups must be copied.
- The target backup repository must have enough free space to store copied VM backups. To receive alerts about low space on the backup repository, configure global notification settings. For more information, see Specifying Other Notification Settings.
- If you plan to use pre-job and/or post-job scripts, you must create scripts before you configure the backup copy job.
- [For backup mapping] The backup copy job can be mapped to a backup if the backup chain is created with the incremental backup method. You cannot map the backup copy job to a backup if the backup chain is created with the reverse incremental backup method or contains both incremental and reverse incremental restore points (for example, if the backup chain was transformed).
If you plan to use WAN accelerators for backup copying, check the following prerequisites:
- Source and target WAN accelerators must be added to the backup infrastructure and properly configured. For more information, see Adding WAN Accelerators.
- A license for Enterprise Plus Edition for Veeam Backup & Replication must be installed on the backup server.
- It is recommended that you pre-populate the global cache on the target WAN accelerator before you start the backup copy job. Global cache population helps reduce the amount of traffic transferred over WAN. For more information, see Populating Global Cache.
Mind the following:
Veeam Backup & Replication ignores the cardinality setting for VM tag categories. For example, you create a tag category Priority and set cardinality to One tag per object. In the tag category, you create two tags: Normal and High. You assign the Normal tag to a VM folder and the High tag to a VM in this folder. If you now configure a job that will process objects with the Normal tag, the VM with the High tag will also be added to this job (since Veeam Backup & Replication regards that VMs and templates in the VM container inherit the tag assigned to the container).
To overcome this situation, you can add to the list of exclusions the tag assigned to objects that you do not want to process.