Sync Database with multiple Files

[Stefan Murawski]

Hi All

I have:
Google Drive KeePass DB.
I sync this DB to 4 local DBs on 4 PCs and work on the local DBs.

But google drive is sometimes not the fastest, that 2 pcs sync at the same time and "DB conflict" occure. Some weeks past, I do have 6 or 20 db "conflicts".

There is the option File -> Sync -> Sync with Files for syning 1 file.
I sync then manually all conflicts with the main db and delete them. Everything is good.
But, 24 files to sync need manual doing.

I can't make a trigger which (tools missing):

Take all Files DB*.kdbx
Foreach file do sync
done.

How can I archive that? Is there a way? or is there only the manual way unfortunatly?

Thanks for the help.

(unfortunalty, I have limited C knowledge, that KPS from nothing to working is not possible)

Regards Stefan

[steelej]

I don't know how this works with Google Drive. With other cloud services there is a step by step guide

https://keepass.info/help/kb/trigger_examples.html#dbsync

The principle is that you have a "master copy" in the cloud service and sycronise each local copy to that. Any local copy syncronises to the "cloud copy. And this virtually eliminates all resk of conflicted copies.

The only conflict would be if two users updated the smae KeePass record.

[Paul]

You do not need to sync the conflicted copies, only the main database.
Each local copy will sync with the cloud database and eventually everyone will catch up. No data will be lost because the local files will always contain local data.

You should still backup each machine to ensure you don't lose local changes that have not yet made it to the cloud / other machines.

cheers, Paul

[Stefan Murawski]

For both of you. I exaclty do that what is described within the link.
But that was not the question. Did you read it?

When using any cloud storage, when sync conflicts occure, if google drive, dropbox or one drive, all have the same issue. Do you use the same setup that you can help?

When 2 clients sync the local db with the "cloud DB" an condlict occure.

So again, Is there somebody able to help me generating a KPS to sync a db with all conflicts and then remove them.

[steelej]

If you follow the syncronisation method described in the help files the confilcts reported by the cloud service can be ignored.

There willl be NO loss of data. All of your users will get identical data record in the LOCAL copies. If might take more than one syncronisation to achieve this if the various local databases are undated frequently.

It is important to realise that the local copies will never be idenmtical at the binary level but they will contain the same records. While the current data items will each become identical their histories may have the changes in a different order on each device. Your local copies will however all contain identical records. Syncronmisation takes place at the KeePass record level. None of your files will be identical if you do a binaray comparison.

Conflicts reported by the cloud provider are unavoidable but totally irellevant and should be ignored.

[Jim D]

it cannot be claimed that no loss of data will occur, if the files that are being synced to are still local files and not the actual cloud hosted files. i use the onedrive plugin as i have had situations where DB is conflicted because the onedrive app running on my local machine didn't update fast enough and i added 2 entries within a few seconds of each other on 2 different computers and only one was seen after. onedrive didn't report a conflict or anything, just saved multiple versions of the same file. so my advise is use a plugin. it will always retieve the latest file, merge, then upload (at least the onedrive sync does). no data loss since using it.

[steelej]

If you follow the description for synchronisation with a cloud service correctly there can only be a conflict if the SAME KeePass record is updated on BOTH computers at the same time.

If you attempt to have all computers directly opening the same database file that is directly synchronised via the cloud then conflicts like you describe are inevitable and unavoidable.

If you follow the advised method there is a window where your two remote databases may take more than one synchronisation for the CONTENT to be the same in all machines but no data will be lost. If both update the same RECORD then one will win but the other will be retained in the file history.

Note that the two local copies will have identical records but will NOT be identical at the binary level. Nether will they be identical at the binary level with the cloud synchronised copy.