Platform & Infrastructure · Level 3 · artefact
Artefact — Backups and restore runbook
Three tiers — local snapshots · a copy on another machine · an offsite copy — with retention stated in the job and a restore runbook kept beside them.
- Borg
- Kopia
- Backrest
- AWS S3
- systemd
- NFS
Artefact — Backups and restore runbook
Status: stub. Redacted job definitions and the restore runbook land in Phase 7. Passphrase locations and remote paths are removed before publication.
What the artefact is
The backup design: Borg jobs on the two desktop hosts to local storage with a network copy, Kopia and Backrest on the edge host to network storage, an offsite copy in object storage, and retention expressed in the job (seven daily, four weekly, three monthly, plus annual on the edge). Beside it, the restore runbook and the list of what is deliberately not covered.
What it proves
That failure was designed for: three tiers cover disk loss, machine loss and site loss, and the restore path is written down rather than recovered from memory at the worst possible moment.
Limits stated on the page
Not everything is covered, and the page says so — one storage host is itself a single point of failure for some repositories, and the file server has no backup of its own. Those are known gaps with owners, not oversights to be hidden.
When it is delivered
Phase 7. Source: the infrastructure reference and the backup system notes, read 2026-10-26.