Forum Discussion
Onedrive used the 'mklink' command to synchronize files for too long
I used to use the 'mklink' command to synchronize files on other drives to onedrive, but for some reasons, I had to reinstall the system. However, when I reinstall the system and synchronize the file...
If any of your file metadata has altered e.g. my your sync tool changing the modified date, then the OneDrive agent has to compare every file with its online record, so it's going to take as long as your local environment and connection speed require.
As comparison I had to do the same thing with Dropbox last week after a local HDD failure required re-syncing 2TB of files, which took several days to complete. The processing time is going to be dependent on both #files and #bytes - the handshake for each file is about the same irrespective of size.
My recommendation in this situation is to minimize the number of files that are kept locally, particularly when you have many thousands of small files in some folders. Moving infrequently used collections of small files into zip archives also helps.
As comparison I had to do the same thing with Dropbox last week after a local HDD failure required re-syncing 2TB of files, which took several days to complete. The processing time is going to be dependent on both #files and #bytes - the handshake for each file is about the same irrespective of size.
My recommendation in this situation is to minimize the number of files that are kept locally, particularly when you have many thousands of small files in some folders. Moving infrequently used collections of small files into zip archives also helps.
At present, the time of file handshake has almost exceeded the time I used to synchronize 3TB data. If this continues, I might as well delete all the files in onedrive and synchronize them again.