Repair ana-docker database backups and bound CI build caches

2026-09-10 09:10:01 -07:00
parent eb75713c1b
commit 44c853cd20
11 changed files with 277 additions and 26 deletions
@@ -0,0 +1,25 @@
+# ana-docker disk pressure repaired
+
+Operator authorized all three: repair/verify backups, remove failed dump
+residue, prune named builders with ongoing retention. Root went from 84%
+(about 39 GiB available) to 51% (115 GiB available).
+
+Gitea failed dumps since June 4 came from root-only config history unreadable
+to git. Five config history files MOVED, permissions preserved, outside dump
+tree to `/opt/docker/backups/gitea-config-history`. Vaultwarden dump credentials
+were stale; synchronized live connection to root:600 `/etc/restic/dbcreds.env`
+and Vaultwarden item `ana-docker/restic-dbcreds.env`.
+
+Hook now fails required dump errors, preserves previous stage until successful
+generation, validates Gitea tar, isolates/trap-cleans scratch. Three regression
+tests pass. Fresh Restic snapshot `2ec5a37c` restored into isolated disposable
+PostgreSQL: Vaultwarden 7 users, Gitea 9 users/93 repos. Then deleted 101 old
+dump residues (47.31 GiB logical); manifest kept with config history. Gitea
+temp now 8 KiB. Full app recovery and OpenWebUI SQLite consistency not claimed.
+
+Hourly named-builder prune targets 10 GiB unused-cache retention per active
+builder; not a hard quota. Worldtree temporarily started, pruned, STOPPED again;
+Skaldsong stays running and Soong stays stopped. Gitea HTTP 200, Vaultwarden
+healthy, test DB removed, cache unit success/timer enabled. Canonical files:
+`configs/restic/ana-docker/`, `configs/buildkit/ana-docker/`, deployment playbooks
+`ana-docker-backup-repair.yaml` and `ana-docker-cache-budget.yaml`.