Configuration Maximums

This section outlines the supported Veeam Backup for Microsoft 365 configuration maximums. While the actual numbers may vary depending on deployment types and available resources, the provided values represent the currently supported limits, considering acceptable performance. These values apply to any combination of Online and On-Premises environments utilizing Microsoft Exchange, Microsoft SharePoint, OneDrive for Business and Microsoft Teams.

The tables in this section use the number of objects and their variations as a metric for estimations.

Object types and variations:

• Mail (Primary, Archive, Shared, PublicFolder)
• Sites (SharePoint incl. Subsites, Personal, Teams)
• OneDrive for Business
• Teams

SharePoint

A special note is necessary regarding the object count for SharePoint Sites. Given the wide range of functionalities SharePoint offers, implementations in the field vary from simple ‘hello world’ websites with a few megabytes of data to complex document management systems hosting terabytes of data. While we count one SharePoint site as an object for sizing the Veeam Backup for Microsoft 365 infrastructure, this doesn’t always accurately represent the impact on the backup infrastructure. For instance, a SharePoint site with 250,000 documents within a document library takes more compute resources to process than a simple 50 MB intranet site.

First and foremost, we recommend adhering to the limits specified by Microsoft for SharePoint, paying special attention to the guideline that suggests, “For optimum performance, we recommend storing no more than 300,000 files in a single OneDrive or team site library.” Additionally, we advise counting every 5GB of SharePoint data as one object for your sizing to accurately reflect the impact of larger SharePoint sites on Veeam Backup for Microsoft 365 “VB365” infrastructure.

The Recommended Maximums

These maximums are derived from Veeam QA testing and help to ensure the best performance for v8 installations builds 8.0.2.159-8.1.0.3503.

With the availability of Proxy Pools, some limits like Objects per Job have been removed from the list, since the load is distributed across a Pool. Nevertheless, as a best practice you should consider not to have more than 5000 - 10.000 objects in a Job. The reason is found in management tasks like job restarts or analysis in case of any issues.

The maximums per component (proxy, repository, installation, organization) must be maintained simultaneously such as the number per objects and number per users.

Refer to the official system requirements Helpcenter - System Requirements

Resources

---