Quick troubleshooting view
A Windows backup fails because, a/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C//C//C/C/C/C/C/C/C//C//C//C//C//C/C///C//C/C///C/C/C///////////C////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
- application service blocked.
- Incorrect VSS.:.:.
- Third party in conflict.
- List the writers
- Identify the related service
- View events
- restart the service of the 1998/99 properly if this is acceptable
- correct the application that blocks the writer
- to deal with a conflict of ,
Contextual technician plan
Run vssadminlist1909 and raise the exact state.
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.
Associate the failing 1998/99 with its application or service.
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.
Search VSS/VolS-Rap around the job time.
CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-G-CZG-CZG-CZG-CZG-CZG-CZG-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-GThe 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.
Check the installed VSSs.
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.
Scalader if multiple writers remain in error after restarting controlled or if the server hosts a transactional critical application.
A Windows backup fails because, a/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C/C//C//C/C/C/C/C/C/C//C//C//C//C//C/C///C//C/C///C/C/C///////////C////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Causes probables
- application service blocked.
- Incorrect VSS.:.:.
- Third party in conflict.
- Inadequate storage area or infrastructure
Diagnostic étape par étape
- 1
List the writers
Run vssadminlist1909 and raise the exact state.
- 2
Identify the related service
Associate the failing 1998/99 with its application or service.
- 3
View events
Search VSS/VolS-Rap around the job time.
- 4
Control the crows.
Check the installed VSSs.
Commands utiles
Csadminlist1909.vssadminlist,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, ,,CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-CZG-G-CZG-CZG-CZG-CZG-CZG-CZG-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-G-GSolutions possibles
- restart the service of the 1998/99 properly if this is acceptable
- correct the application that blocks the writer
- to deal with a conflict of ,
- adjust the shadow storage space if events confirm
Scalader if multiple writers remain in error after restarting controlled or if the server hosts a transactional critical application.