TopicBackup & PRA →
⌚ About 2 min read
Control the Windows VSS Writers status when a backup using VSS fails.
Avant de commencer : adaptez toujours les commandes et manipulations à votre environnement. Sur un système de production, prévoyez une backup ou un retour arrière lorsque l’action peut modifier la configuration.
Étapes à suivre
-
1
Open an admin terminal
Run Windows Terminal as an administrator.
-
2
List the Writers.
Run vssadminlist1909.
-
3
Search for Errors.
Find the grads that are not Stable and No error.
-
4
Identify associated service.
According to the Writer, look for the corresponding service or application.
-
5
Correct with caution.
Avoid restarting critical production services without assessing the impact.
Commands utiles
Csadminlist1909.
À retenir
- UnKer is a symptom: identify the application or the department responsible.
- Rebooting a server completely is not always an acceptable solution in production.
VSS: read Writer, Provider and Shadow Storage together
Technical checkpoints
- A Writer should be Stable and error-free for an application-consistent backup to use VSS.
- Events 8193/12289 often point to permissions, providers, COM or snapshot issues; context and error code matter more than the event number alone.
- vssadmin list shadowstorage checks used/max shadow storage; insufficient space can delete or fail snapshots.
VSS triage
Read Writers, Providers and ShadowStorage before restarting services.
vssadmin list writers
vssadmin list providers
vssadmin list shadowstorageTopic-specific pitfalls
- Restarting all VSS services can make writers Stable while hiding the responsible application.
- Deleting snapshots without checking backup policy can remove useful restore points.
How to validate
- All required Writers are Stable/No error immediately before backup.
- A test backup or snapshot completes and correlated VSS events do not recur.