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.

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.kdbx

When I was still using it I used Syncthing to distribute copies to multiple devices and that distributed nature also functioned as a backup.

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 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.

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.

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)

I manually copy it to Proton Drive and access it via android with KeepassDX

Yunohost + Nextcloud

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.

Syncthing folder for the databases. Keep an additional key file on a separate storage and memorize a long password.

Several flash drives stored at different places. I update them either once every three months or when I make an incredibly important change to one of the entries in the database.

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.

Webdav (of my mail provider)

I copy it to external hard drives. It also syncs to other devices via Syncthing and Syncthing-Fork.

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.

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.

It lies on my cloud which I backup regularly to a spare computer via restic.

I keep multiple dated backups made using a script shell + crontab, to automate the thing.

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

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 save a copy on my PC regularly (because I use keepassdx primarily, an android-only client), and I upload it to signal. Yes, I use signal as cloud storage, and it works really well! I have peace of mind that the file is encrypted using top-notch encryption, and only accessible by my linked devices.