Creating VM Backup Jobs
In Veeam Backup & Replication, backup is a job-driven process. To back up VMs, you must configure a backup job. The backup job defines how, where and when to back up VM data. One job can be used to process one or several VMs.
Veeam Backup & Replication backs up a VM image as a whole: it copies VM data at a block level unlike traditional backup tools that process guest OS files separately. Veeam Backup & Replication retrieves VM data from the source storage, compresses and deduplicates it and writes to the backup repository in Veeam’s proprietary format. You can use the image-level backup for all types of data restore scenarios: restore a full VM, VM guest OS files and folders, VM files and VM virtual disks (for VMware VMs only) from the backup file.
Veeam Backup & Replication conducts both full and incremental backup. During the first run of a backup job, Veeam Backup & Replication creates a full VM backup (VBK). All subsequent job cycles produce incremental backups: VIB if forward incremental backup is used or VRB if reversed incremental backup is used. The number of increments kept on disk depends on retention policy settings.
This section describes only basic steps that you must take to create a VM backup job targeted at a cloud repository. To get a detailed description of all backup job settings, see the Creating Backup Jobs section in the Veeam Backup & Replication User Guide.
To create a backup job:
- On the Home tab, click Backup Job and select Virtual machine > VMware vSphere or Virtual machine > Microsoft Hyper-V.
- At the Name step of the wizard, specify a name and description for the backup job.
- At the Virtual Machines step of the wizard, click Add and select VMs and VM containers that you want to back up. To quickly find the necessary object, use the search field at the bottom of the Add Objects window.
- If you want to exclude VMs from the VM container or back up only specific VM disks, click Exclusions and specify what objects you want to exclude.
- At the Storage step of the wizard, from the Backup repository list, select the cloud repository to which you plan to store the backup file.
- In the Retention policy field, specify how many restore points you want to keep on the cloud repository. To do this, in the Retention policy field, specify the number of restore points or the number of days for which you want to store backup files on the cloud repository. If you want to use the GFS (Grandfather-Father-Son) retention scheme, you can also specify how weekly, monthly and yearly full backups must be retained.
- Click Advanced.
- On the Backup tab, select what type of the backup chain you want to create: forward incremental or reverse incremental. You can also choose to periodically create synthetic full backups (for the forward incremental backup method only) and active full backups.
The reverse incremental backup method is not recommended for backup jobs targeted at the cloud repository. The process of a full backup file rebuild requires higher I/O load. This may impact the backup job performance, especially in case of low bandwidth or high latency network connection between the tenant side and SP side. To learn more, see Veeam Backup & Replication Best Practices.
- To encrypt the resulting backup file on the cloud repository, on the Storage tab, select the Enable backup file encryption check box. From the Password field, select a password that you want to use to encrypt the backup file. If you have not created a password beforehand, click Add or use the Manage passwords link to specify a new password.
Starting from Veeam Backup & Replication 12.1 (build 22.214.171.1241), you can select a Key Management System (KMS) server in the Password field. The KMS server must be added to Veeam Backup & Replication in advance. If you choose to use KMS keys for backup file encryption at this step of the wizard, Veeam Backup & Replication immediately starts communication with the KMS server to retrieve the encryption keys. To learn more, see the Key Management System Keys section in the Veeam Backup & Replication User Guide.
- To create a transactionally consistent backup of VMs, at the Guest Processing step of the wizard, select the Enable application-aware processing check box.
- Click Add next to the Guest OS credentials list and specify credentials for a user account with local administrator privileges on the VM guest OS. By default, Veeam Backup & Replication uses the same credentials for all VMs added to the job. If some VM requires a different user account, click Credentials and enter custom credentials for the necessary VM.
- Click Applications, select the necessary VM and click Edit. On the General tab, in the Applications section, specify the VSS behavior scenario:
- Select Require successful processing if you want Veeam Backup & Replication to stop the backup process if any VSS errors occur.
- Select Try application processing, but ignore failures if you want to continue the backup process even if VSS errors occur. This option is recommended to guarantee completion of the job. The created backup image will not be transactionally consistent, but crash consistent.
- Select Disable application processing if you do not want to enable quiescence for the VM at all.
- [For Microsoft SQL, Oracle and PostgreSQL VMs] In the VSS Settings section, specify how Veeam Backup & Replication must handle database logs:
- Select Process transaction logs with this job if you want Veeam Backup & Replication to handle Microsoft SQL Server transaction logs or Oracle archived logs. With this option enabled, Veeam Backup & Replication will offer a choice of log processing options on the SQL and Oracle tabs.
- Select Perform copy only if you use native application means or a third-party tool to process transaction logs. Veeam Backup & Replication will create a copy-only backup for the selected VM. The copy-only backup preserves a chain of full/differential backup files and transaction logs. To learn more, see Microsoft documentation.
You cannot enable log backup options in the properties of a backup job targeted at the cloud repository. For Microsoft SQL Server, you can enable transaction log truncation options only. For Oracle, you can choose whether to delete archived logs.
If you want to store database log backups in the cloud repository, you can do the following:
- At the Schedule step of the wizard, select the Run the job automatically check box and specify the necessary scheduling settings for the job. If you do not select this check box, you will have to run the backup job manually to create a backup file in the cloud.
- At the Summary step of the wizard, select the Run the job when I click Finish check box if you want to start the created job right after you complete working with the wizard.
- Click Finish.