Before you create a VM copy job, check the following prerequisites:
- Backup infrastructure components that will take part in the VM copying process must be added to the backup infrastructure and properly configured. These include the source ESX(i) host and server or backup repository on which you plan to store the VM copy.
- The target storage device must have enough free space to store created VM copies. To receive alerts about low space on the storage device, configure global notification settings. For more information, see Specifying Other Notification Settings.
- If you plan to use pre-freeze and/or post-thaw scripts, you must create scripts before you configure the VM copy job.
Mind the following limitations:
- Due to Microsoft limitations, you cannot use Microsoft Azure Active Directory credentials to perform application-aware processing on VMs running Microsoft Windows 10.
- 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.