- Use Object Storage
- Use recommended proxy size (8C/32GB)
Check out the official Veeam VBO Sizer at https://calculator.veeam.com/vbo/
Sizing the VBO compute infrastructure is based on the amount of objects which need to be processed in the backup. The following list shows what counts as an object for Veeam Backup for Office 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
Use case: Organization with 500 users might need to protect all mailboxes (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 to 3,410 objects as per table below:
|500||OneDrive for Business|
|100||Teams (Count as 2 objects, because of complexity)|
The example can be backed up by a single repository based on the recommended configuration maximums.
When sizing the backup jobs the best practise includes the following:
- Create separate jobs based on the application type (eg. separate jobs for Exchange, SharePoint and OneDrive). This also allows to direct the jobs to different repositories with separate retention. Different types of data don’t grow equally.
- Do not exceed the 4,000 users per job.
- For large environments it is advised to increase the retry fail in the job configuration at least to 20 minutes or more.
- Run the backup jobs outside the work hours reducing impact on Microsoft Office 365 throttling when other clients (OneDrive, ActiveSync etc..) are operating.
Microsoft Teams as a service itself does only hold relatively low amounts of data. Most of the data is distributed on other Microsoft 365 services like Exchange, SharePoint and OneDrive for Business.
Thus for calculating your required backup space for Teams please refer to the respective sections for disk repos 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 side 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. When running a SharePoint job on the site it will backup all the data within the SharePoint, including these Teams related folders. As the object-IDs are the same from the Teams or the SharePoint job backing these up to the same repository will “deduplicate” them and thus generate the mentioned savings.