Windows Server 2022 — VSS Writer Stuck in Failed State After SQL Maintenance Jobs — Fix & Prevention

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Quick Checks
3. Deep Diagnosis
4. Primary Fix
5. Verification
6. Prevention & Hardening

Symptom & Impact

One or more VSS writers remain failed after heavy SQL maintenance windows, causing subsequent backup jobs to abort. Recovery consistency points are missed for transactional workloads. Repeated failures can mask deeper I/O or writer timeout constraints.

Quick Checks

Identify failed writer names and associated service dependencies before restarting broad service sets.

vssadmin list writers
Get-Service SQLWriter,VSS,swprv
Get-WinEvent -LogName Application -MaxEvents 80 | Where-Object {$_.ProviderName -match 'VSS|SQLWRITER'}

Deep Diagnosis

Map writer failures to SQL maintenance operations and storage throughput events during snapshot windows.

Get-WinEvent -LogName 'Microsoft-SQLServer-DataEngine/Operational' -MaxEvents 100
Get-Counter 'PhysicalDisk(_Total)Avg. Disk sec/Transfer'
fltmc instances

Primary Fix

Restart failed writer services in dependency order and adjust maintenance overlap with backup jobs.

Restart-Service SQLWriter
Restart-Service VSS
Restart-Service swprv
vssadmin list writers

Verification

All writers should return Stable/No error and backup test must finish successfully.

vssadmin list writers
wbadmin start systemstatebackup -backupTarget:F: -quiet

Prevention & Hardening

Separate backup and index/rebuild windows and instrument writer-state alerts before nightly protection jobs.

Get-ScheduledTask | Where-Object {$_.TaskName -match 'Backup|SQL'}
Get-WinEvent -LogName Application -MaxEvents 30 | Where-Object {$_.ProviderName -eq 'VSS'}