Problem description
After successfully activating a server, the SQL discovery process begins. It usually takes a few minutes for the server to appear under the SQL workload page, as the discovery process runs on the client and updates the details in the cloud. However, if Druva fails to detect the SQL instance, the SQL server will not be added to the SQL Server Workload.
Cause
SQL Writers are missing on the SQL Server, leading to a failure in the SQL discovery process.
Traceback
ControlService.log
[2024-06-07 19:26:39,013] [ERROR] SyncError : VSS Writer count mismatch.
[2024-06-07 19:26:39,015] [ERROR] SyncError: Required writers count for VSS operation is not correct, current writer count = 0, required writer count = 1
[2024-06-07 19:26:39,015] [ERROR] Error in Executing sql discovery
[2024-06-07 19:26:39,015] [ERROR] Error <class 'inSyncLib.inSyncError.SyncError'>:Required writers count for VSS operation is not correct, current writer count = 0, required writer count = 1 (#10004000a) (Error Code : VSS10). Traceback -Traceback (most recent call last):
.
SyncError: Required writers count for VSS operation is not correct, current writer count = 0, required writer count = 1 (#10004000a) (Error Code : VSS10)
Resolution
Verify VSS Writers:
Open a Command Prompt with administrative privileges.
Run the command
vssadmin list writersto check the status of all VSS writers.If the "SQL Server VSS Writer" is not listed or shows an error, restart the service through
services.msc.If the problem persists, reinstall the SQL VSS Writer component by modifying the SQL Server installation and selecting the VSS Writer feature.
Check for Conflicting Backup Solutions:
Ensure that no other backup software conflicts with Druva’s VSS operations. Conflicting software may disable or block SQL VSS Writers.
Uninstall or configure any conflicting solutions to prevent interference.
Verify SQL Server Compatibility:
Ensure that the SQL Server version is supported by Druva. Incompatible SQL versions can cause discovery failures.
Refer to Druva's documentation for the list of supported SQL Server versions.
Check Disk Space:
Low disk space can lead to VSS issues. Verify that the server has enough free space, particularly on the system volume and other relevant volumes.
Review Event Logs:
Examine Windows Application and System event logs for any VSS-related errors. Look for shadow copy failures or permission issues that may provide additional context.
Verify SQL Services:
Ensure that all necessary SQL Server services, particularly the "SQL Server VSS Writer," are running.
Restart both SQL Server and SQL Server VSS Writer services if needed.
Update SQL Server and Windows:
Confirm that both SQL Server and Windows are up to date with the latest patches and updates, as outdated software can cause VSS Writer compatibility problems.
Re-run SQL Discovery in Druva:
Once the VSS Writer issue is resolved, manually trigger SQL discovery in the Druva console to check if the SQL server is now detected.
Consult Microsoft Support:
If the issue persists despite troubleshooting, consider consulting Microsoft support or an SQL Server expert for further investigation into system-level issues.