It is backed up alongwith everything else, all my data, under a normal 3-2-1 idea, but 5-3-1.
Each of the copies on separate media inc my main PC is also versioned. I keep 12 hourly versions, 7 daily versions, 4 weekly versions, 12 monthly versions, and then per-year versions going way back. This helps protect against corruption, like I accidentally deleted an keepassxc entry without noticing right away or w/e.
I try to follow the 3, 2, 1 backup procedure:
- 3 copies
- Spread across at least 2 devices (Computer, Server, other devices)
- At least 1 copy on a separate storage disk (USB flash drive)
This is the way…
Your KeePass; your documents; your personal data; and your photos.
3-2-1-1 all the things
I usually make a copy once a month of my database, I save it on an external hard drive that I can connect via USB, it probably is not the most practical way but at least it is the best way that is found
I am shocked how many ppl think synchronization like syncthing act as a backup.
No synchronisation is not a backup. If you accidentally delete the database and it syncs across all devices then the database is gone. If something is broken and overrides multiple times then the history if it is enabled is also gone.
Pls use proper backup methods to backup your database.
Edit: I sync my database also with syncthing across devices. But to back it up i have on multiple clients system backups running that include the database.
Syncthing can store multiple versions of things…
So, when you activate simple versioning, and keep the last 20 Versions, then an error occurs (or malicious actor) and overrides the file 20 times. Then the simple versioning is gone.
Yes with the correct setup you could probably backup via syncthing BUT no one in the comments ellaboborated and mostly just says “i sync to multiple devices via syncthing”
Yeah, syncing with default settings is a bad idea for backup, but it’s better than nothing.
A more robust set up, while not foolproof, is to set history to keep all copies for 30 days, not a fixed amount of files. It’s also important to enable conflict detection so if the file was changed on two devices in between sync it keeps both copies (and cross-syncs them).
That’s not my experience, at least with MEGASync.
Manually make a backup with the date in the file name stored in another folder and on a thumb drive.
All my systems backup to a remote box that has a hotswap bay that I rotate the drive every few weeks between another drive. The drive out of the hotswap bay is stored in a fire safe.
This is more all for images and documents, but everything gets the same backup since it’s whole systems. The backups are rsync with hard links so they take up less room.
I keep multiple dated backups made using a script shell + crontab, to automate the thing.
It lies on my cloud which I backup regularly to a spare computer via restic.
I manually copy it to my phone, a thumb drive, a cloud service and another computer whenever I change something. I also let the filename show on which device and on what date the files was last modified. Example:
Passwords_MY-SMARTPHONE_260314.kdbxWhen I was still using it I used Syncthing to distribute copies to multiple devices and that distributed nature also functioned as a backup.
I have mine on a nas server synced with nextcloud.
I backup the file to a separate ssd on a different machine every few days and then backup on a USB in a fire wallet every few months.
Syncthing between my phone, my server, my laptop, and a cloud backup. Home server is always on so it “remembers” the sync to propagate to devices that were not turned on or connected to the internet when the change was made, cloud backup in case of catastrophe
manually. I used to sync via dropbox, but i was never comfortable with that solution.
Syncthing.
I also will make a copy on a usb drive if I’m traveling and keep it in my luggage. Lesson I learned when I broke my phone during a recent trip and didn’t have any way to add a new device to syncthing to retrieve my keepass database. Which was a real pain in the ass.
Yunohost + Nextcloud
I use Vaultwarden, but either way most of my home server data gets backed up by getting encrypted and uploaded to Backblaze regularly/automatically.
If that fails well each client has a copy of the data, so just one has to survive.








