Click Advanced to specify advanced options for the backup job.
Select the method you want to use to back up VMs: Reversed incremental or Incremental. For details, see Backup Methods.
If you choose the incremental backup method, you must select to periodically create a synthetic full backup or perform active full backups.
|•||To create a synthetic full backup, select the Enable synthetic fulls (forever-incremental) check box and click Days to schedule synthetic fulls on the necessary days. The created synthetic full backup will be used as a starting point for subsequent increments.|
You can additionally choose to transform the previous full backup chain into the reversed incremental backup chain. To do so, select the Transform previous full backup chains into rollbacks check box. To learn more about the transform process, see Transforming Incremental Backup Chains into Reversed Incremental Backup Chains.
|•||To perform full backups regularly, select the Perform active full backups periodically check box and define scheduling settings. The created full backup will be used as a starting point for subsequent increments.|
If you schedule the active full backup and the synthetic full backup with or without the transform task on the same day, Veeam Backup & Replication will perform only active full backup and skip the synthetic backup and the transform task.
When scheduling periodic full backups, you need to make sure you have enough free space on the backup repository. As an alternative, you can perform active full backup manually. To do so, right-click the ready backup job in the list and select Active Full.
On the Storage tab, specify deduplication, compression and optimization settings for backup files that the job will provision. For details, see Compression and Deduplication.
By default, Veeam Backup & Replication performs deduplication before storing VM data to a backup repository. Deduplication provides a smaller size of the resulting backup file but may reduce backup performance.
You can disable deduplication at all by clearing the Enable inline data deduplication check box. By disabling this option, you also change the mechanism of incremental backup. If Changed Block Tracking is enabled for the job, Veeam Backup & Replication will save all data block CBT has marked as new to the destination storage, without performing additional check or using Veeam’s filtering mechanism. This will result in faster incremental backup. To learn more, see Changed Block Tracking.
In the Compression section, specify a compression level for the created backup: None, Dedupe-friendly, Optimal, High or Extreme.
In the Storage optimizations section, select the type of backup target you are planning to use. Depending on the chosen option, Veeam Backup & Replication will use data blocks of different size to optimize the size of backups and job performance:
|•||Local target (16 TB + backup size). This option provides the lowest deduplication ratio and produces the largest incremental backup file. This option is recommended for backup jobs that can produce very large full backup files — larger than 16 TB.|
|•||Local target. This option is recommended if you are planning to use SAN, DAS or local storage as a target. SAN identifies larger blocks of data and therefore can process larger quantities of data at a time. This option provides the fastest backup job performance but reduces the deduplication ratio — the larger a data block is, the lower is the chance to find an identical block.|
|•||LAN target. This option is recommended for NAS and on-site replication. It provides a better deduplication ratio and reduces the size of an incremental backup file.|
|•||WAN target. This option is recommended if you are planning to use WAN for offsite backup. Veeam Backup & Replication uses small data blocks, which involves significant processing overhead but results in the maximum deduplication ratio and the smallest size of increment files.|
Use the Notifications tab if you want to be notified when the backup job is completed.
|•||Select the Send email notifications to the following recipients check box if you want to receive notifications by email in case of job failure or success. In the field below, specify a recipient’s email address. You can enter several addresses separated by a semicolon.|
Email notifications will be sent only if you have selected the Enable email notification check box in the Options window and specified email notification settings (select Tools > Options from the main menu). For details, see Specifying Notification Settings.
|•||Select the Enable SNMP notification for this job check box if you want to receive SNMP traps when a job is completed successfully. SNMP traps will be sent if you configure SNMP settings in Veeam Backup & Replication and on the recipient’s computer. For details, see Specifying SNMP Settings.|
|•||In the VM notes section, select the Set successful backup details to this VM attribute check box to write to a VM custom attribute information about successfully performed backup and data on backup results (backup date and time, backup console name and path to the backup file). In the field below, enter the name of the necessary attribute. If the specified attribute does not exist, Veeam Backup & Replication will create it.|
On the vSphere tab, specify if file system freezing and changed block tracking should be used.
The Enable VMware tools quiescence option enables freezing of the file system for proper snapshot creation. With this option enabled, creation of a snapshot is performed with the help of the sync driver responsible for holding incoming I/O and flushing all dirty data to a disk, thus making the file systems consistent.
In the Changed block tracking section, specify if vSphere Changed Block Tracking (CBT) should be used. By default, this option is selected. If you want to force using changed block tracking even if CBT is disabled on the ESX(i) host, select the Enable changed block tracking for all processed VMs check box.
You can use this option only for VMs using virtual hardware version 7 or later.
On the Advanced tab, specify miscellaneous advanced settings for the job.
|•||Select the Enable automatic backup integrity checks check box if you want Veeam Backup & Replication to periodically check the full backup file. An automatic backup check allows you to verify integrity of the backup file and avoid a situation when a full backup is corrupted, making all further increments corrupted, too.|
A backup check is performed every time the job is started. During the backup check, Veeam Backup & Replication verifies the service data written to the backup file. If the check fails, Veeam Backup & Replication displays a notification message, prompting you to perform a new active full backup. During such full backup, no integrity check is performed.
The integrity check verifies only service data in the full backup file. To perform a CRC check, you can create a SureBackup recovery verification job and instruct it to validate the verified backup file. To learn more, see Performing Recovery Verification.
|•||If you are running pre-ESX 3.5 Update 2 hosts, consider enabling the safe snapshot removal option. Because a full image-level backup can take long time depending on the VM size, the VM snapshot can grow very large. When a large snapshot is removed on a VM with heavy disk I/O, a consolidation helper snapshot may grow large too, and will then require a long time to be committed. While a helper snapshot is being committed into VM virtual disk files, the VM remains completely “frozen”, and depending on the consolidation helper snapshot size, the freeze time may be so long that some applications running on a VM will time out. To prevent such situation, Veeam Backup & Replication offers a procedure of safe snapshot removal which includes creating an additional snapshot in cases when the “main” snapshot size is above the specified threshold. An additional snapshot is used to host writes while the “main” snapshot is being deleted. This ensures that a consolidation helper snapshot does not grow large. To use this option, select the Safe removal for snapshots larger than ... MB check box and specify a threshold for the size of a snapshot that should not be exceeded.|
|•||In the File selective image processing section, define whether you want to exclude blocks of Windows page files from the backup. During backup, Veeam Backup & Replication checks the NTFS MFT file on Windows-based VMs to identify blocks of the Windows pagefile, and excludes these blocks from processing. Windows page files are dynamic in their nature and change intensively between backup job runs, even if VMs do not change much. Therefore, page file processing results in reduced backup performance and increased size of backup increments. |
Clear the Exclude swap file blocks from processing check box if Windows page files should be processed during backup.
|•||In the VM retention section, specify the number of days to keep backup data for deleted VMs. If a VM is no longer available (for example, it was deleted or moved to another location), Veeam Backup & Replication will keep its data in the backup for the period you specify in the Remove deleted VMs data from backup after field. When this retention period is over, data of the deleted VM will be removed from backup files. The retention period for deleted VMs is particularly useful if the job is configured to create synthetic full backups with subsequent transform and you want to make sure that the full backup does not include redundant data. To learn more, see Retention Policy for Deleted VMs.|
|•||Select the Run the following command check box if you want to execute post-backup actions (for example, to launch a script recording the resulting backup file to tape). Use the Browse button to select an executable file.|
You can select to execute post-backup actions after a number of backup cycles or on specific week days. If you select the Run every... backup cycle option, specify the number of the backup job run after which the file should be executed. If you select the Run on selected days only option, click the Days button and specify week days when actions should be performed.
Storage integration settings
On the Storage Integration tab, define whether you want to use the Backup from Storage Snapshots technology or not. Backup from Storage Snapshots lets you leverage HP SAN snapshots for VM data processing. The technology dramatically improves RPOs and reduces impact of backup activities on the production environment.
By default, the Use storage snapshots option is enabled. If you do not want to use the Backup from Storage Snapshots technology, clear the check box. To learn more, see Performing Backup from Storage Snapshots.