Backup status
Last-backup-time across every instance, with success/failure tracking.
/dashboard/backups is the fleet-wide backup health page.
What you see
A sortable table with a row per instance:
- Instance name.
- Last backup at — timestamp.
- Age — relative ("3 h ago", "2 d ago").
- Outcome — Success / Failed / Unknown.
- Size — MB of the last backup.
- Schedule — daily / weekly / custom.
Health-score bands
The backup component of the health score uses these tiers:
- < 168 h (≤ 7 days) — full 20 / 20 (healthy).
- 168 – 200 h (~7 to 8.3 days) — 10 / 20 (aging).
- > 200 h — 0 / 20 (stale).
The row colour codes match:
- Green — backup ≤ 7 days.
- Yellow — 7–8.3 days.
- Red — > 8.3 days, or the most recent attempt failed.
These bands were relaxed in May 2026 to match real-world weekly cadences.
Per-instance detail
Click an instance row to open its detail page → Backups tab. There you see:
- Backup history — every backup attempt with timestamp, size, status, and (if failed) the error message reported by 3CX.
- Schedule — read-only mirror of the schedule configured in 3CX.
We don't modify backup schedules from Sikurd — change them in the 3CX admin console. Sikurd just reports.
Failure alerts
A "Backup Failed" alert fires when a backup runs but ends in error. A "Backup Stale" alert fires when no successful backup has happened in 7+ days. Both are configurable in Alert routing.