This article contains a collection of errors that are commonly encountered in backing up and restoring Azure Virtual Machines. Use the Suggested action column to assist in troubleshooting.
Note: If you are looking for information about the known issue where Azure VM files are not available for recovery with InstantData, see Article 1557.
- For a guide to backing up and recovering Azure VMs, see Article 1372 - How to manage your Azure VM backups.
- For more information, see Article 1526 - Azure backup and recovery: frequently asked questions.
Common Azure VM Pro errors
| Error description | Error message example | Suggested action |
|
Adding a VM or storage account resource fails with error "Could not deploy appliance" |
Could not deploy appliance Code: Authorization_RequestDenied Message: insufficient privileges to complete the operation. |
Check the Azure subscription permissions on the Azure user account. In your Azure subscription, your account must have Microsoft.Authorization/*/Write access to assign a role to an Active Directory app. This action is granted through either the Owner role or the User Access Administrator role. |
| Adding a VM fails with error "group capacity limit reached" |
400 BadRequest – {“Limit”[Cannot create Backup Account ‘x’: group capacity limit reached”]} |
Request a capacity increase from your service provider. |
| Adding a VM fails with error "does not have authorization to perform action" | Exception while executing function: AddMachines The client 'x' with object id 'y' does not have authorization to perform action 'Microsoft.Compute/virtualMachines/ read' over scope '/subscriptions/z' or the scope is invalid. If access was recently granted, please refresh your credentials. | Ensure that your Azure service principal has all three of the following roles: Disk Snapshot Contributor, Network Contributor and Virtual Machine Contributor. See Article 1412 for help. |
| Restoring (reverting) a VM fails with error "does not have permission to perform action on the linked scope(s)" | The client 'x' with object id 'y' has permission to perform action 'Microsoft.Compute/virtualMachines/write' on scope 'z'; however, it does not have permission to perform action 'read' on the linked scope(s) or the linked scope(s) are invalid. | This happens when the VM you are attempting to restore (revert) has a golden image or any form of disk attached to it that is located in a different resource group than the VM (the "scope") itself. To resolve this, detach the disk from the VM and retry the recovery. Alternatively, grant the necessary permissions to perform the action by adding the Contributor role to the Redstor Service Principal (usually named Redstor Azure Management followed by a GUID) for the relevant subscription in Azure. |
|
VM backup shows error "Payload stream retry limit reached" |
{"Duration":x,"TransferSize":y,"Issues": ["Payload stream retry limit reached"]} | No user action is required. This happens when the backup times out on a payload request to the Storage Platform. If the maximum number of retry attempts is reached, this error is shown. However, the connection is then rebuilt after a few minutes and the backup proceeds. |
|
Attempting to recover with InstantData leads to error "Response status code |
Could not start InstantDataTemporary: Response status code does not indicate success: 404 (WebLaunch session xxxx-xxxxxxx is invalid or has timed out.). |
This can happen if multiple recoveries are attempted with the same executable. For security purposes, a downloaded InstantData agent can only be run once. Also ensure that you are running the executable as an Administrator. |
Comments
0 comments
Article is closed for comments.