Quick troubleshooting view
Traffic uses a backup link while the main link appears available.
- Limit the impact.
- Collecting Evidence.
- Test the the simplest hypothesis.
- Correct the confirmed cause rather than the symptom.
- Document the change and result.
- Establish supervision if the defect can recur.
Contextual technician plan
Identify whether a position, service or entire site is affected.
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.
Keep the message accurate, time, and associated logs.
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 with equipment or functional path.
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.
Apply only one change at a time and retester.
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.
Cadader if the impact extends, if the data are at risk or if the cause involves irreversible modification.
Traffic uses a backup link while the main link appears available.
Causes probables
- SLA threshold
- SD-WAN rule
- priority
Diagnostic étape par étape
- 1
Limit the impact.
Identify whether a position, service or entire site is affected.
- 2
Collecting Evidence.
Keep the message accurate, time, and associated logs.
- 3
Test the the simplest hypothesis.
Compare with equipment or functional path.
- 4
Correct and validate.
Apply only one change at a time and retester.
Solutions possibles
- Correct the confirmed cause rather than the symptom.
- Document the change and result.
- Establish supervision if the defect can recur.
Cadader if the impact extends, if the data are at risk or if the cause involves irreversible modification.