Files
felhom.eu/documentation/audits/DRILL-r403-tier2-delete-2026-08-31/phase4-teardown-and-final-state.log
T
admin dddcc808be
gates / gates (push) Failing after 17s
R-403 CLOSED (controller v0.230.0), R-404 filed as a decision for Viktor
07-backup-architecture gains section 8.2, placed beside row 5 on purpose: the derived-copy rebuild
rule is UNCHANGED and section 8.2 names the single exception, so a future reader who finds RunTier2
skipping a leg does not fix it back. It carries the measurement (120 082 104 B -> 7 036 B on the
shipped v0.229.0), the four-case table, why hollow is a manifest question and not a size question,
why the data legs are deliberately not guarded, and why the capture job is not guarded either.

00-capability-map: the Tier-2 row's status does NOT move, stated explicitly rather than left
ambiguous. R-403 removes a way the route could be DESTROYED between uses; it does not change what
the route can be relied on for.

Register: R-403 CLOSED and compressed into CLOSED-ITEMS (594 -> 593 open lines). R-404 FILED as a
DECISION and deliberately not acted on - should a documents-only push be subject to the
golden-currency gate, now that it has been correctly bypassed six times? Both sides stated, plus
what happens if Viktor does nothing. The gate was NOT changed.

R-242: seventh conviction, and the FIRST where the day-0 ground does not apply - R-403 is a defect
in the nightly Tier-2 copy, which a day-0 box starts running on its first night. This push uses
git push --no-verify, declared here and in felhom-controller/REPORT.md. A golden carrying 0.230.0 is
owed and is more urgent than the previous six.

STATUS: the R-403 item moves out of 'Broken' into what works, in plain words; the delivery item now
says a golden is owed and that the fleet carries the defect; R-404 goes into the decide section with
its do-nothing outcome.

Drill evidence: nine phase logs, including the two things that went wrong (a repair whose rsync was
not installed in the guest and silently did nothing, and a session that expired mid-run so a POST
did nothing).
2026-08-31 14:39:29 +02:00

46 lines
1.5 KiB
Plaintext

######## TEARDOWN / final state ########
UTC 2026-08-31T12:33:57Z
--- a normal Tier-2 run now that BOTH sides are complete (the unit leg must NOT be skipped)
200
2026/08/31 12:33:57 tier2.go:424: [INFO] [backup] Tier 2 copied docmost → /mnt/felhom-drives/hdd_1/backups/secondary/docmost (114.5 MB, 0 leg(s), 0s)
unit-leg skips in this run: 0
--- both copies
PRIMARY : 3 tars, 4 dumps, 120082104 bytes
SECONDARY : 3 tars, 4 dumps, 120082104 bytes
IDENTICAL volume-dumps/docmost_docmost_postgres_data.tar
IDENTICAL db-dumps/docmost-postgres.sql
--- the surface is back to normal (no stale notice anywhere)
adatcsomagja occurrences: 0
--- remove the drill safety net and the driver
safekeeping removed
.bash_history
.bashrc
.docker
.profile
.ssh
settings.json.drill-backup
--- every app healthy?
docmost Up 9 minutes (healthy)
docmost-redis Up 9 minutes (healthy)
docmost-postgres Up 9 minutes (healthy)
romm Up 3 hours (healthy)
romm-db Up 3 hours (healthy)
romm-redis Up 3 hours (healthy)
privatebin Up 3 hours (healthy)
paperless-webserver Up 3 hours (healthy)
paperless-postgres Up 3 hours (healthy)
paperless-redis Up 3 hours (healthy)
opengist Up 3 hours (healthy)
kimai Up 3 hours (healthy)
kimai-db Up 3 hours (healthy)
calibre-web Up 3 hours (healthy)
bookstack Up 3 hours (healthy)
bookstack-db Up 3 hours (healthy)
filebrowser Up 9 days (healthy)
cloudflared Up 9 days
traefik Up 9 days