WAL-G backup staleness monitor #6

Closed
opened 2026-05-23 07:42:06 +00:00 by fkrebs · 1 comment
Owner

Every hour, check latest WAL-G backup timestamps per DB (immich, lobe) in Garage S3.
If last backup >26h old → Gotify priority 8 alert.

Context: silent WAL-G stall went undetected for 13h in 2026-05-22 incident.

Nodes: Cron → Execute Command (mc ls garage S3 paths) → IF age >26h → Gotify.

Every hour, check latest WAL-G backup timestamps per DB (immich, lobe) in Garage S3. If last backup >26h old → Gotify priority 8 alert. Context: silent WAL-G stall went undetected for 13h in 2026-05-22 incident. Nodes: Cron → Execute Command (mc ls garage S3 paths) → IF age >26h → Gotify.
Author
Owner

Closed by /usr/local/sbin/walg-staleness-check.sh + walg-staleness.timer on CT 103 (hourly). Queries pg_stat_archiver on each Postgres host; alerts on stale archive OR recent failures. Found Immich wal-g had been broken for 42h (garage hostname unresolvable after Garage container was manually recreated on bridge network not shared_backend) — fixed by reconnecting garage to shared_backend.

Closed by /usr/local/sbin/walg-staleness-check.sh + walg-staleness.timer on CT 103 (hourly). Queries pg_stat_archiver on each Postgres host; alerts on stale archive OR recent failures. Found Immich wal-g had been broken for 42h (garage hostname unresolvable after Garage container was manually recreated on bridge network not shared_backend) — fixed by reconnecting garage to shared_backend.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: fkrebs/n8n-flows#6