#1 Global Leader in Data Resilience

How to Configure the Azure Restore Proxy Appliance Size

KB ID: 4462
Product: Veeam Backup & Replication | 12 | 12.1 | 12.2 | 12.3
Published: 2023-06-20
Last Modified: 2023-06-20
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.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.

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 how to override the default Azure Restore Proxy Appliance size.

Challenge

Attempting to restore a Linux workload fails to Microsoft Azure when using a proxy appliance size that is not available for subscriptions that have VM size limitations.

The following error may be found in:
C:\ProgramData\Veeam\Backup\AzureAppliance.Job.Azure_Helper_Appliance_Deployme.log

The requested VM size for resource 'Following SKUs have failed for Capacity Restrictions: Standard_D2lds_v5' is currently not available in location 'japanwest'. Please try another size or deploy to a different location or different zone. See https://aka.ms/azureskunotavailable for details. (Veeam.Backup.AzureAPI.CAzureWebException)

Cause

The error shown occurs when the helper appliance size Veeam Backup & Replication attempted to create is not available.

When performing Restore to Azure for Linux workloads, a helper appliance is used. That helper appliance's VM size is selected using a sizing algorithm based on the region associated with the Microsoft Azure Compute account. However, the helper appliance deployment may fail if the selected VM size is unavailable for the subscription selected within the Helper Appliance Configuration.

Solution

Veeam Backup & Replication Version Requirement
This solution requires at least Veeam Backup & Replication 12 P20230412 (build 12.0.0.1420 P20230412).
No workaround is available for earlier versions.

The following registry setting overrides the automatic sizing algorithm and uses the specified VM size for the helper appliance.

Create the following registry value on the Veeam Backup Server:

Key: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication
Value Name: AzureApplianceRmVmSizeOverride 
Value Type: String Value (REG_SZ)
Value Data: standard_d2s_v3 (example value, an empty string is the default value)

Notes:

  • No reboot or service restart is required.
  • The setting must be applied before adding the Microsoft Azure Compute account
    If the Azure Compute account has already been added, it must be readded to force redeployment of the helper appliance using the VM size specified.
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.