Problem Description
MS-SQL Server backup jobs fail continuously with the following error message displayed in the Druva console: "License expired or the server is busy processing another job"
Symptoms
SQL backup jobs fail consistently with the license/busy server error.
The issue persists even though the Druva license is valid and active, and no conflicting backup or restore operations are active on the server.
The total database size within the Druva configured backup set may incorrectly display as
0.00 B.
Cause
This issue occurs when the SQL Server Availability Group (AG) replicas are unhealthy or completely out of synchronization. When replica health breaks down, Druva’s database discovery layer is unable to properly query or resolve the configuration. This failure bubbles up to the management console as a generic and misleading licensing or resource constraint error.
Traceback
Reviewing the Druva Hybrid Workloads agent logs (PhoenixSQLAgent.log or equivalent helper traces) yields warnings similar to the following during the discovery phase:
level=warn ts=[Timestamp] filename=helper.go:469 layer=discovery message="Replica with name [Replica_Name_1] is not healthy, backups may fail. Please make sure the replica is healthy and database(s) are synchronized."
level=warn ts=[Timestamp] filename=helper.go:469 layer=discovery message="Replica with name [Replica_Name_2] is not healthy, backups may fail. Please make sure the replica is healthy and database(s) are synchronized."
Resolution
To resolve this error, the health state of the underlying Microsoft SQL Server Availability Group must be restored before forcing a refresh in Druva.
Restore SQL Availability Group Health
Open SQL Server Management Studio (SSMS) and check the Always On High Availability dashboard.
Identify the degraded or unsynchronized secondary/primary nodes.
Resume data movement or rejoin the impaired databases to ensure the AG status returns to Healthy / Synchronized.
Verify the VSS Writer State
Log into the affected Windows Server host nodes.
Open a Command Prompt as an Administrator and check the state of the VSS writers:
vssadmin list writers
Ensure that the SqlServerWriter is present, displays
State: [1] Stable, and shows no errors. If needed, ensure theSQL Server VSS Writerservice is running viaservices.msc.
Force Database Discovery in Druva
Log into the Druva Management Console.
Navigate to your Protect > MS-SQL servers.
Select the affected SQL Server host/cluster.
Click Discover Databases to force the Druva agent to re-map the healthy Availability Group layout.
Test the Backup
Select the affected backup set and click Backup Now to trigger an on-demand job and verify resolution.