I keep multiple dated backups made using a script shell + crontab, to automate the thing.
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”
It lies on my cloud which I backup regularly to a spare computer via restic.
Syncthing. It’s not so much a backup as redundancy, though.
I have machines in the network that rarely get powered on, however, so I could possibly consider them offline backups.
manually. I used to sync via dropbox, but i was never comfortable with that solution.
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
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.
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.
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.
When I was still using it I used Syncthing to distribute copies to multiple devices and that distributed nature also functioned as a backup.
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.kdbxYunohost + Nextcloud
I manually copy it to Proton Drive and access it via android with KeepassDX
Syncthing folder for the databases. Keep an additional key file on a separate storage and memorize a long password.
I sync it using my pCloud folder. In case I’m away and I need access to them, I also have a cron job that copies the most recent version to a webserver I have, under a directory I only know of, protected by a password. My .kbdx files also need a credentials file that can be generated programatically. Secure enough for me.
