# esh-vm-db Restic repaired

User asked diagnose/fix two service issues. Only check was systemd-failed:
Sep6 repository network timeout after boot. Backup exited0 nightly but pg_dumpall
used TCP localhost, required a password, and silently kept April23 dump.
Mongo dumps worked. Root cause was the WARN-only hook masking PG failure.

Fixed PG to /var/run/postgresql peer auth with -w, both DB failures now fail
backup preserving prior per-DB dump. Three red-green regression tests pass.
Added drop-ins to both jobs: network-online ordering, Restart=on-failure,
RestartSec=5min, StartLimitIntervalSec=1h, StartLimitBurst=3.

Verified real backup bc5eeaff 07:01PDT; fresh PG gzip 3460215 bytes. Retrieved
from repo, decompression and completion marker pass (not full restore).
Check at07:02 passed 99 snapshots/10% data (19 packs). No failed units remain;
both timers active, PG and Mongo active. Inactive/dead between jobs is normal.
Old hook/dump preserved root-only /var/lib/restic/repair-20260912.
Canonical configs/restic/esh-vm-db and playbooks/esh-vm-db-restic-repair.yaml.
No DB restarts or auth-policy changes; changes saved locally, no commit.