Before You Begin
Before you create a backup job, check the following:
- Backup infrastructure components that will take part in the backup process must be added to the backup infrastructure and properly configured. These include ESXi hosts on which VMs are registered, backup proxy and backup repository.
- The backup repository must have enough free space to store created backup files. To receive alerts about low space in the backup repository, configure global notification settings. For more information, see Specifying Other Notification Settings.
- If you plan to map a backup job to a backup file that already exists in the backup repository, you must perform the rescan operations for this backup repository. Otherwise, Veeam Backup & Replication will not be able to recognize backup files in the backup repository. For more information, see Rescanning Backup Repositories.
- If you plan to use an HPE StoreOnce repository as a target for backup jobs, check limitations and requirements for the repository.
- If you plan to configure a secondary destination for the backup job, you can create a backup copy job or backup to tape job beforehand. While creating the backup copy or backup to tape job, you can leave the source empty and link the source to the job later. For more information, see Creating Backup Copy Jobs and Creating Backup to Tape Jobs.
- If you plan to enable guest processing for the job, check Guest Processing Requirements and Limitations.
- If you plan to use pre-job and post-job scripts and/or pre-freeze and post-thaw scripts, you must create scripts before you configure the backup job.
- If you plan to periodically perform maintenance operations with backup files, consider the following limitations: Health Check for Backup Files, Retention Policy for Deleted VMs, Compact of Full Backup File.
- [For Dell Data Domain backup repository] The length of forward incremental and forever forward incremental backup chains that contain one full backup and a set of subsequent incremental backups cannot be greater than 60 restore points. To overcome this limitation, schedule full backups (active or synthetic) to split the backup chain into shorter series. For example, to perform backups at 30-minute intervals, 24 hours a day, you must schedule synthetic fulls every day. In this scenario, intervals immediately after midnight may be skipped due to the duration of synthetic processing. For more information, see How Synthetic Full Backup Works.
- If you assign the role of a backup proxy to a VM, you should not add this VM to the list of processed VMs in a job that uses this backup proxy. Such configuration may result in degraded job performance. Veeam Backup & Replication will assign this backup proxy to process other VMs in the job first, and processing of this VM itself will be put on hold. Veeam Backup & Replication will report the following message in the job statistics: VM is a backup proxy, waiting for it to stop processing tasks. The job will start processing this VM only after the backup proxy deployed on the VM finishes its tasks.
- If you use tags to categorize virtual infrastructure objects, check limitations for VM tags. For more information, see VM Tags.
- If a job is unable to complete within 21 days period, it will be stopped with the Failed status.
- If you plan to protect VMware Cloud Director objects, consider using the dedicated backup job. For more information, see Backup for VMware Cloud Director.