View Single Post
Old 09-14-2014, 02:07 AM   #29
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,495
Karma: 8065348
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by cybmole View Post
bear in mind that google drive is not an actual local copy of a cloud - it's not like a sugar sync or dropbox folder . its a "fake" folder whose contents exist only in the cloud. ( there is an offline mode but it is off by default )
It doesn't work like this for me. I have changed no option and with the exception of google docs files, all my data is stored locally.
Quote:
let me start that ball rolling. I have side by side, my local calibre library & my google drive copy. I am opening each author folder in both locations & checking the 4 digit numbers. I checked the 1st 3 authors & get 3 out of 3 matches. so I conclude no corruption, which is what I expected.
Concluding no corruption on three samples is a bit like me concluding that all people in Paris are women (except me) because the last three people that went by my window were women.

I have personally had Google Drive change those numbers. It happened when there were two machines syncing the drive, but the library with the numbers was written by only one machine. I don't know why it did it at that time, but it was indisputable that a four digit number became a single digit. I no longer let my calibre library anywhere near GD for any purpose.

My position: a backup that might change behind your back, even though it apparently hasn't yet, is not a backup. It might be considered an archive, useable as eschwartz says to reconstruct a library by reimporting, but that is not a backup.
chaley is offline   Reply With Quote