backup-strategy: note the measured nightly cost
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Fable 5
parent
f9cf92772e
commit
4856010cb5
+1
-1
@@ -10,7 +10,7 @@ docs; this page is the map.
|
|||||||
|---|---|---|
|
|---|---|---|
|
||||||
| **local replication** | `incus copy --refresh` → pool `backup` on ks4's second disk (sdb) | instances, against losing the `data` pool |
|
| **local replication** | `incus copy --refresh` → pool `backup` on ks4's second disk (sdb) | instances, against losing the `data` pool |
|
||||||
| **remote replication** | nuc pulls the same replicas over WireGuard → pool `ks4backup` | instances, against losing ks4 or the site |
|
| **remote replication** | nuc pulls the same replicas over WireGuard → pool `ks4backup` | instances, against losing ks4 or the site |
|
||||||
| **remote backup** | **restic** → S3 bucket `restic-data`: database dumps + selected filesystem trees | the data itself, versioned and encrypted, independent of every disk above |
|
| **remote backup** | **restic** → S3 bucket `restic-data`: database dumps + selected filesystem trees | the data itself, versioned and encrypted, independent of every disk above (a nightly run walks 1.1 M files / 1.24 TiB in under two minutes) |
|
||||||
|
|
||||||
Only two tools are involved: `incus copy` (ZFS-incremental, native to
|
Only two tools are involved: `incus copy` (ZFS-incremental, native to
|
||||||
the platform — a restore is `incus start`) and restic (dedup +
|
the platform — a restore is `incus start`) and restic (dedup +
|
||||||
|
|||||||
Reference in New Issue
Block a user