docs(plan): sixth revision of the storage plan: backups done, LVM thin snapshots with kopia, lab proof first #26

Open
beddari wants to merge 1 commit from storage-plan-rev6 into main
Owner

The storage plan, sixth revision. The backups step is complete (hov1 live 2026-09-20, WAL archiving and daily base backups on both clusters, first restore test passed 2026-09-21) and becomes a Done record. The mechanism under the databases changes from the static provisioner (decision 007) to OpenEBS LVM LocalPV thin on an LVM volume group Talos creates (RawVolumeConfig + LVMVolumeGroupConfig), so CNPG takes cold volume snapshots from a standby and kopia ships them off the node; barman-cloud keeps the WAL everywhere. New building block 7 says why (community measurements: multi-terabyte restores from snapshots in minutes; object-store base backups fine below about half a terabyte) and what the driver choice gives up against ZFS, LINSTOR and TopoLVM. New step 1 is a lab proof with four checks and measured numbers before anything touches production. Steps 2 to 4 follow the new layout; the file backups move to step 4 on kopia (bucket files-forgejo). Alerts, operations, expansions and both placement tables updated. The backup READMEs, the top-level names table and bin/user say kopia instead of restic.

The storage plan, sixth revision. The backups step is complete (hov1 live 2026-09-20, WAL archiving and daily base backups on both clusters, first restore test passed 2026-09-21) and becomes a Done record. The mechanism under the databases changes from the static provisioner (decision 007) to OpenEBS LVM LocalPV thin on an LVM volume group Talos creates (RawVolumeConfig + LVMVolumeGroupConfig), so CNPG takes cold volume snapshots from a standby and kopia ships them off the node; barman-cloud keeps the WAL everywhere. New building block 7 says why (community measurements: multi-terabyte restores from snapshots in minutes; object-store base backups fine below about half a terabyte) and what the driver choice gives up against ZFS, LINSTOR and TopoLVM. New step 1 is a lab proof with four checks and measured numbers before anything touches production. Steps 2 to 4 follow the new layout; the file backups move to step 4 on kopia (bucket files-forgejo). Alerts, operations, expansions and both placement tables updated. The backup READMEs, the top-level names table and bin/user say kopia instead of restic.
This pull request has changes conflicting with the target branch.
  • backup/README.md
  • docs/plans/2026-09-storage-building-blocks.md
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin storage-plan-rev6:storage-plan-rev6
git switch storage-plan-rev6

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff storage-plan-rev6
git switch storage-plan-rev6
git rebase main
git switch main
git merge --ff-only storage-plan-rev6
git switch storage-plan-rev6
git rebase main
git switch main
git merge --no-ff storage-plan-rev6
git switch main
git merge --squash storage-plan-rev6
git switch main
git merge --ff-only storage-plan-rev6
git switch main
git merge storage-plan-rev6
git push origin main
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
dataverket/fabrikk-infra!26
No description provided.