Backup and Sync auto-deleting local copies of backed-up files, Google’s investigating [updated]
Here’s a Google suggested workaround till the company debugs the issue in question:
Workaround for now is to go to Preferences and uncheck syncing the Google Drive folder. Click apply and let the app settle. Then go back and recheck it. IT should force detect any missing files and fill them in.
Original story below:
Fraught with bugs, Google Drive and Photos common client Backup and Sync’s journey so far has been quite bumpy. While it’s been frequently updated, the improved versions somehow end up bringing more issues than they fix. The latest problem gaining lime light is that the client is automatically deleting local copies of backed up files from the system.
The official Drive help forum is drenched with such complaints, with both Windows and Mac users reporting that Backup and Sync (v3.37) is deleting files/ folders from the local Drive folder on their system without any permission.
In addition, users have also started raising the issue on Twitter:
@googledrive why the last google backup and sync deletes my files ? or a entire folder ??
— Seven (@SevenBlue_) October 26, 2017
@googledrive WHY IS BACKUP AND SYNC DELETING EVERYTHING!!! I'M MISSING A LOT OF FILES. . .WILL I GET THEM BACK?
— David Rutherford (@DRuth44) November 2, 2017
Coming back to the problem, needless to say, the deleted stuff awaits in the system’s trash folder. For what it’s worth, those affected also mention that the Backup and Sync icon in the system tray appears to be stuck on syncing ‘1 of 1.’
Sadly, quitting the app is not an option, as it repeats the deletion behavior every time it’s restarted. The only relief is that the corresponding backed up copies stay unaffected on cloud.
Until now, a lot of users have posted the typical ‘me too’ post on the thread discussing the problem. The good news, meanwhile, is that Google has finally swung into action. Google employee Rishi (who is also the Community Manager at Google Drive Help Forum) is asking users to share their log-files to debug the issue in question.
Would you mind sharing your log files with drive-debug at google.com? We are looking into this issue
Here are the details that he asked for:
- 1. What OS you are running?
- 2. What version of the app you are running?
- 3. Downloading the latest version of 3.37 (3.37.7411.4599) from https://www.google.com/drive/download/ and installing it over your current version to see if the issue is resolved?
We are hopeful that the company will catch hold of the root cause, and fix the problem soon. Meanwhile, you stay connected for all future updates on the matter.