Is Google Drive safe as backup and sync?

johnbw · 12-31-2020, 11:32 AM

Is it safe to maintain a library on a Google Drive if the drive is only used for backup and/or when fully sync'd across endpoints?

The plan is to only work on calibre on a single endpoint at a time (Win10 PC), and only on multiple endpoints (non-concurrently) if the library is fully sync'd first with the on-line copy and any other endpoints. A sort of manual file-locking protocol.

I've seen previous posts that warn of corruption but want to confirm this only happens if the library is modified concurrently from multiple endpoints.

Thanks

theducks · 12-31-2020, 11:37 AM

Multiple access was not specifically the issue with GD.
Changing the file names (to include versioning info) IS the issue

You CAN use GD if you first ZIP up the backup as GD does not mess with file internals

chaley · 12-31-2020, 11:58 AM

GD once destroyed one of my test libraries that was accessed on only one computer. Calibre puts id numbers in parentheses on some directory names. GD changed many of them, rendering my library useless.

I can't say whether or not GD still has that behavior.

johnbw · 12-31-2020, 11:58 AM

Quote:

Originally Posted by theducks

Multiple access was not specifically the issue with GD.
Changing the file names (to include versioning info) IS the issue

You CAN use GD if you first ZIP up the backup as GD does not mess with file internals

Great - thanks. So the recommended process would be:

Work with the library on a non-GD
Zip snapshots of library versions to a GD
Unzip GD snapshots to non-GD space on any other endpoints
Repeat as needed

12-31-2020, 11:32 AM	#1
johnbw Agile eBooks Posts: 6 Karma: 10 Join Date: Aug 2011 Device: kindle	Is Google Drive safe as backup and sync? Is it safe to maintain a library on a Google Drive if the drive is only used for backup and/or when fully sync'd across endpoints? The plan is to only work on calibre on a single endpoint at a time (Win10 PC), and only on multiple endpoints (non-concurrently) if the library is fully sync'd first with the on-line copy and any other endpoints. A sort of manual file-locking protocol. I've seen previous posts that warn of corruption but want to confirm this only happens if the library is modified concurrently from multiple endpoints. Thanks

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Problems with sync by Google Drive because too long path	Daniel Roziecki	Related Tools	2	09-07-2013 12:30 AM
Reading app with freehand annotations and cloud sync (Dropbox, Google Drive, ...)	sjvs	Reading and Management	1	08-30-2013 03:18 PM
Does Google Drive sync edited back to the cloud?	cptnemo	Android Devices	2	10-22-2012 12:00 AM
Problem Sync with Ez PDF and Google Drive	cptnemo	Android Devices	0	09-27-2012 09:33 PM

12-31-2020, 11:37 AM	#2
theducks Well trained by Cats Posts: 30,942 Karma: 60358908 Join Date: Aug 2009 Location: The Central Coast of California Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A	Multiple access was not specifically the issue with GD. Changing the file names (to include versioning info) IS the issue You CAN use GD if you first ZIP up the backup as GD does not mess with file internals

12-31-2020, 11:58 AM	#3
chaley Grand Sorcerer Posts: 12,364 Karma: 8012652 Join Date: Jan 2010 Location: Notts, England Device: Kobo Libra 2	GD once destroyed one of my test libraries that was accessed on only one computer. Calibre puts id numbers in parentheses on some directory names. GD changed many of them, rendering my library useless. I can't say whether or not GD still has that behavior.