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

by

Troubleshooting Guide: Error 3197 – “I/O is Frozen on Database”

Why This Error Happens

This message is typically informational and appears when SQL Server 2025 issues an I/O freeze to support a VSS (Volume Shadow Copy Service) snapshot backup operation, pausing writes momentarily so a consistent backup can be taken. However, if the “thaw” command never arrives—due to a failed or interrupted backup utility, antivirus interference, or a malfunctioning VSS writer—the freeze can persist longer than expected, causing application timeouts. In rare cases, this can also stem from storage-level latency or corrupted VSS provider components on Windows Server 2025/Windows 11.

Step-by-Step Resolution Guide

Step 1: Verify the VSS Writer Status

  • Open an elevated Command Prompt and run vssadmin list writers.
  • Check for the “SqlServerWriter” entry; confirm its state reads [1] Stable and No error.
  • If it shows “Failed” or “Retryable Error,” note the Writer ID for restart purposes.

Step 2: Restart the SQL Server VSS Writer Service

  • Open Services.msc (Windows Server 2025/Windows 11).
  • Locate SQL Server VSS Writer, right-click, and select Restart.
  • Alternatively, run in an elevated prompt:
    net stop SQLWriter && net start SQLWriter

Step 3: Check Backup Software and Antivirus Interference

  • Review the third-party backup application (e.g., Veeam, Commvault) logs for incomplete snapshot jobs.
  • Temporarily disable real-time antivirus scanning on the SQL data/log directories (e.g., D:\SQLData\, E:\SQLLogs\) to rule out file-lock conflicts.
  • Ensure backup jobs are not overlapping or running concurrently on the same volume.

Step 4: Review SQL Server Error Log for Thaw Confirmation

  • Open SQL Server Management Studio (SSMS) and navigate to Management > SQL Server Logs.
  • Search for the corresponding “I/O was resumed on database %ls” message, which should follow shortly after the freeze.
  • If no thaw message appears within a few minutes, manually restart the SQL Server service during a maintenance window:
    net stop MSSQLSERVER && net start MSSQLSERVER

Step 5: Update VSS Hardware/Software Provider Drivers

  • Check Device Manager or storage vendor tools (e.g., SAN/NAS provider) for outdated VSS hardware provider drivers.
  • Update to the latest version compatible with Windows Server 2025.

Alternative or Verification Steps

  • Run vssadmin list writers again post-fix to confirm “SqlServerWriter” returns to a Stable state with no errors.
  • If the issue recurs, switch the backup method to SQL Native Backup instead of VSS-based snapshots to bypass the freeze/thaw mechanism entirely.