📘 Volume 6 — Operations
Make it last. Backups, monitoring, security, capacity, disaster recovery. The volume that turns a build into a system.
The NAS is built, the apps are running, the family uses it, the creator uses it, the lab runs on it. The question becomes: how do I keep this working for years? This volume covers the operations: backups, monitoring, security, capacity planning, disaster recovery, updates, the runbook. The discipline of operations is what turns a working system into a lasting one.
What this volume covers
Operations is the discipline of keeping a system running. The seven chapters:
- The 3-2-1 rule — backups in depth, the discipline that protects against disaster
- Monitoring and alerting — knowing what's working, knowing when something breaks
- Security hardening — the layers that protect against attackers
- Capacity planning — predicting when you'll need more, and acting before you do
- Disaster recovery — what to do when the worst happens
- Update strategy — the discipline of keeping software current without breaking things
- The runbook — the documentation that turns operations into a habit
Chapters
📖 Ch 01 · The 3-2-1 Rule
Backups in depth. Three copies, two media, one offsite. The discipline that protects against disaster.
12 min read📖 Ch 02 · Monitoring and Alerting
Knowing what's working, knowing when something breaks. The discipline of observability.
12 min read📖 Ch 03 · Security Hardening
The layers that protect against attackers. Defense in depth.
15 min read📖 Ch 04 · Capacity Planning
Predicting when you'll need more. The math, the signs, the timing.
10 min read📖 Ch 05 · Disaster Recovery
What to do when the worst happens. The playbooks, the practice, the recovery.
12 min read📖 Ch 06 · Update Strategy
Keeping software current without breaking things. The discipline of patching.
10 min read📖 Ch 07 · The Runbook
The documentation that turns operations into a habit. The single source of truth.
10 min read📖 Ch 08 · UPS & Power Protection
The cheapest data integrity insurance you can buy. Sizing, runtime, graceful shutdown.
10 min readThe "operations" mindset
Building is a sprint. Operations is a marathon. The discipline of operations is the discipline of doing the small, regular, important work that keeps a system running for years. It's not exciting. It's not the part of the conversation that gets people excited. It's the part that makes the system last.
What you'll know by the end
- How to apply 3-2-1 to every dataset that matters
- How to set up monitoring and alerting
- How to harden the system against attackers
- How to plan capacity for years of growth
- How to recover from disasters
- How to update software without breaking things
- How to document it all in a runbook
Operations is a habit, not a project. The system isn't "operational" once and forever; it's operational because you keep doing the small things. The volume gives you the patterns; the discipline is making them part of the rhythm. Once a month, look at the alerts. Once a quarter, test the backups. Once a year, replace the aging drives. The habit is what makes the system last.