Windows Server 2022 — SQL Server backup jobs fail due VSS writer unstable state — Fix & Prevention

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution — Primary Fix
7. Solution — Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Scheduled SQL backups fail with VSS-related errors, leaving recovery points incomplete and increasing RPO risk.

Environment & Reproduction

Common after patching/reboot sequences where Volume Shadow Copy writers enter failed state.

vssadmin list writers
Get-Service VSS,SQLWriter
Get-WinEvent -LogName Application -MaxEvents 60 | Where-Object {$_.Message -match 'VSS|SQLWriter|backup'}

Root Cause Analysis

VSS writer inconsistency, provider conflicts, or storage snapshot contention interrupts backup snapshot creation.

Quick Triage

Check writer state and restart affected services before rerunning backup workflow.

vssadmin list providers
Restart-Service SQLWriter -Force
Restart-Service VSS -Force

Step-by-Step Diagnosis

Correlate VSS events with SQL Agent backup job history to isolate timing and impacted databases.

Get-WinEvent -LogName Application -MaxEvents 100 | Where-Object {$_.ProviderName -match 'VSS|SQLWriter'}
Invoke-Sqlcmd -Query "SELECT TOP 30 run_date,run_time,run_status,message FROM msdb.dbo.sysjobhistory ORDER BY run_date DESC,run_time DESC"

Solution — Primary Fix

Reset failed writers, ensure stable storage provider state, and execute controlled backup retry.

Restart-Service SQLSERVERAGENT -Force
Restart-Service SQLWriter -Force
vssadmin list writers
Invoke-Sqlcmd -Query "BACKUP DATABASE [] TO DISK='C:/Temp/.bak' WITH COPY_ONLY,INIT"

Solution — Alternative Approaches

Use native SQL backup path without VSS dependency for immediate protection until VSS subsystem is fully repaired.

Invoke-Sqlcmd -Query "BACKUP DATABASE [] TO DISK='D:/SqlBackups/_fallback.bak' WITH COMPRESSION,CHECKSUM"

Verification & Acceptance Criteria

All VSS writers are stable and backup jobs complete successfully with valid restore tests.

vssadmin list writers
Invoke-Sqlcmd -Query "RESTORE VERIFYONLY FROM DISK='D:/SqlBackups/_fallback.bak'"
Get-WinEvent -LogName Application -MaxEvents 20 | Where-Object {$_.Message -match 'backup'}

Rollback Plan

If writer reset fails, revert to previous backup method and isolate problematic VSS provider/agent modules.

vssadmin list providers
# Disable offending backup agent service temporarily and run native SQL backups

Prevention & Hardening

Automate writer-state checks before backup windows and alert on any writer not in Stable state.

vssadmin list writers | Out-File C:/Temp/vss-writers-status.txt
Get-ScheduledTask | Where-Object {$_.TaskName -match 'Backup|SQL'}

Related Errors & Cross-Refs

Related to VSS 8193/12293 events, SQL Agent backup step failures, and storage snapshot provider timeouts.

View all Windows Server 2022 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Microsoft VSS troubleshooting references and SQL Server backup reliability guidance for production Windows Server workloads.