Forum Discussion
Huge Sync Issues with Large Libary - Need Help :(
Yes. Documentation is here.
Although SharePoint Online can store 30 million documents per library, the sync performance of OneDrive may start to decline when you store more than 100,000 files in a single OneDrive for Business site or team site library. To resolve this limitation, ensure that files are stored in multiple folders/libraries. If you have more than 100,000 files in a OneDrive for Business site, you may need to wait an extended period of time with OneDrive continuously syncing before sync can complete.There are other limits on viewing a document library using the web that may affect how you structure your files in OneDrive.We're always working to optimize OneDrive to better handle libraries with a large number of files.
i would start by splitting the library up into many libraries, using the top level folders as new libraries could be a good starting point. I would also want to know why users think they need so many files when they are working offline, if they need a certain set of files, those could be put into their own library for improved management flexibility.
Agreed, splitting up the library will be the second step in this process.
As for the users need. They don't actually need those files offline, that is way we've waited until to Win10 1709 to use Files on Demand. Actually the users only has a few GB offline available. What they do need tho is easy access to their documents, which the browser view currently doesn't offer.
I'm still stuck on the first step of the recovery process. I think I can limit the out of sync clients to a single user at the moment. Which makes this a little easier to resolve.
I'm kind of stumbling over Windows 10 1709 file handling of synced libraries at the moment.
My first instinct was to sync the library with some other tool, like the new SharePoint Migration Utility. The goal is to upload the missing documents that were created on the client but haven't been uploaded yet. Unfortunately am unable to accomplish this, as the Migration Utility somehow can't read the folder structure.
Any ideas? I don't think splitting up the library before will help in any way, because of the way OneDrive/Windows handles the synced files.
I ran into this issue once and I was able to use Teracopy from the original source, chose to "Skip all" of the files that already existed, and it went in and replaced all missing folders and documents.
Are you able to identify and select locally (i.e. on the client) the out-of-sync files?
Hi Ivan. I have a couple of suggestions to help resolve the issue, but they both involve using commercial tools so hope you don't mind.
Firstly to identify the files that have not yet synced you could try using Files To Go. http://www.thinkscape.com/SharePoint-Online-File-Migration-Tool/#IncrementalMigration so should identify only new and modified files for migration. Just be sure your local and target root folder matches when choosing your source and destination in Files To Go then Files To Go can perform an accurate analysis.
To work with the large library after you have migrated the unsynced files across you could try using Zee Drive. http://www.thinkscape.com/Map-Network-Drives-To-Office-365-OneDrive/. It should work fine with a large 300,000 item document library.
Disclosure: both Files To Go and Zee Drive are tools my company develops.
Regards,
Myles
