Run the backup jobs outside the work hours reducing impact on Microsoft Office 365 throttling when other clients (OneDrive, ActiveSync etc.) are operating.For large environments it is advised to increase the retry fail in the job configuration at least to 20 minutes or more.Different types of data don’t grow equally. This also allows to direct the jobs to different repositories with separate retention. separate jobs for Exchange, SharePoint and OneDrive). Create separate jobs based on the application type (eg.When sizing the backup jobs the best practise includes the following: The example can be backed up by a single repository based on the recommended configuration maximums. 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 Office 365: Sizing the VBO compute infrastructure is based on the amount of objects which need to be processed in the backup. Check out the official Veeam VBO Sizer at Object-based Sizing
0 kommentar(er)
