Improve the feature of synchronizing more than 100,000 items on a stable basis for OneDrive.
I am aware of the behavior the restriction mentioned that the sync performance will possibly deteriorate when the stored items in the library exceed 100,000 items more. However, I need to operate this process frequently so that I wish the feature will be improved enables sync more than 100,000 items on a stable basis as soon as possible.
Although I have concerns about if the synchronization is going to be impossible to proceed unexpectly, but so as MS described as "We are working on optimization of OneDrive to improve processing of many Libraries." below the Reference information.
Title: Restrictions on synchronizing files and folders
Thank you for your continued support.
We are working on changes to improve the experience when syncing large file collections.
If the /settings/***.DAT file exceeds 4GB One-drive completely crashes and no longer functions. I assume this is due to a large number of files in the one drive folder.
Allowing for certain folder exclusions could prevent this for many.
Can we get an update on where your up to with the improvements to large file collection syncs are yet - we have multiple customers who are now facing the issue as their syncing over 300,000 files -
It's becoming quite common for business data sets OneDrive to have larger than 300k files and our support desk is now getting calls regularly about this issue to which there is no resolution yet
Let us know, thanks.
In my OneDrive I have currently about 315000 files - on my private PC. When using OneDrive for business needs, I will have more. As a software developer working for multiple huge enterprises, I would expect OneDrive to handle multi-million files without any issues.
William Hilsum commented
Any news here at all? This is ludicrous that you have gone so long without an update.
The fact is, Onedrive syncing is just broken on large file counts - even some of our libraries with only 40k items suffer.
Dropbox has high IO on mechanical drives, but, a NVME fixes things and it can run very well with a library of 900k files, and likewise, not seen any problem with Google Drive.
The shocking thing is, Onedrive appears to work quite well on a Mac, but, it just seems that you can't get your act in order on Windows which makes no sense at all.
In fact, I would go to say that third party apps that mount Onedrive as a network drive do the job "ok" and I would say that you really need to reintroduce this feature in a supported way as it is so much more reliable.
We are on the verge of moving away from Onedrive and to Azure Files or back to a third party tool as we can't go on with this...
Microsoft, what is your status on this problem? We have been suffering with sync breakdowns for 2-1/2 years now. Files On-Demand helped but did not solve the problem, and we have suffered data loss because of the problem. Sometimes, the sync becomes so broken that it simply gives up and starts over, but gets no farther the second time or the third, and a user's local changes will never be synchronized to SharePoint Online. Office 365 Enterprise Support always refuses to help us collect data that you could use to diagnose the problem, and their solution is for us to disconnect the sync, delete the local files, and reconnect the sync, which means a lot of lost data and productivity each time.
Having some idea of what you are doing to work on it or a timeline when you anticipate having the problem fixed would be helpful. We've been begging for this to be fixed since June of 2017.
Marc Tremmel commented
A restriction of 300.000 files is just ridiculous. As one of the leading companies in terms of modern cloud based Data-Pools Microsoft certainly has to push this topic even more. This is next step for many companies to get rid of old server-structures. ODFB is a great tool for simpliflying processes and push the acceptance for the older generation to work with the cloud.
@MS this is your chance to improve work sustainedly
Unfortunately I read this article after we did a big migration from a file server to SPO.
We got large Performance Issues with ODFB when we synchronized 450.000 Elements from SPO to the client (Files on Demand). The speed of the initial sync was OK but when we worked with these files, we had to wait 20-30 minutes until new / edited Office files were synced to the clients. Not acceptable for the users. In our misery we started to sync all Documents with OFDB on a fileserver again and connect the users via file share to the documents. We had to rebuild all Permissions and so on …
Very bad situation because we see a great potential in this way of syncing, and it is of cause one huge advantage of ODFB / SPO. But now we a really frustrated. Hope that MS is improving ODFB soon!!
Ferhat Baydemir commented
In modern Cloud based Data-Pools is the restriction of 300.000 files to low. Sharepoint Online can handle millions of files. OneDrive is the perfect tool to work in the Cloud with your usual tools like the Windows-Explorer.
Not every user is a Generation Y user with perfect working skill. The big part of the Users are older. They don't want to learn new working forms like in Sharepoint Online --> Browser based.
300000 files only? Are you kidding? I have over 500000 and its taking AGES
SPO and OneDrive are currently only suitable for small amounts of files and data and not a replacement for file servers, even it would make sense to have everything stored in O365.
I see that it is common to move file servers to SharePoint and use On Demand with OneDrive to have access to files, but users are used to have all their data at hand, even they don't use 95% of the data at all (but the feeling they could, makes them happy😊 and so the admins). Moving off data to archives or only synching partially is not an option, no one has time to do that nor does the user have the know-how how to do it right to synch from SharePoint what he needs - too complicated. On top provisioning and permission limitations make it a headache when splitting data to be synched or having multiple sites/libraries to remediate SPO limitations.
I would expect, especially when using OneDrive with "on demand" functionality it should be possible to have more than 500k files and not just hit your clients CPU to 100% for 2 hours to get some updates lined up. By the way, 500k+ are not an uncommon number of files for smaller companies at all.
So please make the OneDrive on demand piece at least smart enough (and fast) so it can handle more than 100k files.
Another request in this area would be to lift the size of “free” SharePoint storage from 1TB + 10GB per licensed users. It’s fine that every user could use 1TB on his personal drive (which no one does, so it’s pure sales arguments), but the company data is limited to 1TB plus 10gb per user. Buying storage is way too expensive with SharePoint, so our customers are not moving to SharePoint and considering other offers (Dropbox, box.com etc.). So, for us, the partners it’s hard to move customers to the cloud if they can’t move a simple file server - still a core piece of infrastructure in 2019. Other approaches like Azure file servers or services for files in Azure are way too expensive. So please start to fix this better sooner than later - OneDrive has evolved, but's still not there where it should be.....
I wonder why this still is an issue. A cloud storage solution that doesn't work on your own operation system. How is that even possible?
For those needing to access large numbers of files from File Explorer, try mapping a network drive to your SharePoint Online document libraries with Zee Drive as it supports libraries with large numbers of files http://www.thinkscape.com/Map-Network-Drives-To-Office-365-OneDrive/
How is this possible? 300,000 file limitation sounds like a lot, until you realize how easy it is for departments to surpass that number. By restricting the number, it puts teams in a very difficult situation who needs to have quick access to these files.
This means, sticking with Network drives is the option.
Daniel Wirjoprawiro commented
This is absolutely critical and is preventing us from migrating more users. Please action this one!
Mohcine Chaouki commented
A huge roadblock for our company to migrate to sharepoint online from our network drives that have well over millions of files for some departments.
There are environments where you need this optimized. I support this
Saša Jovanović commented
Limit of 100.000 files is not ok. I looking around for better solution than One Drive.
Automated Builder commented
Trying to Sync with 481,473 Files, 577 Folders it chugs but eventually finishes... Crashes every so often but once its uploaded *seems to work*
Same experience here. I guess we will have to go back to DropBox enterprise or Gdrive. I was so hopeful for an all in one solution using sharepoint and OneDrive synch for our companies client files archive. Not working. Fix it. 100,000 File count libraries are more and more common.
James Beaty commented
Our Org is migrating 500+ users from Network SAN (Personal Mapped Drive) to OneDrive. We're running into this issue. This is a major problem for us. The client doesn't tell you that it's struggling it just stalls out, no errors. The client has got to be hardened and more informative about problematic conditions. If it's going to choke on 100K files then it should tell you or be re-engineered to handle this condition. Unacceptable.