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

by

Troubleshooting Guide: SQL Server Error 3086 — VSS Snapshot Backup Suspension Notice

Why This Error Happens

Error 3086 is actually an informational message, not a true failure condition, which is generated when SQL Server successfully freezes I/O operations on a database in response to a Volume Shadow Copy Service (VSS) request. This occurs because a third-party or native backup utility initiated a snapshot backup, causing the SQL Server VSS Writer to pause write activity on the specified database to ensure a consistent, point-in-time image can be captured. While not an error in the traditional sense, it is often reported by administrators when the “suspension” phase takes too long, fails to resume (thaw), or is accompanied by application timeouts because the freeze period exceeded the default I/O freeze threshold (typically 10-60 seconds) allowed by the Windows VSS framework.

Step-by-Step Resolution Guide

Step 1: Verify the VSS Writer Service Status

  • Open an elevated Command Prompt on your Windows Server 2025 or Windows 11 machine.
  • Run vssadmin list writers to check the status of the “SQLServerWriter.”
  • Look specifically for a state of “Stable” with “No error.” If the state shows “Failed” or “Retryable Error,” the freeze/thaw cycle did not complete successfully.

Step 2: Restart the SQL Server VSS Writer Service

  • Open the Services management console (services.msc).
  • Locate SQL Server VSS Writer in the list.
  • Right-click and select Restart. If the service is disabled, set the Startup Type to Automatic and start it manually.
  • Re-run vssadmin list writers to confirm the state has reset to “Stable.”

Step 3: Check I/O Freeze Timeout Duration

  • Navigate to the registry path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer.
  • Look for or create a DWORD value named BackupIoRequestTimeout.
  • Increase the value (in seconds) if your underlying storage (SAN/NAS) is slow to respond to the snapshot creation request, as a timeout here can prevent the “thaw” command from being issued.

Step 4: Audit Third-Party Backup Software Configuration

  • Check your backup software’s logs (e.g., Veeam, Commvault, Windows Server Backup) for the exact timestamp matching the SQL Server error log entry.
  • Ensure the backup software is configured to use the “Transportable” or “Copy-Only” full VSS backup method to avoid conflicts with native SQL Server transaction log backups.
  • Confirm the backup account running the snapshot software has sysadmin rights on the SQL Server instance or is a member of the local Administrators group.

Step 5: Review Disk Latency and Hardware Provider

  • Verify that the storage hardware VSS provider (if using a SAN) is up to date, as outdated drivers often cause the snapshot to hang during the frozen I/O state.
  • Use vssadmin list providers to confirm the specific hardware or software provider being used for the snapshot.

Alternative or Verification Steps

  • Verification: After resolving the issue, run a manual VSS-based backup and immediately check the SQL Server Error Log (via SSMS) for a corresponding “successfully resumed from” message, which confirms the freeze/thaw cycle completed without hanging.
  • Alternative: If VSS snapshots continue to fail intermittently, switch the backup strategy temporarily to native SQL Server BACKUP DATABASE T-SQL commands (streaming backup) to bypass the VSS layer entirely while you troubleshoot the underlying hardware provider.