Quick troubleshooting view
The space of backup repository approaches saturation, which can cause job failures or prevent new chains.
- retention period too long
- growth of protected data
- orphaned former
- Measure the free space
- Check retention
- Identify big games
- adapt retention to actual OPR/RTO
- increase the capacity of the
- delete only orphan backups identified
Contextual technician plan
Compare total space, free and growth over several days.
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.
Control the actual number of restoration points.
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.
Identify the most voluminous jobs and chains.
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.
Compare actual storage with the backup software inventory.
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.
Escalader before any manual deletion in aDeduced, immutable or backed up by backup software.
The space of backup repository approaches saturation, which can cause job failures or prevent new chains.
Causes probables
- retention period too long
- growth of protected data
- orphaned former
- More large than expected
Diagnostic étape par étape
- 1
Measure the free space
Compare total space, free and growth over several days.
- 2
Check retention
Control the actual number of restoration points.
- 3
Identify big games
Identify the most voluminous jobs and chains.
- 4
Search for orphan data
Compare actual storage with the backup software inventory.
Solutions possibles
- adapt retention to actual OPR/RTO
- increase the capacity of the
- delete only orphan backups identified
- assign jobs to multiple deposits if necessary
Escalader before any manual deletion in aDeduced, immutable or backed up by backup software.