Quick troubleshooting view
The task is either complete or progressed, but the duration has become much longer than usual….
- Insufficient bandwidth
- Slow source/deest storage.
- High rate of change.
- Compare historical flows.
- Control I/O source and target
- Control the network
- Correct the identified bottleneck
- Adapt window or planning
- Optimize exclusions only according to editor recommendations
Contextual technician plan
Look if the flow actually fell.
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.
Watch the disc latency.
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.
Measure the flow rate and errors.
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.
An unusual rate of change may explain the duration.
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 the flow drops abruptly without changing volume or network.
The task is either complete or progressed, but the duration has become much longer than usual.
Causes probables
- Insufficient bandwidth
- Slow source/deest storage.
- High rate of change.
- Antivirus/EDR.
- Cost-effective deduplication or compression.
- Too short backup window.
Diagnostic étape par étape
- 1
Compare historical flows.
Look if the flow actually fell.
- 2
Control I/O source and target
Watch the disc latency.
- 3
Control the network
Measure the flow rate and errors.
- 4
Compare the modified volume
An unusual rate of change may explain the duration.
Solutions possibles
- Correct the identified bottleneck
- Adapt window or planning
- Optimize exclusions only according to editor recommendations
Climb if the flow drops abruptly without changing volume or network.