Sizing
Recommendations
- Utilize the official Veeam Backup for Microsoft 365 calculator
- Use Object Storage
- Adhere to the recommended proxy size (8C/32GB)
- Avoid using SMB based repositories
Veeam Backup for Microsoft 365 calculator
Utilize the official Veeam Backup for Microsoft 365 calculator available at https://calculator.veeam.com/vb365.
The sizer applies the principles outlined in this best practice guide to calculate storage and compute sizing
Object-based Sizing
Sizing the Veeam Backup for Microsoft 365 compute infrastructure is determined by the number of objects that need to be processed in the backup. The following list outlines what is considered an object for Veeam Backup for Microsoft 365:
For Exchange Online and On-Premises
- Primary Mailbox
- Archive Mailbox
- Shared Mailboxes
- Public MailFolders
- Exchange Resources (Room, Equipment)
For SharePoint Online and On-Premises
- Sites (Collaboration, Communication, Publishing, Enterprise, Template based) including subsites
- Personal Sites
- Teams Sites
For OneDrive for Business Online and On-Premises
- OneDrive accounts
For Teams
- Teams
Example
Use case: Organization with 500 may require protection for all mailboxes (both Primary and Archive), 200 Shared Mailboxes, 10 Public MailFolders, all Personal Sites and OneDrives along with 1000 SharePoint sites and 100 Teams. The total number of objects amounts is 3,410 as indicated in the table below:
| Value | Type |
|---|---|
| 500 | Primary Mailboxes |
| 500 | Archive Mailboxes |
| 200 | Shared Mailboxes |
| 10 | Public MailFolders |
| 500 | Personal Sites |
| 500 | OneDrive for Business |
| 1000 | SharePoint Sites |
| 100 | Teams (Count as 2 objects, because of complexity) |
The example can be backed up by a single All-in-one Veeam Backup for Microsoft 365 server, consolidating all roles on a server with the recommended configuration maximums of 8 Cores and 32GB RAM.
Teams Data
Microsoft Teams as a service itself holds relatively low amounts of data. Most of the data is distributed on other Microsoft 365 services such as Exchange, SharePoint, and OneDrive for Business. Therefore, when calculating the required backup space for Teams, please refer to the respective sections for disk repositories or object storage repositories.
To save repository space and processing time, backup your Teams to the same repository as the Teams SharePoint sites.
The files stored within Microsoft Teams are stored in the respective Teams SharePoint site in subfolders based on the channel names (like General). When you run a Teams backup job only these subfolders with a link to the Team will be backed up. Running a SharePoint job on the site will back up all the data within SharePoint, including these Teams-related folders. Since the object-IDs are the same from the Teams or the SharePoint job, backing them up to the same repository will “deduplicate” them and generate the mentioned savings.