DisasterRecovery
Recovering from large-scale failure: RTO (recovery time objective) and RPO (recovery point objective), backup/restore strategy.
Why we need this / what value this brings
Without a tested DR plan, 'we have backups' is an assumption, not a guarantee, until you've actually restored from one.
When to use this
Before you need it — DR plans written during an active outage are worse than useless.
How to use or implement this
Define RTO/RPO targets, automate backups, and periodically test an actual restore, not just that the backup file exists.
Research questions
- What's Localz's current RPO for its Postgres data — how much data loss is acceptable in the worst case?
Empty folder — drop notes, links, and findings here as you research.