In Veeam Backup for Microsoft Azure, worker VMs are responsible for data transfer, including backup and restore operations, maintaining existing backup chains, and following the retention policy.
Default worker configuration is designed to cover most workloads, but sometimes, the worker's configuration must be changed to protect large workloads. To maintain the balance of backup speed and costs of worker VM instances, Veeam Backup for Microsoft Azure uses different worker sizes.
The following worker sizes are recommended:
Profile | Machine Type | Purpose | Backup Speed |
Small | F2s_v2 | for backups of workloads with disks smaller than 100 GiB (default) |
70-85 MB/s |
Medium | F4s_v2 | for disks between 100 GiB and 1 TiB (default) |
90-100 MB/s |
Large | F8s_v2 | for disks over 1 TiB in size, also recommended for initial full backup (default) |
125-140 MB/s |
Archiving | E2_v5 | to handle data tiering (default) |
85-110 MB/s |
By default, the worker VM has a 30 GB disk size, which covers most deployments. The size of the metadata can be calculated according to this formula: 4 KB per 1 MB of backup. The metadata size may vary and is unlikely to be 4 KB since it's the worst-case scenario, but it's recommended to follow this estimation for planning the worker configuration.
For example, if the planned backup chain size is 10 TB, at least 40 GB of free space on the worker disk is needed. Worker data disk size is managed by parameters in the Veeam Backup for Azure REST API per region.
The "Modify Worker Profiles" endpoint must be used to modify the worker's disk size per region.
The following configuration parameters are responsible for this:
/api/{version}/workers/profiles/{regionId} |
Value |
archiveWorkerDataDiskEnabled | "True" / "False" (default) |
archiveWorkerDataDiskSizeInGb | 32 |
normalWorkerDataDiskEnabled | "True" / "False" (default) |
normalWorkerDataDiskSizeInGb | 32 |
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case