#1 Global Leader in Data Resilience

Veeam Backup for Microsoft Azure Worker Size Information

KB ID: 4395
Product: Veeam Backup for Microsoft Azure
Published: 2022-12-21
Last Modified: 2023-02-07
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Purpose

This article documents information regarding the Veeam Backup for Microsoft Azure worker size and configuration.

Solution

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
Swipe to show more of the table

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
Swipe to show more of the table
These parameters are hidden and not mentioned in REST API Reference. It is strongly recommended to contact Veeam Technical Support for assistance.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.