Problem Description
MS SQL backup jobs fail immediately during the initialization phase. When reviewing the backup_agent.go and backup_helper.go logs on the affected SQL server, the following error sequence is observed:
Traceback
level=info ts=2025-10-21T20:23:41.9637846Z filename=backup_agent.go:235 message="SQL backup process started" DeviceVersion=7.0.6::r786034 PluginVersion=0.0.1 level=error ts=2025-10-21T20:23:42.3708099Z filename=signatureutils_windows.go:32 Panic="runtime error: invalid memory address or nil pointer dereference" level=error ts=2025-10-21T20:23:42.3708099Z filename=backup_helper.go:556 message="failed to init sql-ioclient: failed to verify signature for drst-ioserver.exe: panic while validating certificates" Error="Code: 4295163992\nOriginal: SQL IOServer Error\nMessage: SQL IOServer Error\ level=error ts=2025-10-21T20:23:42.3708099Z filename=backup_agent.go:241 message="Error while initializing backup agent" JobID=93366 Error="Code: 4295163992\nOriginal: SQL IOServer Error\nMessage: SQL IOServer Error
Cause
The failure is caused by a runtime crash (Panic) within the VerifyBinarySignature function of the Druva Enterprise Workloads Agent:
Critical Error: The system encountered a
nil pointer dereference, meaning the agent attempted to access a memory address that did not exist while validating security certificates.Specific Failure: The process crashed abruptly while trying to verify the digital signature of the
drst-ioserver.exebinary.Probable Cause: Local Druva Enterprise Workloads Agent executables or local signature/configuration files have become corrupted on the host machine, preventing the agent from safely confirming the authenticity of its own components.
Resolution
A clean uninstallation and re-registration of the SQL server is required to completely replace the corrupted binaries and reset the local agent environment.
Step 1: Uninstallation and Directory Cleanup
Open Control Panel > Programs and Features and uninstall the Druva Enterprise Workloads Agent.
Manually delete the following local configuration folders to ensure no corrupt remnants or signature caches remain:
C:\ProgramData\Druva\EnterpriseWorkloads(For legacy setups)
C:\ProgramData\Phoenix
Step 2: Obtain a New Activation Token
Log in to the Druva Management Console.
Navigate to Protect > MS-SQL Servers.
Select the affected SQL server from the Registered Servers list.
Click More options (...) > Re-Register Server.
Click Proceed to generate a new activation token, then copy it.
Step 3: Re-install and Activate the Agent
Download: Fetch the latest matching installer package (e.g.,
EnterpriseWorkloads-UnifiedAgent-7.0.6-786034.msi) from the Druva Downloads page.Install: Right-click the installer and choose Run as Administrator on the SQL host machine.
Activate: Launch the Druva Agent interface, select the MS-SQL option, paste the new activation token, and ensure the server name matches the console entry perfectly to preserve historical backup mapping.
Step 4: Verification
Verify that the server status changes back to Connected within the Druva Management Console.
Trigger a Manual Backup (Full or Differential) to confirm the
sql-ioclientinitializes successfully without a panic.