From a1e5732d1f34e8854fe912d93706e0854d33c16f Mon Sep 17 00:00:00 2001 From: automation-bot Date: Fri, 18 Sep 2026 23:26:42 +0300 Subject: [PATCH] docs: fix disaster-recovery.md drift (Kopia stack count, stale evidence) Kopia's coverage claim conflated the public repo's curated stacks/ folder (a documentation subset) with the real live stack count on rocky-docker - fixed to the actual live figure (41, cross-checked against docker_stacks.yml and the real repo directory count), same fix applied to the source KB note which had its own stale ~38 figure and an incorrect hyper1 backup mode (suspend -> stop, confirmed against live /etc/pve/jobs.cfg). Refreshed the ls/df and roles_metadata.yml command-output evidence to match current state. --- docs/disaster-recovery.md | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/docs/disaster-recovery.md b/docs/disaster-recovery.md index 8157bae..191f994 100644 --- a/docs/disaster-recovery.md +++ b/docs/disaster-recovery.md @@ -1,6 +1,6 @@ - @@ -21,23 +21,24 @@ A single backup tool covering everything was the simpler design, and it was reje |---|---|---| | Infrastructure as Code | A host lost entirely, VM or LXC alike — rebuilt from the same pipeline that built it ([`docs/iac-pipeline.md`](iac-pipeline.md)), against its existing tag-driven config | Secrets — recovered separately via Vault, see [`docs/secrets-and-pki.md`](secrets-and-pki.md), not part of this layer | | Proxmox Backup Server | Full VM/LXC backups, including the secrets platform's own seal state and Vault's own data described in [`docs/secrets-and-pki.md`](secrets-and-pki.md) | One host's Docker volume data, a large media storage pool, personal data | -| Kopia | The gap the layer above leaves — every stack's databases, uploaded files, and app config on the fleet's largest host, covering the ~55 stacks in [`stacks/`](../stacks/) | Anything outside that one host | +| Kopia | The gap the layer above leaves — every stack's databases, uploaded files, and app config on the fleet's largest host, covering all 41 stacks running there | Anything outside that one host | This is the real Kopia repository, not a description of it — a dedicated set of directories on its own separate disk, confirmed live: ``` $ ls /mnt/samsungssd -kopia-cache kopia-config kopia-repo kopia-tls +kopia-cache kopia-config kopia-repo kopia-tls recovery $ df -h /mnt/samsungssd Filesystem Size Used Avail Use% Mounted on -/dev/nvme0n1p1 234G 65G 167G 28% /mnt/samsungssd +/dev/nvme0n1p1 234G 75G 157G 33% /mnt/samsungssd ``` Layer 1's "rebuilt against its existing tag-driven config" claim is a real, checkable mechanism too — every role in the pipeline declares which of the three rebuild stages it belongs to: ``` -$ head -12 roles_metadata.yml +$ head -14 roles_metadata.yml roles_metadata: + # Bootstrap roles base_users: initialization: true provisioning: false