Nightly MariaDB dumps
One file per database, kept for 7 days.
rttf · recipe pack · version 1.2.0
Nightly MariaDB and S3 backups, Postgres to any minute, and restore tests that run every week and email you when a backup would not come back.
The problem
Dumps get corrupt, jobs stop silently, and you find out on the day you need them. On a home lab, nobody is on call to notice. Except you, eventually, at the worst possible moment.
What you get
Flux manifests for the jobs, restore tools and a runbook. The tests restore into throwaway instances, so they never touch your live data.
One file per database, kept for 7 days.
Every bucket mirrored; changed and deleted files kept for 14 days.
CloudNativePG with weekly base backups and every WAL segment archived to your S3.
Each restores the latest backup into a throwaway instance, compares it with live data, and fails if it cannot.
One script each: a MariaDB database, bucket files, Postgres into a new cluster, or (optional) the whole cluster's state from a nightly k3s datastore copy.
A job stopped, a restore test failing or missing, a Postgres backup stale, WAL archiving failing.
Made for AI coding agents
The recipe ships with an AGENTS.md and a CLAUDE.md written as an operating procedure. A restore can overwrite live data, so the agent must have you name the exact target and confirm.
# following recipes/backups/AGENTS.md
✓ backup-mariadb and backup-garage ran, first base backup completed
✓ restore tests: mariadb, garage, postgres passed
? Restore database shop from 2026-11-09? This overwrites live tables.
? Type the database name to confirm:
(nothing happens until you answer)
Illustration of the steps in AGENTS.md, not a recorded session.
Tested, not promised
500 MariaDB rows, 1,000 Postgres rows and 2 files. The backups ran, the restore tests passed, then five recovery drills, each compared with the source. On x86_64 and again on arm64.
Is it for you?
Yes, if you run MariaDB, Postgres or S3 on a small k3s cluster and want to know, every week, that you could get it back.
No, if you need Neo4j, Valkey or an offsite copy to a second S3: not in this version.
kubectl
Questions
On a volume you choose. The default is a volume on one node's disk, for trying it out; the README and the agent both tell you to use NFS or another machine for real, so a dead disk does not take the backups with it.
Each week it restores the latest backup into a throwaway instance, compares it with your live data (databases present, rows there, files present), and fails if it cannot. A failing or missing test raises an alert.
No. Postgres needs an S3 bucket for its archive; the S3 recipe provides one, but any S3 works.
Done in 1.2. Postgres backs up through CloudNativePG's Barman Cloud plugin, so 1.31 dropping the built-in backup doesn't touch you. Coming from 1.1? The README has an upgrade, tested on a running install: 26 seconds without Postgres writes, and your old backups stay restorable.
It runs on 64-bit ARM: it was tested from zero on an arm64 VM. It was not tested on a Pi itself, and 32-bit ARM is not supported.
Nightly backups, weekly proof, and a restore you have already rehearsed. Tested from zero on x86_64 and arm64.
Get the recipe €29