Azure Files Backups Fail with Quantum Bridge VM Provisioning Errors

Problem description

Scheduled Azure Files backup jobs that were previously functioning normally suddenly fail during the initialization phase. The Druva Management Console displays failed backup jobs for Azure workloads, specifically pointing to unexpected environment errors when attempting to spin up the transient infrastructure needed for data transfer.

Cause

The failure occurs because the target Azure subscription has reached its Total Regional Cores quota limit or specific VM family vCPU limits within the designated deployment region.

Druva's Quantum Bridge architecture dynamically provisions ephemeral VM instances to safely process and isolate data inside the customer's security boundary. The compute configurations dynamically scale based on the specific phase of the backup cycle:

Initial Full Backups / Restores: Demand higher performance scaling, requiring 32 vCPUs per backup set (utilizing sizes such as Standard_D32ls_v5, Standard_F32s_v2, or Standard_D32s_v5).
Incremental Backups: Require 16 vCPUs per backup set (utilizing sizes such as Standard_D16ls_v5, Standard_D16s_v5, or Standard_F16s_v2).

If the concurrent execution of multiple jobs requires more vCPUs than are currently available under the subscription's regional Azure quota constraints, the Azure Resource Manager (ARM) API rejects the deployment request, causing the backup job to fail at the provisioning state.

Traceback

Plaintext

Error Code: cloud.azure.provisioning_failed Severity: ERROR Description: Failed to provision the Quantum Bridge infrastructure in the customer subscription.  Details: Operation results in exceeding quota limits of Core. Current Limit: X, Current Usage: Y, Additional Required: Z. Please contact Azure support to increase the Quota for the required VM family.

Resolution

Option 1: Request an Azure Quota Increase (Recommended)

To support overlapping or concurrent scheduled backups, increase the compute limits directly inside the Microsoft Azure portal:

Log in to the Azure Portal.
Search for and navigate to Quotas using the global search bar, then click on Compute.
Select your target deployment Region.
Locate the Total Regional vCPUs limit as well as the specific VM families utilized by the Quantum Bridge infrastructure (e.g., Standard DSv5 Family vCPUs or Standard FSv2 Family vCPUs).
Click Request an increase, enter the new desired value based on your concurrent backup requirements, and submit the request.

Option 2: Adjust Backup Policies & Scheduling (Workaround)

If an immediate Azure quota increase is not feasible, you can remediate the peak vCPU bottlenecks by staggering your workloads:

Log in to the Druva Management Console.
Divide large, overlapping backup sets into two or more separate backup policies.
Modify the policy execution windows to clear any concurrent runtime schedules. Staggering the start times prevents multiple Quantum Bridge VMs from scaling up simultaneously, keeping cumulative vCPU usage safely below your existing Azure infrastructure cap.

Include and exclude filters

Include Filters: Applies to cloud-native protection policies for Azure Files and Azure Blob Storage running within restricted network environments that depend on ephemeral Quantum Bridge VMs.
Exclude Filters: Does not apply to standard hybrid file server agents, NAS proxies, or AWS native workloads that do not leverage automated Azure ARM compute provisioning.

Verification

To verify that the issue has been successfully resolved:

Navigate to the Druva Management Console and select the impacted Azure workload.
Manually trigger an on-demand backup execution or wait for the next staggered schedule cycle to initiate.
Monitor the job progress to confirm that the environment provisioning step bypasses previous thresholds.
Verify the job completes with a status of Success.
(Optional) Confirm in your Azure Portal Activity Logs that the Microsoft.Compute/virtualMachines/write operations complete successfully without yielding quota validation errors.