OneDrive for Business (Plan 2) Limits
I'm part of a workplace that currently uses Google Workspace for Enterprise but we're looking to switch to Microsoft OneDrive right now and I have a few questions. First of all I want to say that the only thing we care about is cloud storage. We work in video and therefore need the unlimited storage that OneDrive for Business (Plan 2) is supposed to give. We don't need any of the Office365 stuff and other apps and services that can be added on. https://www.microsoft.com/en-in/microsoft-365/onedrive/compare-onedrive-plans?activetab=tab:primaryr2 tells me that Plan 2 for Business gives us unlimited storage for $10/user/month. Of course the conditions say: > Unlimited individual cloud storage for qualifying plans for subscriptions of five or more users, otherwise 1 TB/user. Microsoft will initially provide 1 TB/user of OneDrive for Business storage, which admins can increase to 5 TB/user. Request additional storage by contacting Microsoft support. Storage up to 25 TB/user is provisioned in OneDrive for Business. Beyond 25 TB, storage is provisioned as 25 TB SharePoint team sites to individual users. I intend to add 5-10 users to the organization so I definitely qualify. So, let's say I first increase the limit to 5TB/user to get 25TB total, do I need to wait till I hit 25TB to ask for more? When the conditions say "Beyond 25 TB, storage is provisioned as 25 TB SharePoint team sites to individual users", I have to ask Microsoft for it. I'm wondering what kind of process this is. Do I have to explain exactly what I'm using it for. Is it a lengthy process, or is it just a simple email and they give me a new Sharepoint. Now about SharePoints, I'm not sure how they work, but from what I understand they're limited to 25TB/sharepoint. But when they say it is "provisioned as 25 TB SharePoint team sites to individual users", can multiple sharepoints be provisioned to the same user. $10/user would be $100/month for 10 users. So essentially I could add 250TB in SharePoints. But can I add more SharePoints on top of that to the same users, cus we're way over that on Google already. Or would I have to add more users for each new SharePoint. Next, does it make any difference if I get SharePoint Plan 2 instead of ODfB Plan 2. Also, https://docs.microsoft.com/en-us/office365/servicedescriptions/sharepoint-online-service-description/sharepoint-online-limits says that the total storage per organization is 1TB plus 10gb/license. What is this talking about and is it related to ODfB. Lastly, how hard would it be for me to move my stored files from Google Drive to OneDrive. Right now, it's sitting at over 500TB. Would we have to hire some other service or is there something we can use provided my Microsoft for this kind of process.OneDrive Client, Files on Demand and Syncing large libraries
I thought I'd post some observations regarding the OneDrive sync client we've observed that aren't documented anywhere but we needed to figure out when planning a massive move to SharePoint from on-premise file servers: Limits: Microsoft documents that you shouldn't sync more than 300,000 files across all libraries that the client is connected to, but there was no documentation about Files on Demand limits, and we have observed the following: The OneDrive client will fail when the dat file that stores object metadata reaches exactly 2GB in size (%localappdata%\Microsoft\OneDrive\settings\Business1). Now, while Microsoft says you shouldn't sync more than 300,000 files, you can connect using files on demand to libraries that contain more than this. The trick here is that in this case, the total number of files and folders matter, lets call them collectively "objects". (Interestingly, when you first connect to a library and the client says "Process changes" and gives you a count, "changes" is the total number of objects in the library that it's bringing down using files on demand and storing in the dat file.) My suspicion is that since the OneDrive client is still 32bit, it's still subject to certain 32bit process restrictions, but I don't really know. What matters in this case is that up until build 19.033.0218.0009 (19.033.0218.0006 insiders build), the client would fill up the dat file and reach the 2GB limit after about 700-800,000 objects. After build 19.033.0218.0009, it appears that the client has been optimized and no longer needs to store quite as much metadata about each object, "increasing" the upper limit of files on demand. (It seems that in general, each object takes up just over 1KB of data in the dat file, putting the limit somewhere just under 2 million objects). Keep in mind, this is not per library, this is across all libraries, including OneDrive for Business (personal storage), SharePoint Document Libraries, etc. Performance: The client has made some significant improvements in performance quickly as they refine each new build, but there are some things to be aware of before you start connecting clients to large libraries: It. takes. forever. The more objects in a library, the longer it's going to take for the client to build it's local cache of files on demand copies of all the items in the library. It seems that in general, the client can process about 50 objects per second, if you were connecting to a library or multiple libraries that had 1.4 million objects, it will take around 8 hours before the client is "caught up". During the time that the content is being built out locally, Windows processes will also consume a large quantity of system resources. Specifically, explorer.exe and the Search Indexer will consume a lot of CPU and disk as they process the data that the client is building out. The more resources you have, the better this experience will be. On a moderately powered brand new Latitude with an i5, 8GB of Memory and an SSD OS Drive, the machine's CPU was pretty heavily taxed (over 80% CPU) for over 8 hours connecting to libraries with around 1.5 million objects. On a much more powerful PC with an i7 and 16GB of memory, the strain was closer to 30% CPU, which wouldn't cripple an end user while they wait for the client and Windows to finish processing data. But, most organizations don't deploy $2000 computers to everyone, so be mindful when planning your Team-Site automount policies. Restarts can be painful. when the OS boots back up OneDrive has to figure out what changed in the libraries in the cloud and compare that to it's local cache. I've seen this process take anywhere from 15 minutes to over an hour after restarts, depending on how many objects are in the cache. Also, if you're connected to a large number of objects in the local cache, you can expect OneDrive to routinely use about a third of CPU on an i5 processor trying to keep itself up to date. This doesn't appear to interfere with the overall performance of the client, but it's an expensive process. Hopefully over time this will continue to improve, especially as more organizations like mine move massive amounts of data up into SharePoint and retire on premise file servers. If I had to make a design suggestion or two: - If SharePoint could pre-build a generic metadata file that a client could download on first connection, it would significantly reduce the time it takes to set up a client initially. - Roll the Activity Log into an API that would allow the client to poll for changes since the last restart (this could also significantly improve the performance of migration products, as they wouldn't have to scan every object in a library when performing delta syncs, and would reduce the load on Microsoft's API endpoints when organizations perform mass migrations) - Windows to the best of my knowledge doesn't have a mechanism to track changes on disk, i.e. "what recursively changed in this directory tree in the last x timeframe", if it were possible to do this, Windows and SharePoint could eliminate most of the overhead that the OneDrive client has to shoulder on it's own to keep itself up to date. Speaking to OneDrive engineers at Ignite last year, support for larger libraries is high on their radar, and it's apparent in this latest production release that they are keeping their word on prioritizing iterative improvements for large libraries. If you haven't yet started mass data migrations into SharePoint, I can't stress enough the importance of deeply analyzing your data and understanding what people need access to and structuring your libraries and permissions accordingly. We used PowerBI to analyze our file server content and it was an invaluable tool in our planning. Happy to chat with anyone struggling with similar issues and share what we did to resolve them. Happy SharePointing! P.S., shoutout to the OneDrive Product Team, you guys are doing great, love what you've done with the OneDrive client, but for IT Pros struggling with competing product limits and business requirements, documenting behind the scenes technical data and sharing more of the roadmap would be incredibly valuable in helping our companies adopt or plan to adopt OneDrive and SharePoint.Default version limit
Hi, I don't find any information about the default limit for file versioning in OneDrive for Business linked to my E3 licenses. Is this a limit of amount of version, of time? I don't find clear documentation neither settings on the admin center to check this. Many thanks for your help
Default Versioning Settings - Number of Versions to retain
It appears that the default versioning settings for OneDrive are for 500 major versions. Is there a way to reduce this default globally? It doesn't appear so via the GUI but was wondering if perhaps there was a way to set this via powershell?
OneDrive for Business and Citrix
I was wondering if there was anyone out there that has any experience using OneDrive and Citrix. Let me give you a bit of background. We have been mandated to move all of users personal netwrok drive over to OneDrive but we have encountered an issue a number of our Citrix applications. These are some lagacy applications that must write various data to a UNC path (in this case the users personal network drives). Now we do not want to use the OneDrive Sync Client as we are worried that we will quickly run out of space on our Citrix servers. We had hoped that the new OneDrive on demand functionality might help with this, but it sounds like it will only be available on Win 10, and all of our Citrix Servers are running Server 2016. I know that there are a several third part tools that would help us solve the issue, but again we want to avoid the additional cost if we don't have too.
