Reference · Storage & Backup
Data that doesn’t get lost
The backup strategy is built around one concrete disaster scenario: "the boot disk dies." Non-overlapping sets make sure each file is backed up exactly once — and an offsite copy survives even a total local loss.
3-2-1 backup strategy
3
Copies
live + backup + offsite
→
2
Media
NVMe/SSD + HDD on NAS
→
1
Offsite
encrypted in the cloud
Non-overlapping sets · automated · watched by a dead man’s switch.
🧩Non-overlapping sets
Databases, app data and boot configuration are each backed up once with the right tool. No duplication — recovery stays simple to reason about.
🔐Encrypted & versioned
App data lands end-to-end encrypted and versioned in the backup (Kopia) — protection from mistakes as much as from ransomware.
☁️3-2-1 offsite
An additional encrypted copy of the irreplaceable data lives off-site in the cloud — deliberately upload-only, with no read-back.
🔔Dead man’s switch
Every backup job actively reports success. If a report goes missing, monitoring raises an alert — a silent failure is noticed at once.
Stack in use
KopiaPostgreSQL pg_dumpBTRFS snapshotsCloud offsiteUptime Kuma