How to fix Error 3084 on Windows Server 2025 / Windows 11

by

Troubleshooting Guide: SQL Server Error 3084 — “Database Released Suspend Locks in Session”

Why This Error Happens

This informational message indicates that SQL Server temporarily suspended I/O operations on a database (typically during a VSS-based backup or snapshot operation) and has now resumed normal activity by releasing the suspend locks. It commonly occurs in conjunction with third-party backup software, Volume Shadow Copy Service (VSS) snapshot operations, or Always On Availability Group synchronization tasks. While not an error in the traditional sense, repeated or unexpected occurrences can point to a VSS writer timeout, a backup application holding the freeze state too long, or underlying storage latency causing the suspend/resume cycle to behave abnormally.

Step-by-Step Resolution Guide

Step 1: Verify the SQL Server VSS Writer Status

  • Open an elevated Command Prompt on Windows Server 2025 / Windows 11.
  • Run vssadmin list writers and confirm “SQL Server VSS Writer” shows a state of [1] Stable with no error.
  • If the writer shows a failed or unstable state, restart the service via net stop SQLWriter followed by net start SQLWriter.

Step 2: Review SQL Server Error Log and Event Viewer

  • Open SQL Server Management Studio (SSMS) and navigate to Management > SQL Server Logs.
  • Cross-reference the timestamp of Error 3084 with Windows Event Viewer under Applications and Services Logs > Microsoft > Windows > VSS.
  • Look for any correlating backup job failures, snapshot timeouts, or storage driver warnings (Event IDs 12289, 8229, or similar).

Step 3: Audit Third-Party Backup / Snapshot Software

  • Identify the backup agent (e.g., Veeam, Commvault, Windows Server Backup) currently interacting with the SQL instance.
  • Check the backup software’s configuration for VSS freeze/thaw timeout settings — default is usually 10-60 seconds.
  • Increase the timeout value if storage latency is causing the suspend to run longer than expected, located typically under the backup job’s advanced storage/application-aware settings.

Step 4: Check Underlying Storage Performance

  • Open Performance Monitor (perfmon.exe) and add counters for PhysicalDisk > Avg. Disk sec/Transfer on the volume hosting your .mdf/.ldf files.
  • Values consistently above 20ms indicate disk latency that may be prolonging the suspend state.
  • If using SAN or cloud-attached storage, confirm multipathing drivers and firmware are updated to the latest version certified for Windows Server 2025.

Step 5: Validate SQL Server and OS Patch Level

  • Run SELECT @@VERSION; in SSMS to confirm you are on the latest Cumulative Update for SQL Server 2025.
  • Apply any pending Windows Updates via Settings > Windows Update, as storage class drivers and VSS components are frequently patched.
  • Reboot the server during a maintenance window after patching to fully apply driver-level fixes.

Alternative or Verification Steps

  • To verify resolution, run a manual full backup via SSMS or your backup software and confirm Error 3084 appears only once per backup cycle (expected behavior) rather than repeatedly or alongside timeout errors.
  • If the issue persists, temporarily disable third-party VSS-aware backup agents and run a native BACKUP DATABASE T-SQL command to isolate whether the issue is SQL-side or backup-software-side.