Tag: Backups

The Recovery Runbook You Should Have Written Six Months Ago

Halfway through writing the recovery procedure for a stack you've been running for two years, you realize you don't know where the .env file actually lives, whether the named volume is app_data or app-data, or what network_mode: host is doing on that one service

How Deep Does the Recovery Documentation Need to Go?

The Architecture post for this idea draws the line between data resilience and operational resilience , between the backup job completing and actually being able to rebuild your environment. That line is the reason you're here. The decision this post is about is what comes next: given that the

The 3-2-1 Rule Covers Data. It Doesn't Cover Knowledge.

The 3-2-1 backup rule is useful because it's specific. Three copies of your data. Two different storage media. One offsite. That specificity is what made it spread — it's a checklist, not a philosophy. You can implement it, verify it, and cross it off. The backup job