Nobody anticipated how quickly Microsoft 365 may expand or how our everyday conversation and work life would change when the first Veeam Backup for the platform was released in 2016. The Microsoft 365 system now includes different features and programs. Players, for instance, had just started to be a fixed part of Microsoft 365.
There were still a number of obstacles at that time. In business environments, there were not as many customers with larger user numbers and item storage was not yet state-of-the-art. We quickly learned that we had developed a effective, highly possible product that had been enhanced over time. Veeam Backup for Microsoft 365 v7 has been released safely in the interim. The best techniques have already changed as a result of the product’s ongoing advancements and improvements. Our standard best-practice guide, Best Practice Guide, contains all present best practices. In this article, we’d like to provide a better perspective on the best practice’s history and an in-depth understanding for effective and straightforward infrastructure planning.

Basics

Veeam Backup for Microsoft 365‘s simplicity and maximum agility are its strongest features. However, because there is not” the one” perfect method, these benefits also make extra planning challenging. Veeam may give you the ability to seamlessly integrate with your network and strategy whether you use cloud-only, on-premises, or a combination of the two. Parts: You need to look more closely at your conditions for effective best practices and size. To reach further conclusions, you need the following information: the number of objects that need to be backed up per service( Mail, SharePoint / Sites, OneDrive, Teams ). For a better understanding, the following Veeam Backup for Microsoft 365 recommendations serve as the cornerstone for an accurate sizing: Current numbers: Data volume for each service to be backed up( Mail, SharePoint, OneDrive, Teams ) – Retention period of your backup data.

An image is equivalent to one user’s service. Mail, Archive, OneDrive, individual websites, SharePoint sites, Teams Objects, etc. are examples of services. You would use four objects, for instance, if a person backups all services. To create a suitable backup conditions, it is necessary to comprehend our storage solutions and tactic. For more details, visit RAM allocation and number of repository databases per proxy.

the supervisor’s client

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.the supervisor’s client is automatically installed together with the first proxy server during the initial installation. These services can be run together, as the management server requires only a few resources (RAM, CPU). Separation of the components is recommended in large environments (>10,000 users).The proxy: The proxy server is the main component that downloads all data from Microsoft and processes the backup data and stores it on a repository.To optimize requests towards Microsoft, they can be split in parallel and in so called “threads.” A thread describes an “action” like requesting objects, files and attributes like title and content of an email, file history, etc.Any kind of information we need in case of a disaster to be able to restore elements successfully and completely.The number of threads is between 1-256, but a too high number of threads is often the cause for a very high RAM and CPU usage and increases the risk that the throttling rule of Microsoft limits the requests and data processing rate strongly.Of course, the available bandwidth on the customers side also plays a major role, but there are limitations on Microsoft’s side as well.What use are 10 proxy servers when they are each restricted by an inadequate Internet connection?For example, if you are connected to a high-performance Internet line, it does not mean that your backup will be downloaded quickly. Usually we see the limitation in the bandwidth provided by Microsoft (source-side).One of the biggest challenges is the dependency on Microsoft. Factors beyond our control may negatively affect the performance of our backup, yet they are still essential for a successful one:-The bandwidth (For more information see: Microsoft 365 network connectivity principles)-The throttling:How to temporarily turn of Microsoft M365 throttling
Veeam Best Practice Guide – ThrottlingIn addition, depending on the current load in the Microsoft 365 data center or access point, faster or slower access is granted. This cannot be influenced or increased.Therefore, set the backup times preferably outside the normal working hours. At this time, the access points usually have a lower load and you will see a higher backup speed.

The collection

The collection can be a local disk repository or an object storage. For a high-performance backup and better scalability for future needs, we recommend object storage.If you are using object storage, the responsible proxy hosts an on-premises “cache” for metadata.The collection cache in Veeam Backup for Microsoft 365 helps to speed up the backup and restore process and reduce costs by caching the metadata locally before transferring it to the cloud repository. This helps to reduce bandwidth usage and improve the reliability of backups by reducing the risk of connection issues.The collection cache requires ~ 1% of the over-all backup size as free disk space.Veeam Disk Repository – Best PracticesVeeam Object Storage Repository – Best PracticesIf you a looking for a good estimation for your future requirements and costs you can use the Veeam Capacity Calculator.

Large-scale environment marketing

When creating jobs, you can take some optimizations into account for large environments (& gt, 2000 users ). On a proxy server, combine storage work with the same expertise( see examples below ). For each system, establish separate repositories or subfolders, and support each one separately in the backup infrastructure. Increased freedom in work configuration is crucial for enterprise environments in order to guarantee future usability. It is best to divide the products into separate repositories and proxies from the beginning. Consider building more libraries per service than are immediately required if you are currently migrating your conditions or have plans for future growth. On devoted proxy, you can divide up the work from scratch and divide them in the future. You can split the corresponding back data from the back APIs on Microsoft’s part by using this pre-sorting at the start of your configuration. To better understand, Veeam addresses the backup / graph APIs concurrently, allowing jobs to run simultaneously without causing throttling. The back jobs’ dependence on one another in the event of a content structure error is another benefit of parallelization. For instance, a back occupation that backups all services is handled step-by-step. The whole fallback job is impacted, though, if a SharePoint share contains an infected file. Due to the support network style of Teams, you can combine SharePoint and Teams jobs on one store to avoid consuming superfluous storage space. Players save almost 80 % of their information on SharePoint by creating a SharePoint section for each channel. Data will be backed up and stored doubly if SharePoint and Teams are divided into separate archives and jobs. In the instance that follows, there are three proxies that each use their own store and are only in charge of a specific set of services.

The stand-in position

In the backup job wizard, you can define all of these dependencies( Backup Job – & gt, Service / pkg, Proxy vs. Repo ). Working with back types based on Dynamic Azure Active Directory groups is advised to prevent users from being unintentionally forgotten in larger environment. ( Job Design with Azure Active Directory Groups ) We must take into account more than just user objects when backing up SharePoint and Teams. We must work with corresponding items for both Teams and SharePoint pages. To make this process easier in business environments, you can also use a book: SharePoint and Teams JobManagerFor, which predefines all settings in an orderly fashion and provides an overview and evidence:

Conclusion

Veeam Backup for Microsoft 365 offers a practical and dependable way to backup your computer’s culture. Understanding the components of the storage environment, the best techniques, and the design of backup jobs is essential to using this method successfully. Businesses can guarantee the performance, dependability, and protection of their backups by adhering to best practices and sizing tips. Organizations can optimize the performance of their files and ensure that their culture is operating efficiently by adhering to the best techniques in this article. Please feel free to get in touch with us or our Veeam Partners to help you plan your storage conditions. Follow the best practices video for more details and best practice information. Do you need to choose the store you’ll used? Study the Microsoft 365 Backups Storage Choice Guide. Access Veeam Backup for Microsoft 365 for a 30-day FREE trial.