Managing Worker Profiles

In this article

    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. The profile of each launched worker instance is selected based on the performed operation and either the total size of virtual disks attached to the processed Azure VM or 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 image-level backups and restoring data if the total disk size of the processed Azure VM or the total size of the processed Azure SQL database is less than 100 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 image-level backups and restoring data if the total disk size of the processed Azure VM or the total size of the processed Azure SQL database is more than 100 GB but less than 1 TB.
    • Large — a profile that Veeam Backup for Microsoft Azure uses for creating image-level backups and restoring data if the total disk size of the processed Azure VM or the total size of the processed Azure SQL database is more than 1 TB.
    • 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 small profile is Standard_F2s_v2, the medium profile is Standard_F4s_v2, the large profile is Standard_F8s_v2, and the archiving 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