Quick troubleshooting view
Windows backup software fails when creating, a VSS snapshot….
- VSSKyr in error.
- Space shadow copy insufficient.
- Failed application service.
- List the Writers.
- Control the crows.
- Check events.
- Process service/application associated with the quar.
- Fix the space or configuration shadow copy.
- Restarting a service with controlled impact only.
Contextual technician plan
Run vssadminlist1909.
Csadminlist1909.The command should complete without an unexpected error and return data consistent with the intended service.
If the result is normal, keep this layer lower in the hypothesis ranking and continue with the next discriminating check.
If the result is abnormal, preserve the output and investigate this layer before making broader changes.
List the VSS-Shoths.
vssadminlist,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,The command should complete without an unexpected error and return data consistent with the intended service.
If the result is normal, keep this layer lower in the hypothesis ranking and continue with the next discriminating check.
If the result is abnormal, preserve the output and investigate this layer before making broader changes.
Read Application and System at the time of the failure.
The check should identify the exact failing backup stage and show healthy snapshot/writer/capacity state for the component being tested.
If this layer is healthy, keep the job timestamp and continue with repository, transport or authentication evidence.
If this layer is unhealthy, preserve the exact vendor/VSS error and repair that component before deleting chains, snapshots or restore points.
A wrongly-made Writer often points to a specific service.
The check should identify the exact failing backup stage and show healthy snapshot/writer/capacity state for the component being tested.
If this layer is healthy, keep the job timestamp and continue with repository, transport or authentication evidence.
If this layer is unhealthy, preserve the exact vendor/VSS error and repair that component before deleting chains, snapshots or restore points.
Repeat the same validation test after the correction and confirm the original symptom is gone. Validate stability before closing the incident.
Before changing configuration, record the current value and a way back.
Climb if multiple Writers fail or if the ERS, VSS seems unstable.
Windows backup software fails when creating, a VSS cliché.
Causes probables
- VSSKyr in error.
- Space shadow copy insufficient.
- Failed application service.
- 2005 VSS third party.
- High server load.
Diagnostic étape par étape
- 1
List the Writers.
Run vssadminlist1909.
- 2
Control the crows.
List the VSS-Shoths.
- 3
Check events.
Read Application and System at the time of the failure.
- 4
Identify the associated application.
A wrongly-made Writer often points to a specific service.
Commands utiles
Csadminlist1909.vssadminlist,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,Solutions possibles
- Process service/application associated with the quar.
- Fix the space or configuration shadow copy.
- Restarting a service with controlled impact only.
Climb if multiple Writers fail or if the ERS, VSS seems unstable.