AZURE_BLOB 1000
Error Message: Internal Error
Error Description: This is an internal error.
Error Resolution: 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 Resolution:
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:
Invalid subscription ID, storage account name, or container name.
Invalid service principal.
Error Resolution:
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:
Invalid storage account/resource-group name.
Restricted network access to storage account.
Permission issues over storage account/resource group.
Error Resolution:
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:
Invalid subscription ID or storage account name.
Invalid service principal.
Error Resolution:
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 Resolution:
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:
An empty folder/container was restored.
Original location restore triggered with always skip option and all files already exist.
Original location restore triggered with overwrite if older but all existing files are newer.
Error Resolution:
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 Resolution:
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 Resolution:
Increase the backup window.
Trigger the backup job manually.
AZURE_BLOB 1044
Error Message: Failed due to throttling from Azure services
Error Description: This error occurs when Microsoft Azure limits API request rates or data throughput for the storage account during backup operations. Throttling typically happens during initial container discovery or high-volume parallel reads when the storage account exceeds Azure’s standard transaction limits.
Error Resolution:
Adjust Backup Schedules: Stagger backup start times or move the backup window to off-peak hours when production activity on the storage account is lowest
Configure Backup Scope: For storage accounts containing millions of objects, divide the container selections across separate backup sets or policies to reduce total request rates (RPS/TPS) during backup execution.
Request Ingress or Egress Quota Increases: Submit a support request in the Azure portal to increase the storage account's ingress or egress throughput limits if data transfer limits are being breached.
Optional: Upgrade Storage Performance Tier: Standard storage accounts handle most workloads, but upgrading to a Premium Block Blob storage account is an optional Azure-level change that provides higher transaction rates and throughput capacity.
AZURE_BLOB 2001
Error Message: Role assignment not found.
Error Description: This error occurs if the role assignment for the Druva service principal is not found or cannot be accessed.
Error Resolution:
Confirm that the role assignment name matches the role assignment in Azure and that the service principal still has the assignment at the subscription scope.
Verify that the service principal has permissions to perform the read operation.
AZURE_BLOB 2002
Error Message: Resource group not found.
Error Description: This error occurs if the resource group is not found or cannot be accessed.
Error Resolution:
Verify the resource group name and the subscription.
Verify that the service principal has permissions to perform the read operation.
AZURE_BLOB 2003
Error Message: User-assigned managed identity not found.
Error Description: This error occurs if the user-assigned managed identity is not found or cannot be accessed.
Error Resolution:
Check that the managed identity exists in the expected resource group.
Verify that the service principal has permissions to read the managed identity.
AZURE_BLOB 2004
Error Message: Key Vault not found.
Error Description: This error occurs if the primary or secondary Key Vault is missing or cannot be accessed.
Error Resolution:
Verify that both the primary and secondary Key Vaults exist.
Verify that the service principal has permissions to read the Key Vault resources.
AZURE_BLOB 2005
Error Message: Custom role definition not found.
Error Description: This error occurs if the custom role definition linked to the role assignment is not found or cannot be accessed.
Error Resolution:
Re-create or restore the Druva custom role.
Re-run onboarding so that the role definition and the role assignment stay in sync.
Verify that the service principal has permissions to perform the read operation.
AZURE_BLOB 2006
Error Message: Authorization failed while reading the resource.
Error Description: This error occurs if Azure returns an authorization or forbidden error while Druva reads a resource during the pre-check.
Error Resolution:
Ensure that the service principal is assigned the RBAC roles required for the onboarding pre-check. The roles must provide sufficient permissions to read the resource group, managed identity, Key Vault, and role assignments. For more information, see permissions.
AZURE_BLOB 2007
Error Message: Custom role is missing required permissions.
Error Description: This error occurs if the custom role exists but does not include the actions or data actions that the workload requires.
Error Resolution: Update the custom role with the permissions required to perform the pre-checks. For more information, see permissions.
AZURE_BLOB 2008
Error Message: Azure custom role version is outdated.
Error Description: This error occurs if the configured Azure custom role version is older than the latest supported version.
Error Resolution: Upgrade the Azure custom role to the latest version by using the Update Tenant registration workflow.
AZURE_BLOB 2009
Error Message: No blob containers found in the storage account.
Error Description: This error occurs if the storage account has no blob containers, or if the list or get operation for containers returns empty or not found.
Error Resolution: Create at least one blob container in the storage account that you want to back up.
AZURE_BLOB 2010
Error Message: Included containers not found in the storage account.
Error Description: This error occurs if the storage account has containers, but none of the container names specified in the include list exist in the storage account.
Error Resolution:
Update the backup content selection to include the names of existing containers.
Alternatively, create the containers that are listed in the include list.
AZURE_BLOB 2011
Error Message: Some included containers not found in the storage account.
Error Description: This error occurs if only some of the container names specified in the include list exist in the storage account (partial match).
Error Resolution:
Remove or correct the invalid container names in the include list.
Alternatively, create the missing containers in Azure.
AZURE_BLOB 2012
Error Message: Azure Resource Manager (ARM) API request throttled.
Error Description: This error occurs if the Azure ARM API throttles requests while Druva runs the pre-checks.
Error Resolution: Wait for some time and retry the pre-checks.
AZURE_BLOB 32884
If you encounter this error, see Troubleshoot Network Configuration Issues for Azure Storage Accounts.