Engineering Case Study
Designing Backup Redundancy People Will Maintain
The Problem
Hosting retained only one month of rolling backups, and original launch-state files were not being preserved.
Constraints
The process needed to supplement hosting, remain easy to perform quarterly, and make the current recovery point unmistakable.
Approach
I established a quarterly manual backup stored in a single ‘Most Recent Backup’ folder that overwrites the prior quarter. I also added preservation of the original launch state to the launch process.
Outcome
The organization gained a recovery point beyond the host’s rolling window without creating a confusing archive of dated folders.
Looking Back
The ‘Most Recent Backup’ folder intentionally sacrifices historical accumulation for immediate clarity. It supplements rolling hosting backups rather than attempting to replace every recovery layer.
Perspectives
Julie: The most technically complete backup policy is useless when nobody can quickly identify or maintain it.
Jae: One current off-host recovery point. One preserved launch state. No folder archaeology.
Min: Recovery design must account for how people behave during an incident.
Engineering Principles
- Simple and maintained beats comprehensive and abandoned.