Configuring jobs in VBR

Configure a local job

To configure a job in the customer’s VBR, go to the Home section and choose Backup Job. Here you can choose the type of backup you’d like to create. In our example, we’ll backup a Virtual Machine.

image-1610726889242.png

Give the job a name, it can be anything, but it’s practical to choose something meaningful e.g. the name of the VM you’ll backup.

image-1610726900988.png

To choose the machine(s) you want to backup, click on Add and browse the servers that are available on your hypervisor. Select the server(s) you need, click on Add again, then on Next to go on with the wizard.

image-1641983936943.png

The default repository after a Veeam install is on the computer's C:\ drive, but it is not supported to do backups there. You need to create repositories on system-independent storages e.g. on a NAS or on a separate disk. To see how, click here.

If you click the Advanced button, you can choose special settings, e.g. if you want to create incremental or reverse incremental backups, or how often you want to create an active full backup. More about this can be read in the Veeam knowledgebase. https://helpcenter.veeam.com/docs/backup/vsphere/backup_methods.html?ver=100

image-1610726942005.png

Our recommendation is that if you specify less than 15 restore points, create synthetic full backups periodically to shorten the restore times (in case you need one). If you need to specify more than 15 restore points, there's a chance full backups will fill up your repository, so it's more advisable to go with forever forward incrementals. (More about the different job types here.)

image-1641984222713.png

On the Maintenance tab tick in Perform backup files health check - this will help in preventing the backup files to be corrupted.

image-1641984356166.png

On the Storage tab, you can choose the compression level. The higher the compression level, the greater load is on the source computers CPUs BUT the backup sizes become smaller. Choose the one appropriate to your scenario.

image-1626876192571.png

Under storage optimization choose the appropriate settings depending on the destination of your backups. In this scenario, we are backing up to a local storage, so Local  target is what we need to choose. Review the table here to get more information.

image-1626876209484.png

Enable encryption if it is required by the customer. 

Caution: store the password securely because it will be needed in case of a restore. If you lose it, we cannot recover it.

image-1626876249589.png

Click Apply when all the required configurations are done.

Still under the Retention policy section of the wizard: in case you need GFS backup, tick in Keep some periodic full backups longer for archival purposes. These backups are created weekly / monthly / yearly - and they have a different retention policy compared to the one you defined (e.g. a GFS yearly backup is kept for a year, while the normal daily backups are kept for 7 days).

Click configure, and choose the settings that the customer needs.

image-1626876368375.png

On the Guest Processing tab, you can specify if you need Veeam to do something special with the applications and data inside the virtual machine, e.g. index the file system or truncate SQL logs. More on this here: https://helpcenter.veeam.com/docs/backup/vsphere/guest_processing.html?ver=100

For a server running a database, you can truncate logs by enabling application-aware processing.

Caution: use this option ONLY if you are very sure of what you are doing. Using both Veeam SQL backup and native SQL backups will render both of those backups useless! More on SQL backups here. Let us know if you need help in this, we are happy to assist.

image-1610726957549.png

On the next tab, you can choose a schedule for automatic processing, if you want your backup to run periodically.

image-1610726971722.png

If you need to use a backup window i.e. the backups can run during specific times e.g. only at night, tick in Terminate the job if it exceeds allowed backup window

image-1626880271598.png

Click on Window...

Mark the times when you don't want the job to run > if the small squares are grayed out, it means the job won't run during those times.

Click OK

image-1626880296007.png

Click Next.

On the Summary tab, review your configuration and click Finish to finalize the backup job settings. Optionally, you may tick in the “Run this job when I click Finish”, and the job will start right away.

image-1610726983643.png

Create a backup job to the cloud (to the VCC server)

For this step to work, you need to have an already configured connection to your SP. Check the “Service Provider Configuration in Veeam Backup and Replication Console” chapter for details.

To set up a new backup job that will save the VMs into the cloud, just do everything the way you’d normally do to set up a job (Configure a local backup job in VBR), but on the Storage tab of the Backup Job wizard, specify a Cloud repository existing in the SP’s VCC server (off-site). This is the same repository that you chose when you sat up the company of the customer in the SP Console.

image-1610727168910.png

Caution: 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. 

image-1626881277879.png

Create a backup copy job

You can also create a normal local backup first which would be followed by a cloud backup, basically the local backup is copied into the VCC server.

On the local VBR install, go to Storage Infrastructure > Backup Copy > Virtual machine…

image-1610727196706.png

Give the job a name, and choose the mode. Immediate to copy all local restore points to the cloud, Periodic copy if you want to copy only the last restore point.

image-1610727224859.png

As an object, choose the already existing backup job to start from, OR the machine you want to backup.

image-1610727240607.png

Choose the Customer’s repository that’s in the cloud.

image-1610727309080.png

Click the Advanced button to set some extra configuration

On the Maintenance tab tick in Perform backup files health check - this will help in preventing the backup files to be corrupted.

image-1626876853386.png

On the Storage tab, you can choose the compression level. The higher the compression level, the greater load is on the source computers CPUs BUT the backup sizes become smaller. Choose the one appropriate to your scenario - or if you're unsure, leave it on Auto to let Veeam decide.

image-1626876620160.png

Enable encryption if it is required by the customer. 

Caution: store the password securely because it will be needed in case of a restore. If you lose it, we cannot recover it.

image-1626876249589.png

Click Apply when all the required configurations are done.

Still under the Retention policy section of the wizard: in case you need GFS backup, tick in Keep some periodic full backups longer for archival purposes. These backups are created weekly / monthly / yearly - and they have a different retention policy compared to the one you defined (e.g. a GFS yearly backup is kept for a year, while the normal daily backups are kept for 7 days).

Click configure, and choose the settings that the customer needs.

image-1626876821485.png

Click Next >

If your network speed (upstream) is below 100 Mbit/sec, and your license allows it, enable WAN acceleration. WAN acceleration is available with the Enterprise and Enterprise plus license. Otherwise the option is grayed out. To utilize WAN acceleration please, check this documentation: https://helpcenter.veeam.com/docs/backup/hyperv/wan_add.html?ver=110 

Enterprise license:

image-1626876950430.png

Standard license:

image-1610727332007.png

On the Schedule tab, you can choose Continuously so that the job is waiting for any changes in the “mother” backup job or choose your custom time periods.

image-1610727345389.png

Click Apply > Finish

After finishing the wizard, if you go to Backup Copy Jobs menu, you’ll see that the job is running, but is in a Pending state, saying that the status is Idle. This is because it’s waiting for changes that appear on the backup job, that’s related to it. If a new backup is detected, it will wait until the backup job finishes, and then starts a copy into the cloud.

image-1610727356187.png

If you chose the already existing Job as the backup object, then the local and the cloud job will already be connected. If you chose the VM as the object, now you need to connect the two jobs.

To assign a backup job to the backup copy job, create the backup job, or if it exists, open it and on the storage tab, choose Configure secondary backup destinations. (Note on the screenshot that the target of the backup job itself stays locally, only the secondary location will be in the cloud.)

image-1610727383777.png

New menu points will appear in the wizard where you’ll be able to specify the backup copy job that we created previously.

image-1610727399059.png