I agree with others here about file sync priority / pausing etc and better enterprise support.
I also have emailed twice with a suggestion for something I am calling ‘pull mode’ and have got no response.
Pull mode would basically work like rsync or a p2p sync client where changes in the cloud are only pulled to the client and not changes on the client sent back (to prevent local data corruption from being pushed back to the cloud). The next bit is critical: archive off changes and deletions in a (user definable?) folder. Again, think rsync/syncthing/resilio etc. Why? Pick one of many reasons. Bitrot, Ransomware etc. Google does NOT protect from any of this. Whereas services with a more generous undelete/version history do. By the time a nasty ransomware has taken more than 30 days on an older box to encrypt the lot, your version history and files are gone and all nicely synced to every computer you run Insync/drive on. I can find plenty of people on Google’s forums that have been on the receiving end of Google’s 30 day limit plus the very nature of cloud sync screwing them over.
Having a pull only mode on a separate box running a self healing file system like Btrfs or Zfs would go a long way to mitigate some of this risk. If the data on the box gets corrupt, it won’t push back. If the cloud gets contaminated and syncs, the originals are still there in invisible folders.
It would be great if this would at least be considered.