Quote:
Originally Posted by ratinox
This is not entirely accurate.
Leaving aside Dropbox in particular, the root problem is that multiple instances of an open database file on replicated or shared storage will result in corruption. Instance 1 writes, replication system replicates, but Instance 2 does not know that the file is changed so it writes and damages the file. This damage is replicated back to Instance 1's filesystem but Instance 1 does not know of these changes so it writes and causes further damage. The more times this happens, the more damage is done.
Dropbox in particular may have additional problems. I don't use it so I don't know. I do use Syncthing, being careful to avoid Calibre concurrency, and it has been fine for many years.
|
Very well said.
Another example is someone with Google Drive. The active library gets synced to Google Drive and then corrupted and synced back and the active library then become corrupted.