Back to All Scenarios
PASSEDdatabase / backup_failure
PostgreSQL 16 Backup Job Failed — Retention at Risk on Debian 12 Bookworm
PostgreSQL 16 backup job has been failing for 20 consecutive runs. No recent restore point available. Data protection gap growing.
Pattern
BACKUP_FAILURE
Severity
HIGH
Confidence
68%
Remediation
Auto-Heal
Test Results
| Metric | Expected | Actual | Result |
|---|---|---|---|
| Pattern Recognition | BACKUP_FAILURE | BACKUP_FAILURE | |
| Severity Assessment | HIGH | HIGH | |
| Incident Correlation | N/A | None | |
| Cascade Escalation | N/A | No | |
| Remediation | — | Auto-Heal — Corax resolves autonomously |
Scenario Conditions
Debian 12 Bookworm. PostgreSQL 16 backup job failing since 20 runs ago. Backup repository accessible. Error during data transfer phase.
Injected Error Messages (1)
PostgreSQL 16 backup failed on Debian 12 Bookworm — backup job failed for 20 consecutive runs, backup chain broken, no recent restore point, postgres data not protected
Neural Engine Root Cause Analysis
Backup failure detected — a scheduled backup job has failed, the backup chain may be broken requiring a new full backup, the backup repository is full or unreachable, or restore points are missing. Failed backups leave critical data unprotected and may violate compliance requirements and SLAs.
Remediation Plan
1. Check the backup application (Veeam, Datto, etc.) for the specific job failure reason and error code.
2. Verify backup repository has sufficient free space — clear old backup sets if needed.
3. For broken backup chains, initiate an active full backup to re-establish the chain.
4. Check network connectivity between the backup server and source/target if the job timed out.
5. Verify VSS (Volume Shadow Copy Service) is healthy on the source server if snapshot-based backups are failing.
Tested: 2026-04-02Monitors: 1 | Incidents: 1Test ID: cmnhnwaqu04gklijgsa97vqq9