{"canonical_url":"https://engineer.company/portfolio/implemented-backups-and-disaster-recovery-as-code/","content_markdown":"# Implemented backups and disaster recovery as code\n\nConfigured database backup retention as infrastructure‑as‑code, then audited the recovery position and documented the restore procedure — naming the remaining gaps rather than leaving them to be found during an incident.\n\n2025\n\n**Situation.** A product that lives on its data can't afford to lose any, and \"there are backups somewhere\" is a hope, not a recovery plan. The only backup worth having is one you know restores, into an environment you know you can rebuild. The product had neither half written down.\n\n**Task.** Get the recoverable position defined instead of assumed — the data, the environment around it, and an honest account of how far that actually reaches today.\n\n**Action.** Backup retention is configured in the Bicep beside the database it protects, so point‑in‑time restore is a property of the template rather than a setting someone once clicked in a portal. The environment around it is defined as infrastructure‑as‑code too, which is the quiet half people forget: restoring a database into an environment you'd have to rebuild by hand from memory isn't really recovery. Then the position was audited and written up — the restore procedure, the drill that would measure it, and the gaps still open: geo‑redundancy is switched off, and the recovery‑time objective is proposed rather than measured, because no drill has been run yet.\n\n**Result.** Recovery stopped being a vague reassurance and became a documented position with its gaps named. That reads less impressively than \"disaster recovery: done\", and it is worth considerably more — whoever touches it next knows what is covered, what isn't, and exactly which drill closes the difference. A named gap is one you can close; an unnamed one is discovered during an incident.\n\n---\n\n- Role: Site Reliability Engineer\n- Categories: [Databases](https://engineer.company/categories/databases/), [PostgreSQL](https://engineer.company/categories/postgresql/), [DevOps](https://engineer.company/categories/devops/), [Infrastructure](https://engineer.company/categories/infrastructure/), [Cloud](https://engineer.company/categories/cloud/), [Reliability \u0026 Backups](https://engineer.company/categories/reliability/)\n- Services: [Database Administration (DBA)](https://engineer.company/services/database-administration/), [Infrastructure as Code](https://engineer.company/services/infrastructure-as-code/), [Backup \u0026 Disaster Recovery](https://engineer.company/services/backup-recovery/)\n\n\u003chttps://engineer.company/portfolio/implemented-backups-and-disaster-recovery-as-code/\u003e\n","date_modified":"2026-11-12T05:34:23Z","description":"Configured database backup retention as infrastructure-as-code, audited the recovery position and documented the restore procedure and remaining gaps.","formats":{"gemtext":"https://engineer.company/portfolio/implemented-backups-and-disaster-recovery-as-code/index.gmi","gopher":"https://engineer.company/portfolio/implemented-backups-and-disaster-recovery-as-code/gophermap","html":"https://engineer.company/portfolio/implemented-backups-and-disaster-recovery-as-code/","json":"https://engineer.company/portfolio/implemented-backups-and-disaster-recovery-as-code/index.json","markdown":"https://engineer.company/portfolio/implemented-backups-and-disaster-recovery-as-code/index.md","pdf":"https://engineer.company/portfolio/implemented-backups-and-disaster-recovery-as-code/index.pdf"},"kind":"page","language":"en","title":"Implemented backups and disaster recovery as code","url":"https://engineer.company/portfolio/implemented-backups-and-disaster-recovery-as-code/","version":1}