One/some of their engineers created and maintain this I believe. But still only unique blocks are ever going to be sent to capacity tier.įor space figuring, you could try using this Eventually there are less similar blocks as the months and years go by so it may grow larger down the road. So your bucket is only going to grow similar to the size of your incremental backup sizes for a while. It is not dedupe but a way of preventing duplication in the first place.

It works similar to the refs/xfs block cloning feature in those file systems. 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.Ĭopyright © 2019-2023 Solutions Architects, Veeam Software.Object storage in veeam is offloaded in incremental forever manner. When running a SharePoint job on the site it will backup all the data within the SharePoint, including these Teams related folders. When you run a Teams backup job only these subfolders with a link to the Team will be backed up. The files stored within Microsoft Teams are stored in the respective Teams SharePoint site in subfolders based on the channel names (like General). To save repository space and processing time backup your Teams to the same repository as the Teams SharePoint sites. Thus for calculating your required backup space for Teams please refer to the respective sections for disk repos or object storage repositories. Most of the data is distributed on other Microsoft 365 services like Exchange, SharePoint and OneDrive for Business. Microsoft Teams as a service itself does only hold relatively low amounts of data. The example can be backed up by a single All-in-one Veeam Backup for Microsoft 365 server running all roles together on a server based on the recommended configuration maximums of 8 Cores and 32GB RAM. Teams (Count as 2 objects, because of complexity) The total number of objects amounts to 3,410 objects as per table below: 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.

Sites (Collaboration, Communication, Publishing, Enterprise, Template based) including subsitesįor OneDrive for Business Online and On-Premises.

The following list shows what counts as an object for Veeam Backup for Microsoft 365: Sizing the VB365 compute infrastructure is based on the amount of objects which need to be processed in the backup. The sizer uses the principles of this best practice guide to calculate storage and compute sizing. Make use of the official Veeam Backup for Microsoft 365 calculator at. Veeam Backup for Microsoft 365 calculator Use the official Veeam Backup for Microsoft 365 calculator.

Calculator veeam