LinkedIn
Twitter
Over the years I have generally found the root of a digital fault is in the user end and we have been committed to rebuild Drive for users' due to a routine maintenance storage re-structure.
Following the upgrade and moving the still and some live data, Drive commenced re-syncing to a new remote computer profile; Time to study this app and how to resolve !
The new computer variant was left live for several weeks and did synchronise some data (with all the directory structure) but as it went deeper in, memory consumption spiked and the server halted every few hours due to congestion in some larger binaries.
Working around this is explained elsewhere in fragments but what we did today, (when no-one is in the center, Sunday) was:
- Disconnect the account
- Reconnect and find that no folders were monitored
- Start with a smaller folder with limited content (8GB only) and add it to "My Computer" in the drive client
- This caused the app to test the tombstone at the cloud and reported that the directory was present and "continuing" merged the user data with the cloud in a few minutes, because it connected with the original profile which was intact (but out of date)
- After eight hours or more, memory usage is less than 600MB and several complex primary folders are synced
- Streaming access only
- Should be all matched in sync' in just a few days at this rate
- Avoid multiple large and complex directory synchronisations
At the time of the post above, a version release also occurred (99.x to 100.x), so it is likely that that solved the memory utilisation; Very good ๐
https://support.google.com/a/answer/7577057?hl=en
