These maximums are based on Veeam QA testing and the recommended maximums for the specified config.The two primary methods of measuring the criticality of IT systems are how much data and time you can afford to lose, commonly referred to as RPO and RTO. In addition we recommend to count every 5GB of SharePoint data as one Object for your sizing to reflect the impact of bigger SharePoint sites for the VB365 infrastructure. A SharePoint site with 250.000 documents within a document library takes more compute resources to process than a simple 50mb intranet site.įirst of all we recommend you to respect the limits Microsoft is specifying for Microsoft Sharepoint and take special account to the “For optimum performance, we recommend storing no more than 300,000 files in a single OneDrive or team site library.” guideline. As we count one SharePoint site as an object for the sizing of the Veeam Backup for Microsoft 365 infrastructure this doesn’t always represents the impact on the backup infrastructure. As SharePoint offers a wide range of functionalities the implementations within the field are from a simple “hello world” website with a few MB of data to complex document management systems hosting TB’s of data. Subsites, Personal, Teams)Ī special remark is required on the object count for SharePoint Sites. Mail (Primary, Archive, Shared, PublicFolder).The tables in this section use the number of objects and their variations as a metric for estimations.
The values provided refer to any combination of Online and On-Premises environments that use Microsoft Exchange, Microsoft SharePoint, OneDrive for Business and Microsoft Teams. These values represent what’s currently supported also in light of acceptable performance. Numbers might vary depending on deployments types and available resources. This section covers the supported VB365 configuration maximums.
0 kommentar(er)
