Backup
Read-only health view of the backup system showing schedule configuration, local storage usage, encryption status, S3 remote storage reachability, and trigger history. Two configurable daily backup times (labelled "Config DB" and "Results DB" — a legacy naming from before the schemas shared one cluster) each produce a full cluster bundle. Configure backups in Admin > Backups.
Fields & columns
| Name | Description |
|---|---|
Config DB / Results DB schedule | Whether automated daily backups are enabled and at what hour they run |
Config / Results Retention | How many days backup bundles are kept before automatic cleanup |
Next Config / Results Backup | Scheduled time of the next automated backup for each of the two daily backup times |
Bundle Count | Number of backup bundles reported via the backup HTTP API |
Total Size | Combined size of all local backup bundles |
Free Disk | Available disk space on the backup volume — red when below the minimum threshold |
Min Free Threshold | Minimum free disk space required; backups fail if disk drops below this |
Oldest / Newest Bundle | Timestamps of the oldest and most recent backup bundles |
Encryption Status | Whether backup bundles are encrypted with AES-256-CBC before storage |
S3 Bucket | The S3-compatible bucket name when remote storage is configured |
S3 Reachable | Whether the S3 endpoint is currently accessible (checked with a 5-minute cache) |
Total / Successful / Failed Triggers | Cumulative counts of backup triggers (both manual and scheduled) |
Recent Triggers | List of recent backup triggers showing who requested them, when, and their status |
Gotchas
- This page is read-only monitoring. To change backup settings or trigger a manual backup, use Admin > Backups.
- Trigger health is based on the most recent completed trigger only — a single past failure does not permanently mark health as unhealthy.
- S3 reachability uses a 5-minute cache, so changes to S3 configuration may take up to 5 minutes to reflect here.
- Backup bridges both networks: internal for database dumps via pg_dump, external for S3 remote storage push.
API calls (1)
| Method | Path | Description |
|---|---|---|
| GET | /api/health/infra/backup | Fetch backup schedule, storage, encryption, S3, and trigger data |
Related
- Overview — Architecture diagram showing the backup node and S3 connection
- Database Status — Backup system dumps the cluster via pg_dump
- Backup Configuration — Configure backup schedules, retention, encryption, and S3 replication
- Maintenance — Restart the backup service or trigger a manual backup from the centralized maintenance page