0037 (ADR-014): Backup as a destination appliance #42
Labels
No labels
accessibility
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Keel-Linux/tracker#42
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Decision (maintainer, 2026-09-30). TKLBAM stays as the client (profile/delta backup, duplicity). New Keel Backup appliance (storage backend + key service), installable by anyone as LXC or VM. The backup manifest is derived from the composition manifest. A destination is never in the same site as its data (refuse, or warn loudly in simple). Restores tested periodically into a throwaway container, reported to etcd. Database backups taken from the hot standby. TKLBAM gets a backend abstraction to target Keel Backup instead of Hub + S3. Depends on 0038.
Handbook:
docs/decisions/0037-backup-destination-appliance.md(handbook#26)Amends: 0002 (the TKLBAM port is defined: a backend abstraction), 0014 section 2 (open; the "no backup service" line is superseded when this lands), 0013 problem 5 (backups from the standby).
First tasks