View Single Post
Old 11-19-2019, 12:21 PM   #4
theducks
Well trained by Cats
theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.
 
theducks's Avatar
 
Posts: 31,152
Karma: 60406498
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
Quote:
Originally Posted by beejsbj View Post
i see, so is the only problem with cloud storages the syncing causing problems with different versions? what if your whole library is just based in the cloud which wouldn't require sync(which is ideally what id want)
Not a version issue (in most cases), but a Transaction issue.
Calibre write to a number of files on adding or modifying a book (or many books). Thees MUST happen as done and remain in lockstep. Miss or delay and things start to fall apart. Bring back an older part and , it may be out of date, not match the current. File Timestamps may not save you.

Again. it is When, not If it will fail. Murph says, it will happen BIG TIME and when you need access the most

(BTW GD modifies file names, which is why that is a total disaster )
None of this precludes storing a Backup ARCHIVE (eg spanned Zip or RAR...) of an entire library
theducks is online now   Reply With Quote