Case study

The backup loop that proves the dump will load.

A backup that only proves a file exists is not enough. The failure that matters is the one discovered on disaster day: a missing extension, truncated dump, version mismatch or row count that no longer matches production.

Internal infra · backup · continuityDaily backup loop with heartbeat and failure warningRow-count verification inside gzipped dumpsDestination asserted outside any git work tree14 daily plus 8 weekly retention pruningWeekly restore into throwaway Postgres on a non-production portRestore checks for SQL errors, table presence and row-count parityKnown gaps surfaced on the page rather than hidden

operational stores covered by the current dump

14 + 8

daily and Sunday weekly retention

production writes during restore testing

16.15

Postgres version recorded for recovery

How these were measured: Source: operations/systems/K-16-backup-cold-com-kratt-backup-cold.md and K-17-restore-test-com-kratt-restore-test.md record the build dates, green runs, retention, restore behavior and known exception.

What we shipped

backup-cold dumps the operational stores that would hurt if the box died and verifies row counts against the same run. restore-test then loads those dumps into a throwaway Postgres instance on a separate machine, checks for load errors and matching rows, and destroys the test database after the run.

Daily backup loop with heartbeat and failure warningRow-count verification inside gzipped dumpsDestination asserted outside any git work tree14 daily plus 8 weekly retention pruningWeekly restore into throwaway Postgres on a non-production portRestore checks for SQL errors, table presence and row-count parityKnown gaps surfaced on the page rather than hidden

What this page does not claim

No database contents, dump paths, host addresses, personal data, Slack webhook or credential material is exposed.
The n8n backup gap remains stated instead of claimed solved. The source card says the target exists but is blocked on a human approval and encryption-key handling.
No claim that this replaces a formal disaster-recovery program. It proves these dumps exist, verify row counts and load in a separate restore test.

Recovery Guarantee: your revenue stops leaking, or we work free until it does. No lock-in.

Where is your business leaking revenue?

A free AI audit finds it, ranked by impact, and it is yours to keep.

Get your free AI audit See every live build

Back to all case studies, or see every live build on the portfolio wall.