Windows: Selective Syncing suddenly not working

Bugs and issues
1

At the beginning of the week, Windows v1.3.3 working great, but today I, the list of folders/files are not updating with the latest info from Google Drive. Lots of activity in inSync and status is stating “Scanning for changes…”

Could recent Windows 7 updates have caused issues with InSync?

Btw, my DB files for inSync are huge!

Screenshot_12_23_15__11_21_AM.png717×169 15.2 KB

2

I will tag our engineer @dipesh and he will get back to you next week regarding this issue.

Thanks!

3

@CBECGoogle_Apps, Sorry for not being able to get back to this any sooner. How is the sync status now?

“Scanning for changes…” state means that Insync is either busy fetching the changes from your Google Drive or busy scanning the local folder (to look for changes that were done while Insync was paused/not running) or both. This phase may take a while if you have a huge local folder or if there are a lot of changes made in your Google Drive since the last run. So, it is recommended that you do not pause/quit Insync and let it run for long intervals.

If the local files don’t change while Insync is not running, you may want to skip this local folder scan by disabling Insync auto-start on system startup and starting Insync via command-line with the following command:

%appdata%\Insync\App\Insync.exe --skip-local-scan

This will make it skip the local folder scan to scan for changes while it wasn’t running and hence it would proceed to the transfers faster.

If you want to start Insync on the system startup with this flag set, kindly do the following:

  1. Go to %appdata%\Microsoft\Windows\Start Menu\Programs\Startup
  2. Right click Insync shortcut -> click Properties
  3. In the “Target” field under the “Shortcut” tab append --skip-local-scan (See: https://mrkr.io/EIZWUDQYp2)
  4. Click Apply

Thanks

4

Thanks for your response. The sync never started up again… I ended up quitting the app, deleting the two gd2-.db & gd2-.db-wal files in C:\Users\User\AppData\Roaming\Insync\dbs and then restarting Insync, and completing the connection setup.

It seems to be working OK now.

Regarding skipping the local scan. We have Insync running on startup of the machines. Should we follow your instructions then to skip the local scan?

5

@CBECGoogle_Apps: If you are experiencing significant delay in syncing during startup and you are sure that you do not change or move around files locally between quitting Insync and the system startup, then you may consider following the 4 steps procedure to skip the initial local scan.

Thanks

6

Thanks for all your effort. I will test your suggestion. OK to close.