Managing Worker Profiles

A profile is the VM size of a worker instance that Veeam Backup for Microsoft Azure launches in a specific Azure region to perform a backup, restore, health check, indexing or archive operation. Veeam Backup for Microsoft Azure launches one worker instance per each Azure resource added to a backup policy or restore task. When configuring worker profiles, you can use the default set of worker profiles, or select VM size of each worker profile based on the performed operations and the total size of virtual disks attached to the processed resource. The profile of each launched worker instance is selected based on the performed operation, and either on the total size of virtual disks attached to the processed Azure VM or on the total size of the processed Azure SQL database.

There are 4 types of worker profiles in Veeam Backup for Microsoft Azure:

Small — a profile that Veeam Backup for Microsoft Azure uses for creating backups and restoring data if the total disk size of the processed Azure VM is less than 100 GB, or the total size of the processed Azure SQL database is less than 1 GB. This profile is also used to launch worker instances for file-level recovery, backup retention, file share indexing and health check operations.
Medium — a profile that Veeam Backup for Microsoft Azure uses for creating backups and restoring data if the total disk size of the processed Azure VM is more than 100 GB but less than 1 TB, or the total size of the processed Azure SQL database is more than 1 GB but less than 50 GB.
Large — a profile that Veeam Backup for Microsoft Azure uses for creating backups and restoring data if the total disk size of the processed Azure VM is more than 1 TB or the total size of the processed Azure SQL database is more than 50 GB.
Archiving — a profile that Veeam Backup for Microsoft Azure uses for creating archived backups.

Out of the box, Veeam Backup for Microsoft Azure comes with the default set of worker profiles where the backup profile is Standard_F2s_v2 and the archive profile is Standard_E2_v5. However, to boost operational performance, you can add custom sets of worker profiles to specify VM sizes of worker instances that will operate in different regions.

In This Section