veeam exchange 2016 backup best practices

The management server is automatically installed together with the first proxy server during the initial installation. The actual server is a pure administrative component and is used for connecting an organization in Microsoft 365, creating backup jobs and managing the infrastructure. To build a suitable backup environment, it is necessary to understand our backup technology and strategy. RAM allocation and number of repository databases per proxy A service is Mail, Archive, OneDrive, personal site, a SharePoint site or a Teams Objects, etc.įor example, if a user backs up all services, you are using four objects. – Repository type for your backup data (Disk-Repository or Object Storage Repository - see section “The repository”)įor better understanding, these are the following recommendations within Veeam Backup for Microsoft 365 that serve as a basis for a successful sizing:Īn object is equal to one service of one user. – Data volume for each service to be backed up (Mail, SharePoint, OneDrive, Teams) – Number of objects to be backed up per service (Mail, SharePoint/Sites, OneDrive, Teams). You need the following data to draw further conclusions: Whether cloud-only, on-premises or a mix of both, Veeam will give you the ability to integrate perfectly with your infrastructure and strategy.įor successful best practices and sizing, you need to take a closer look at your environment. However, these advantages also make further planning difficult because there is not “the one” perfect solution. The strength of Veeam Backup for Microsoft 365 is its simplicity combined with our maximum flexibility. In this article we would like to deliver a better point of view about the background of the best practices and provide a comprehensive understanding for successful and simple infrastructure planning.

You can find all current best practices in our official best-practice-guide: Best Practice Guide Due to constant improvements and innovations in the product, the best practices have also changed. In the meantime, Veeam Backup for Microsoft 365 v7 has been successfully released. We soon found out that we had created a successful product with a lot of potential, which was improved from version to version. Object storage was not yet state of the art and there were not that many customers with larger user numbers in enterprise environments. For example, Teams was just becoming a fixed component of Microsoft 365.Īt that time, there were still various challenges. New features and software were added to the Microsoft 365 package. When the first version of Veeam Backup for Microsoft 365 was released in 2016, no one realized how fast Microsoft 365 would grow and how our daily communication and work life would change.

Veeam exchange 2016 backup best practices