Guidelines for Mass Instant Recovery to Azure
| KB ID: | 4764 |
| Product: | Veeam Backup & Replication | 13 |
| Published: | 2025-09-11 |
| Last Modified: | 2025-12-30 |
Challenge
When attempting to perform mass recovery using Instant Recovery to Azure, the restore fails with the following error messages, which may be found within the UI and logs:
Specific error messages:
-
TooManyPendingCreatAccountOperations
-
TooManyRequests
Generic error messages:
-
The request failed due to an internal error
-
The request wasn't completed in time. Cannot validate argument on parameter 'parameter_name'. The argument is null", If the restore was started using PowerShell cmdlets
Cause
When this occurs, the restore settings and Veeam Backup & Replication configuration must be adjusted for mass recovery.
The following factors may cause a mass restore to fail:
- Many Azure resources are created during the restore process, which may lead to Azure API throttling and subsequent restore failures.
- By default, restore jobs create temporary Azure storage accounts.
The rate at which storage accounts can be created is limited, which may result in restore job failures. - Mass recovery generates additional peak load on the backup server.
- Both restored VMs and temporary helper appliance VMs require sufficient CPU quotas and available IP addresses.
Solution
Mass Restore Preparation and Considerations
Start preparations for mass restore by checking the latest version of these documents:
Azure Resources Created During Restore
To reduce the number of Azure resources created during each restore, select existing resources whenever possible. This helps prevent Azure API throttling, which may cause restore failures.
Avoid creating temporary storage accounts during restore, as the rate at which storage accounts can be created is additionally limited.
CPU Quotas and IP Addresses
Each restore workload requires a temporary helper appliance VM, which runs until the restored workload completes the switchover phase and becomes a regular Azure VM.
Each helper appliance requires:
- CPU cores — By default, appliances use the Standard_D4lds_v5 VM size, consuming 4 CPUs from the Dldsv5 series.
The VM size can be adjusted; for more details, see: https://helpcenter.veeam.com/docs/vbr/userguide/ha_template_change_size.html - One IPv4 address in the appliance subnet.
Ensure that the target Azure subscription's CPU quotas are sufficient for both:
- Restored workloads
- Helper appliances
Ensure that the selected subnets have enough available IP addresses in the:
- Production subnet for restored workloads
- Appliance subnet for helper appliances
Overview of Restore Wizard Recommended Settings
- On the Resource Group tab of the restore wizard, select an existing resource group.
- On the Network tab of the restore wizard, select the following options to reduce the number of Azure resources consumed:
- Select an existing network security group. Using the default option ("Empty") will cause a new network security group with default settings for each restored workload.
- Do not assign public IP addresses. Each public IP is an additional Azure resource.
- On the Helper Appliance tab of the wizard, select an existing storage account.
By default, a new temporary storage account will be created for convenience. However, this is not optimal for parallel restores, as Azure limits the rate at which storage accounts can be created. It is not recommended to use this storage account for purposes other than Instant Recovery to Azure. The same storage account can be used for multiple restored workloads.
Although not related to Azure API load, it is highly recommended to select a separate subnet for appliance traffic, as some workloads may fail to boot after restore if this is not configured. Production subnet is selected on the previous page ("Network") of the restore wizard.
Example Start-VBRAzureInstantRecovery PowerShell Script
More Information
- Veeam Backup & Replication: System Requirements
- Veeam Backup & Replication: Instant Recovery to Microsoft Azure - Considerations and Limitations
- Veeam Backup & Replication: Changing Template and Helper Appliance Size
- Veeam Data Platform 13 Recommended Maximums
- Veeam PowerShell Reference: Start-VBRAzureInstantRecovery
- Microsoft Documentation: Sizes for virtual machines in Azure
If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.
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.