Skip to main content

Azure Blob Storage Error Codes

This topic lists the errors that you may encounter during backup and restore of Azure Blob Storage.

Updated today

AZURE_BLOB 1000

Error Message: Internal Error

Error Description: This is an internal error.

Error Solution: Download job logs and contact Support.

AZURE_BLOB 1010

Error Message: Failed to fetch credentials.

Error Description: This error occurs when the services principles cant be fetched from the customer's tenant either due to network issues or incorrect app registration.

Error Solution

  • Validate if the service principal is created correctly with valid permissions.

  • Retrigger job.

AZURE_BLOB 1012

Error Message: Failed to connect to Azure container.

Error Description:

This error could occur due to one of the following reasons:

  1. Invalid subscription ID, storage account name, or container name.

  2. Invalid service principal.

Error Solution

  • Validate if the service principal is created correctly with valid permissions. Download job logs and contact Support.

  • Validate that the container name is valid and Druva has the necessary permissions to access it.

AZURE_BLOB 1016

Error Message: Failed to fetch container list.

Error Description: This error could occur due to one of the following reasons:

  1. Invalid storage account/resource-group name.

  2. Restricted network access to storage account.

  3. Permission issues over storage account/resource group.

Error Solution

  • Check storage account/resource group.

  • Check for any network restrictions over the storage account like Disabled public access.

  • Sync the Azure subscription again.

AZURE_BLOB 1024

Error Message: Failed to connect to Azure storage account.

Error Description: The error could occur due to one of the following reasons:

  1. Invalid subscription ID or storage account name.

  2. Invalid service principal.

Error Solution

  • Validate if the subscription ID and storage account name are correct.

  • Validate if the service principal is created correctly with valid permissions.

AZURE_BLOB 1030

Error Message: Failed to initiate backup due to misconfigured content rules.

Error Description: This could happen if there is no content to backup. Could be because of the following reasons:

  • All included container paths specified for backup are invalid.

  • Conflicting include and exclude paths. Eg: [ include: cont1/folder1 exclude: cont1 ]

Error Solution

  • Check if the container names provided are valid.

  • Resolve conflicting include and excludes rules.

AZURE_BLOB 1031

Error Message: No files restored.

Error Description: This error occurs if no data is restored. This could happen due to one of the following reasons:

  1. An empty folder/container was restored.

  2. Original location restore triggered with always skip option and all files already exist.

  3. Original location restore triggered with overwrite if older but all existing files are newer.

Error Solution

  • Validate whether the restore options are correctly set.

  • Check the source list (eg: empty folder/container).

AZURE_BLOB 1033

Error Message: Operation failed due to insufficient permissions.

Error Description: This error occurs if authorization issues are encountered during backup/restore operations.

Error Solution

  • Check for any extra permission checks added over entities provided in the source list for restore jobs and content rules for backup jobs. Eg: container, storage account, or specific files/folders.

  • For restoring to alternate locations, make sure there are no restrictions on creating new containers.

AZURE_BLOB 1036

Error Message: Backup window expired.

Error Description: The scheduled backup window expired.

Error Solution

  • Increase the backup window.

  • Trigger the backup job manually.

Did this answer your question?