feat(backup): dump Vaultwarden before each backup #7
Loading…
Reference in a new issue
No description provided.
Delete branch "jonnxor/feat/backup-vaultwarden"
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?
Backs up Vaultwarden, following the Forgejo and Kuma dumps. Must be merged before real passwords go in.
dump_vaultwardenusesvaultwarden backupfor a consistent database copy and archives it withrsa_key.pem, attachments and sends to~/Backups/vaultwarden/vaultwarden-dump.tar, owner-readable only. A failed dump keeps the last good one and doesn't stop the backup.include.txtcovers the new path, andverifychecks the dump is readable and containsdb.sqlite3.docs/recovery.mdhas the restore steps.A bug the rehearsal caught: busybox tar keeps only the last
-C, so the first version archived the livedb.sqlite3and missed everything in its WAL; the restore came back with 0 accounts. Everything is now archived from one directory. Kuma's dump uses GNU tar and isn't affected: its archived database matched the.backupcopy.Tested on hades: the dump against the live container (temp files cleaned up), the failure and not-running cases on the first version, and a restore into a throwaway instance (1 account and 2 devices, same as live; integrity check ok;
/alive200).Not tested: a full
mise run backuporbackup:verifythrough restic. The vault holds no items yet, so attachments and sends weren't exercised.Timing: the monthly verify runs on 2026-11-01 around 09:46, after the nightly backup around 03:05. Merge and pull before the backup, or after verify; in between, verify raises a false alarm.
🤖 Generated with Claude Code
d47751653a3eae91565e