Problem Description
SQL Full or Differential backups triggered through Druva Phoenix fail with the following error:
Phoenix SQL agent found no instance/database on the server to backup or the SQL service is not running or the backup content is set to exclude all the databases. (#100030006) (Error Code: SQL6)
This error indicates that the Phoenix SQL Agent was unable to identify any eligible databases for backup on the SQL Server.
Cause
This issue is commonly caused by corruption in SQL Server system metadata or indexing, particularly within the msdb database.
The Phoenix SQL Agent executes a standard SQL query to fetch backup metadata.
Due to index or metadata corruption, the query fails or returns no results.
As a result, the agent assumes:
No databases are available for backup, or
SQL services are not running, or
All databases are excluded
Verification
Follow the steps below to validate the issue:
1. Verify Backup Configuration
Ensure that the backup set does not exclude all databases
Confirm that:
SQL Server services are running
The SQL instance is properly detected in Druva
2. Review Backup Logs
Check the Phoenix logs for errors similar to:
[ERROR] Error in executing SQL Query:
select database_name Collate SQL_Latin1_General_CP1_CS_AS, max([backup_start_date])
from [msdb].[dbo].[backupset]
where type='D'
and is_copy_only=0
group by database_name Collate SQL_Latin1_General_CP1_CS_AS;
SyncError: Phoenix SQL agent found no instance/database on the server to backup...
(Error Code: SQL6)
3. Execute the SQL Query Manually
Run the following query in SQL Server Management Studio (SSMS):
select database_name Collate SQL_Latin1_General_CP1_CS_AS, max([backup_start_date])
from [msdb].[dbo].[backupset]
where type='D'
and is_copy_only=0
group by database_name Collate SQL_Latin1_General_CP1_CS_AS;
Expected Result:
The query should return backup metadata
If the query fails or returns no data:
Indicates a metadata access issue or indexing corruption
4. Check Windows Event Viewer
Review Application and System logs
Look for SQL Server or disk-related errors
(Note: In some cases, no relevant errors may be logged.)
5. Run Database Integrity Check
Execute:
DBCC CHECKDB (msdb)
If corruption is reported, it confirms an issue within the system database
In some cases, DBCC CHECKDB may not fully resolve the issue
Resolution
Step 1: Confirm the Root Cause
Ensure backup configuration is valid
Confirm SQL services are running
Validate query failure against msdb
Step 2: Fix Index / Metadata Corruption
Engage the SQL Database Administrator to:
Rebuild or repair corrupted indexes in msdb
Use appropriate methods such as:
Index rebuild/reorganization
DBCC DBREINDEX (for older SQL versions)
Dropping and recreating affected indexes (if required)
Step 3: Re-run Backup
Trigger the backup again from the Druva console
Monitor logs to confirm successful execution
Additional Recommendations
Ensure the Phoenix SQL Agent has proper permissions on:
msdb database
Required system tables
Perform regular SQL maintenance:
Index maintenance
Integrity checks (DBCC CHECKDB)
Periodically validate backup metadata queries to detect early issues