{"canonical_url":"https://engineer.company/portfolio/backups-that-have-actually-been-restored/","content_markdown":"# Backup automation with an explicit restore method\n\nImplemented restic backup automation with retention, integrity checks and a monthly restore‑test workflow; documented storage activation and live‑restore verification as separate operational steps.\n\nSeptember 2026\n\n**Situation.** Engineer ApS needed a recovery design that covered its own infrastructure beyond a provider snapshot. The work concerned backup automation, storage prerequisites and a way to test restoration.\n\n**Task.** The implementation needed encrypted off‑host snapshots, retention rules, integrity checks and a repeatable restore test. Writing those controls and proving a live recovery are separate deliverables.\n\n**Action.** An Ansible role installs restic scripts and systemd units. The backup path supports a database dump where configured, snapshot creation, pruning and integrity checks. A separate monthly workflow restores a known file to a scratch location and compares its bytes. Success signals are separate for backup and restore; timers depend on a configured repository. The passphrase is read from a protected file rather than a systemd‑parsed environment value.\n\n**Result.** The repository contains the backup and restore‑test implementation and documents its activation prerequisites. The implementation record dated 2026‑10‑27 says the timers were disabled without a repository and records no completed live restore. That dated evidence supports the automation work, not a claim about current runtime state, successful disaster recovery or a recovery‑time commitment.\n\n---\n\n- Role: Site Reliability Engineer\n- Categories: [Infrastructure](https://engineer.company/categories/infrastructure/), [Automation \u0026 CI/CD](https://engineer.company/categories/automation/), [Reliability \u0026 Backups](https://engineer.company/categories/reliability/), [Linux \u0026 Servers](https://engineer.company/categories/linux/), [Security](https://engineer.company/categories/security/), [Documentation](https://engineer.company/categories/documentation/)\n- Services: [Infrastructure as Code](https://engineer.company/services/infrastructure-as-code/), [Site Reliability \u0026 Monitoring](https://engineer.company/services/site-reliability/), [Backup \u0026 Disaster Recovery](https://engineer.company/services/backup-recovery/), [System Administration](https://engineer.company/services/system-administration/)\n\n\u003chttps://engineer.company/portfolio/backups-that-have-actually-been-restored/\u003e\n","date_modified":"2026-11-15T19:47:44Z","description":"The repository contains the backup and restore-test implementation and documents its activation prerequisites.","formats":{"gemtext":"https://engineer.company/portfolio/backups-that-have-actually-been-restored/index.gmi","gopher":"https://engineer.company/portfolio/backups-that-have-actually-been-restored/gophermap","html":"https://engineer.company/portfolio/backups-that-have-actually-been-restored/","json":"https://engineer.company/portfolio/backups-that-have-actually-been-restored/index.json","markdown":"https://engineer.company/portfolio/backups-that-have-actually-been-restored/index.md","pdf":"https://engineer.company/portfolio/backups-that-have-actually-been-restored/index.pdf"},"kind":"page","language":"en","title":"Built backup and restore-test automation","url":"https://engineer.company/portfolio/backups-that-have-actually-been-restored/","version":1}