Cleaning up Google Drive (for instance when a rogue supplier decides to fill your Windows Documents folder) and preventing TomTom HOME to use too much information
Posted by jpluimers on 2022/04/12
The below links helped me clean the Google Drive of a friend that grew way too large because TomTom HOME decided to put 100 gigabyte of data in the Documents folder instead of the local AppData folder (yup, this is a follow-up of Windows applications: storing your data in the correct place (Roaming, Local, LocalLow, not Documents)).
- [Wayback] support.google.com/drive/answer/6374270
- one.google.com/storage shows an overview on the storage used by email, drive and photos.
- drive.google.com/drive/quota allows sorting ALL files in your Google drive by descending size so you can delete them
- one.google.com/storage/management allows to deleted/spam emails, or large files, emails or photos/videos in your Google account
- drive.google.com/drive/trash allows you to empty the trash, as these files still consume storage space
The trick with extensions to exclude is you have to add exclusions before syncing. Which is a kind of catch-22 or chicken and egg problem.
In case of the friend I helped we made a backup of the TomTom HOME data, then applied the exclusions and restored the data.
For TomTom HOME in order not to fill your Google Drive, but still allow backing up your Documents
folder, these are extensions you might want to exclude (roughly in descending order of space) where you have to mind not storing any of these extensions in other subfolders of your Documents
folder.:
.zip
.cab
.toc
.tmp
.meta
.sat
.tlv
.ttd
.dat
.vif
.chk
.bin
.rex
.lde
.gpr
.dbl
.so
.ov2
The problem with this? Google Backup and Sync does not allow that many exclusion extensions.
–jeroen
Leave a Reply