You can troubleshoot errors encountered while using Azure Backup with information listed in the table below.
|Could not perform the operation as VM no longer exists. - Stop protecting virtual machine without deleting backup data. More details at http://go.microsoft.com/fwlink/?LinkId=808124||This happens when the primary VM is deleted, but the backup policy continues looking for a VM to back up. To fix this error:
|Could not communicate with the VM agent for snapshot status. - Ensure that VM has internet access. Also, update the VM agent as mentioned in the troubleshooting guide at http://go.microsoft.com/fwlink/?LinkId=800034||This error is thrown if there is a problem with the VM Agent or network access to the Azure infrastructure is blocked in some way. Learn more about debugging up VM snapshot issues.
If the VM agent is not causing any issues, then restart the VM. At times an incorrect VM state can cause issues, and restarting the VM resets this "bad state"
|Recovery services extension operation failed. - Please make sure that latest virtual machine agent is present on the virtual machine and agent service is running. Please retry backup operation and if it fails, contact Microsoft support.||This error is thrown when VM agent is out of date. Refer “Updating the VM Agent” section below to update the VM agent.|
|Virtual machine doesn't exist. - Please make sure that virtual machine exists or select a different virtual machine.||This happens when the primary VM is deleted but the backup policy continues to look for a VM to perform backup. To fix this error:
|Command execution failed. - Another operation is currently in progress on this item. Please wait until the previous operation is completed, and then retry||An existing backup on the VM is running, and a new job cannot be started while the existing job is running.|
|Copying VHDs from the backup vault timed out - Please retry the operation in a few minutes. If the problem persists, contact Microsoft Support.||This happens if there is a transient error on storage side or if backup service is not getting sufficient IOPS from storage account hosting the VM in order to transfer data within timeout period to vault. Make sure that you followed Best practices while setting up backup. Try moving VM to a different storage account which is not loaded and retry backup.|
|Backup failed with an internal error - Please retry the operation in a few minutes. If the problem persists, contact Microsoft Support||You can get this error for 2 reasons:
|Failed to install the Azure Recovery Services extension on the selected item - The VM agent is a prerequisite for the Azure Recovery Services Extension. Install the Azure VM agent and restart the registration operation||
|Extension installation failed with the error "COM+ was unable to talk to the Microsoft Distributed Transaction Coordinator||This usually means that the COM+ service is not running. Contact Microsoft support for help on fixing this issue.|
|Snapshot operation failed with the VSS operation error "This drive is locked by BitLocker Drive Encryption. You must unlock this drive from the Control Panel.||Turn off BitLocker for all drives on the VM and observe if the VSS issue is resolved|
|VM is not in a state that allows backups.||
|Azure Virtual Machine Not Found.||This happens when the primary VM is deleted but the backup policy continues to look for a VM to perform back up. To fix this error:
|Virtual machine agent is not present on the virtual machine - Please install any prerequisite and the VM agent, and then restart the operation.||Read more about VM agent installation, and how to validate the VM agent installation.|
|Snapshot operation failed due to VSS Writers in bad state||You need to restart VSS(Volume Shadow copy Service) writers that are in bad state. To achieve this, from an elevated command prompt, run vssadmin list writers. Output contains all VSS writers and their state. For every VSS writer whose state is not " Stable", restart VSS writer by running following commands from an elevated command prompt
net stop serviceName
net start serviceName
|Snapshot operation failed due to a parsing failure of the configuration||This happens due to changed permissions on the MachineKeys directory: %systemdrive%\programdata\microsoft\crypto\rsa\machinekeys
Please run below command and verify that permissions on MachineKeys directory are default-ones:
Default permissions are:
If you see permissions on MachineKeys directory different than default, please follow below steps to correct permissions, delete the certificate and trigger the backup.
|Validation failed as virtual machine is encrypted with BEK alone. Backups can be enabled only for virtual machines encrypted with both BEK and KEK.||Virtual machine should be encrypted using both BitLocker Encryption Key and Key Encryption Key. After that, backup should be enabled.|
|Azure Backup Service does not have sufficient permissions to Key Vault for Backup of Encrypted Virtual Machines.||Backup service should be provided these permissions in PowerShell using steps mentioned in Enable Backup section of PowerShell documentation.|
|Installation of snapshot extension failed with error - COM+ was unable to talk to the Microsoft Distributed Transaction Coordinator||Please try to start windows service "COM+ System Application" (from an elevated command prompt - net start COMSysApp).
If it fails while starting, please follow below steps:
|Failed to freeze one or more mount-points of the VM to take a file-system consistent snapshot||
|Snapshot operation failed due to failure in creating secure network communication channel||
|Snapshot operation failed due to failure in installation of Visual C++ Redistributable for Visual Studio 2012||Navigate to C:\Packages\Plugins\Microsoft.Azure.RecoveryServices.VMSnapshot\agentVersion and install vcredist2012_x64. Make sure that registry key value for allowing this service installation is set to correct value i.e. value of registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Msiserver is set to 3 and not 4. If you are still facing issues with installation, restart installation service by running MSIEXEC /UNREGISTER followed by MSIEXEC /REGISTER from an elevated command prompt.|
|Cancellation is not supported for this job type - Please wait until the job completes.||None|
|The job is not in a cancelable state - Please wait until the job completes.
The selected job is not in a cancelable state - Please wait for the job to complete.
|In all likelihood, the job is almost completed. Please wait until the job is completed.|
|Cannot cancel the job because it is not in progress - Cancellation is only supported for jobs which are in progress. Please attempt cancel on an in progress job.||This happens due to a transitory state. Wait for a minute and retry the cancel operation|
|Failed to cancel the Job - Please wait till job finishes.||None|
|Restore failed with Cloud Internal error||
|The selected DNS name is already taken - Please specify a different DNS name and try again.||The DNS name here refers to the cloud service name (usually ending with .cloudapp.net). This needs to be unique. If you encounter this error, you need to choose a different VM name during restore.
This error is shown only to users of the Azure portal. The restore operation through PowerShell will succeed because it only restores the disks and doesn't create the VM. The error will be faced when the VM is explicitly created by you after the disk restore operation.
|The specified virtual network configuration is not correct - Please specify a different virtual network configuration and try again.||None|
|The specified cloud service is using a reserved IP, which doesn't match with the configuration of the virtual machine being restored - Please specify a different cloud service, which is not using reserved IP, or choose another recovery point to restore from.||None|
|Cloud service has reached limit on number of input end points - Retry the operation by specifying a different cloud service or by using an existing endpoint.||None|
|Backup vault and target storage account are in two different regions - Ensure that the storage account specified in restore operation is in the same Azure region as the backup vault.||None|
|Storage Account specified for the restore operation is not supported - Only Basic/Standard storage accounts with locally redundant or geo redundant replication settings are supported. Please select a supported storage account||None|
|Type of Storage Account specified for restore operation is not online - Make sure that the storage account specified in restore operation is online||This might happen because of a transient error in Azure Storage or due to an outage. Please choose another storage account.|
|Resource Group Quota has been reached - Please delete some resource groups from Azure portal or contact Azure support to increase the limits.||None|
|Selected subnet does not exist - Please select a subnet which exists||None|
|Backup Service does not have authorization to access resources in your subscription.||To resolve this, first Restore Disks using steps mentioned in section Restore backed up disks in Choosing VM restore configuration. After that, use PowerShell steps mentioned in Create a VM from restored disks to create full VM from restored disks.|
Backup or Restore taking time
If you see your backup(>12 hours) or restore taking time(>6 hours), please make sure that you follow Backup best practices. Please also make sure that your applications are using Azure storage in an optimal way for backup.
Setting up the VM Agent
Typically, the VM Agent is already present in VMs that are created from the Azure gallery. However, virtual machines that are migrated from on-premises datacenters would not have the VM Agent installed. For such VMs, the VM Agent needs to be installed explicitly. Read more about installing the VM agent on an existing VM.
For Windows VMs:
- Download and install the agent MSI. You need Administrator privileges to complete the installation.
- Update the VM property to indicate that the agent is installed.
For Linux VMs:
- Install latest from distribution repository. We strongly recommend installing agent only through distribution repository. For details on package name, please refer to Linux agent repository
- For classic VMs, Update the VM property to indicate that the agent is installed
Updating the VM Agent
For Windows VMs:
- Updating the VM Agent is as simple as reinstalling the VM Agent binaries. However, you need to ensure that no backup operation is running while the VM Agent is being updated.
For Linux VMs:
- Follow the instructions on Updating Linux VM Agent. We strongly recommend updating agent only through distribution repository. We do not recommend downloading the agent code from directly github and updating it. If latest agent is not available for your distribution, please reach out to distribution support for instructions on how to install latest agent. You can check latest Windows Azure Linux agent information in github repository.
Validating VM Agent installation
How to check for the VM Agent version on Windows VMs:
- Log on to the Azure virtual machine and navigate to the folder C:\WindowsAzure\Packages. You should find the WaAppAgent.exe file present.
- Right-click the file, go to Properties, and then select the Details tab. The Product Version field should be 2.6.1198.718 or higher
Troubleshoot VM Snapshot Issues
VM backup relies on issuing snapshot commands to underlying storage. Not having access to storage, or delays in a snapshot task execution can cause the backup job to fail. The following can cause snapshot task failure.
- Network access to Storage is blocked using NSG
Learn more on how to enable network access to Storage using either WhiteListing of IPs or through proxy server.
VMs with Sql Server backup configured can cause snapshot task delay
By default VM backup issues VSS Full backup on Windows VMs. On VMs that are running Sql Servers and if Sql Server backup is configured, this might cause delay in snapshot execution. Please set following registry key if you are experiencing backup failures because of snapshot issues.
- VM status reported incorrectly because VM is shut down in RDP.
If you have Shut down the virtual machine in RDP, please check back in the portal that VM status is reflected correctly. If not, please shut down the VM in portal using 'Shutdown' option in VM dashboard.
- If more than four VMs share the same cloud service, configure multiple backup policies to stage the backup times so no more than four VM backups are started at the same time. Try to spread the backup start times an hour apart between policies.
- VM is running at High CPU/Memory.
If the virtual machine is running at High CPU usage(>90%) or memory, snapshot task is queued, delayed and will eventually gets timed-out. Try on-demand backup in such situations.
Like all extensions, Backup extension need access to the public internet to work. Not having access to the public internet can manifest itself in various ways:
- The extension installation can fail
- The backup operations (like disk snapshot) can fail
- Displaying the status of the backup operation can fail
The need for resolving public internet addresses has been articulated here. You need to check the DNS configurations for the VNET and ensure that the Azure URIs can be resolved.
Once the name resolution is done correctly, access to the Azure IPs also needs to be provided. To unblock access to the Azure infrastructure, follow one of these steps:
- WhiteList the Azure datacenter IP ranges.
- Create a path for HTTP traffic to flow
- If you have some network restriction in place (a Network Security Group, for example) deploy an HTTP proxy server to route the traffic. Steps to deploy an HTTP Proxy server can found here.
- Add rules to the NSG (if you have one in place) to allow access to the INTERNET from the HTTP Proxy.
DHCP must be enabled inside the guest for IaaS VM Backup to work. If you need a static private IP, you should configure it through the platform. The DHCP option inside the VM should be left enabled. View more information about Setting a Static Internal Private IP.