Skip to main content

Error Codes for Azure virtual machines

Updated this week

PHOENIX190

Error Message: Backup window expired

Error Description: This error occurs if the backup window expires while processing a job .

Error Solution: Retrigger the backup job.

PHOENIX410

Error Message: Initial attempt failed, Phoenix 410 error.

Error Description: It appears that the VM is using unmanaged disks. Currently, we do not support unmanaged disks, since Microsoft plans to end support for unmanaged disks.

To check for unmanaged disks:

  • Navigate to your Microsoft Azure console.

  • Locate your VM's disks. You can then identify disks with VHD files attached.

Error Solution: You will need to migrate the disks to managed disks, as recommended by Microsoft.

Alternative Cause: The create snapshot operation for the Azure VM has failed with the following exception displayed by Microsoft Azure

Resource 'druva-xxxxx-xxxxx-xxx-0' was disallowed by policy

Error Solution: Alternatively, attempt the following:

  1. Navigate to the policy:

    • Go to the Customer's Azure Account and search for "Policy."

    • Select the affected subscription.

    • Locate the specific policy and make the necessary changes to ensure the VM is able to create the snapshot (possibly remove the policy).

  2. Create a manual snapshot:

    • After making the changes, attempt to create a manual snapshot from your Azure console, and observe the behavior.

  3. Run a backup:

    • If the manual snapshot is successful, run a backup on your management console. It should now be able to take a snapshot.

If the problem persists, contact Support for further assistance.

AZURE1

Error Message: Internal error

Error Description: This error occurs when there is an internal error during the operation.

Error Solution: Contact Support.

AZURE7

Error Message: Access SAS expired

Error Description: This error occurs when you connect to the VM for backup.

Error Solution: Retry connecting to the VM. If the issue persists, contact Support.

AZURE8

Error Message: Access SAS not active

Error Description: This error occurs when you connect to the VM for backup.

Error Solution: Retry connecting to the VM. If the issue persists, contact Support.

AZURE9

Error Message: Invalid Restore Param: Disk Name already exists

Error Description: This error occurs when the disk name provided during the restore already exists.

Error Solution: Provide a unique disk name and retry restore.

AZURE61452

Error Message: Deployment quota exceeded

Error Description: This error occurs when you get quota issues while creating resources in the Azure account.

Error Solution: Increase the quota for the resource and retry the operation.

AZURE61482

Error Message: Operation not allowed

Error Description: This error occurs when you get quota issues while creating resources in the Azure account.

Error Solution: Increase the quota for the resource and retry the operation.

AZURE61496

Error Message: Resource quota exceeded

Error Description: This error occurs when you get quota issues while creating resources in the Azure account.

Error Solution: Increase the quota for the resource and retry the operation.

AZURE61502

Error Message: Subnets not in same Vnet

Error Description: This error occurs when the subnet selected for the VM restore is not in the same Vnet.

Error Solution: Correct the mapping of subnet and Vnet and retry.

AZURE61503

Error Message: Subnet is full

Error Description: This error occurs when the selected subnet does not have free space.

Error Solution: Terminate VMs in the subnet or user a different subnet for VM restore.

AZURE61732

Error Message: The specified resource already exists

Error Description: This error occurs when the resource name already exists in the resource group.

Error Solution: Specify a unique name for the resource (VM name, disk name, etc.) while attempting a restore.

AZURE62005

Error Message: The previous snapshot query parameter value cannot be newer than snapshot query parameter value

Error Description: This error may occur during parallel backup of the same VM.

Error Solution: Retrigger the backup job.

Did this answer your question?