docs(plan): sixth revision of the storage plan: backups done, LVM thin snapshots with kopia, lab proof first #26
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "storage-plan-rev6"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
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.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.