A Scrivener project appears to be a single thing within Scrivener, but in the file system, it is actually a folder containing an index, sub-folders and tens, hundreds, thousands or more individual files, depending on how you organize and granulize your projects. Essentially, a database. Of which many pieces are likely opened and modified during any Scrivener session, no matter how brief or how few if any changes are made. Some cloud sync services have trouble dealing with such numbers and frequencies of activity. As I understand it, this holds true for both Windows and the Mac’s OS X, even though OS X hides the details of the project folder’s contents by presenting it to the user as a “package”. To cloud sync services and backup utilities, however, it always looks like described above, even if the details are hidden from the user.
For background on this, read the articles under Cloud Syncing in the Knowledge Base at scrivener.tenderapp.com/help/kb
A workaround for Google Drive…
- Create/edit/maintain your live Scrivener projects somewhere else on your local internal drive than in the Google Drive folder
- Periodically, in Scrivener, when in a live project that also needs backed up to some place like Google Drive, do a File > Back Up > Back Up To, of the project currently open, to the Google Drive folder, being sure to set/check/use the “Backup as ZIP file” option. This can be to a different location (i.e. the Google Drive folder) than where the live project and routine backups reside locally.
This compresses the entire project (folder, index, subfolders and many files therein) into a single physical .ZIP file that Google Drive should be able to handle reliably. Then be sure to leave the PC on long enough after that for Google Drive to actually sync that new backup file up to Google.
It helps, to assure that the name given to the .ZIP file includes project name, date, and time. Date/time stamps in file systems can get changed for a variety of reasons. Having date/time in the file name itself assures separation, identification, and multiple versions of backups (rather than, say, just overwriting a single file over and over again, which is risky).
In the event that you need to recover from such a backup that is up on Google, download/copy it out to someplace else on your local drive and use Windows or some ZIP utility to unzip/decompress it back out into the folder/subfolders/files that compromise the project and you’ll be able to then work on that.
It’s worth testing this, or any other backup/sync scheme or service, periodically, to assure that it is current and working as you assume it is. You may also want to periodically copy the backup ZIP files to USB thumb drives, CDs, DVDs, etc.
The compressed .ZIP file version of the project created above constitutes the “simple” file (i.e. single physical file) that the knowledge base article about Google Drive refers to.
Hope that is of some assistance.