Backups (restic)
Backups rely on restic 🡕: each host pushes its data to an encrypted repository, either local or remote via a zone REST server. The goal is a 3-2-1 strategy (multiple copies, multiple media, one off-site location).
Two roles, one module
Section titled “Two roles, one module”
| Role | Who | What |
|---|---|---|
| REST server | Host with the restic service | Stores zone repositories |
| Client | Host with enable = true | Pushes its targets (backups) |
Backup categories
Section titled “Backup categories”A target backs up one or more categories into sub-repositories:
| Category | Content |
|---|---|
system | Root /, excluding volatile data and /nix, /srv… |
nfs | Shares /srv/nfs/... |
medias | Media /srv/medias/... |
Implementation
Section titled “Implementation”The full operational configuration (REST server, targets, retention policy, restoration) is detailed in the how-to guide: