mousepopla.blogg.se - Veeam backup for office 365 user guide

VEEAM BACKUP FOR OFFICE 365 USER GUIDE SOFTWARE

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.

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. If you have an extra VM available on your Server OS, that's the perfect place to run it.Check out the official Veeam VBO Sizer at Object-based Sizing So you don't need a server, it can be fully installed on a workstation and the backup store locally or on a shared resource? Why would the documentation not say that? The cost difference is quite big!īut do you really want to trust something as important as your backups to a Desktop machine? Also, most places don't have proper licensing for a VM of a Desktop OS, making that option pretty much impossible. Nightly backups of changes has been adding about 2GB each time. Our Repository, once everything was brought down from O365, takes up 770 GB. We use 142 Veeam licenses (one for each O365 licensed user) and are currently just backing up Exchange Online mailboxes (we won't need any more licenses to add OneDrive and SharePoint backup in the future). Accessing the files through the Explorer is very easy. Now that everything is backed up, the nightly incremental backups take about a half hour. We use 142 Veeam licenses (one for each O365 licensed user) and are currently just backing up Exchange Online mailboxes (we won't need any more licenses to add OneDrive and Microsoft SharePoint Server 2016 backup in the future). Veeam Support helped us tweak the proxy.xml file to reduce the number of connections made to O365 which allowed us to complete the initial download. The biggest trouble we had was with Microsoft throttling our initial backup of our Public Folders. We did have to bump the disk space up a few times though. While that may be a better setup (for efficiency or security?), I found it was not required and have everything on one machine for testing. I too was thinking that we needed two separate machines, one for the Server and one for the Repository. When reading the user guide, I got the feeling that there are several ways to set it up so the details are vague.

VEEAM BACKUP FOR OFFICE 365 USER GUIDE SOFTWARE

In our case, it is a stand alone software that we installed on a Windows 7 VM - both the server and the repository. We are currently testing this for our Office 365 backups.