(click to expand table of contents)

• Scaling for Speed – Auxiliary Backup Applications
  • Day ‘X’ - Scaling the environment
  • Tenant Scaling
  • Multi-Tenant Deployment Limits

Scaling for Speed – Auxiliary Backup Applications

VBO v4 included a technique to improve the speed by which SharePoint and OneDrive data can be extracted from Office 365. This is achieved by launching multiple ‘auxiliary backup applications’. The creation, registration, and permission assignments of these Azure AD Apps is accomplished through the VBO Console. Documentation for creating and editing these accounts can be found here: https://helpcenter.veeam.com/docs/vbo365/guide/adding_backup_accounts.html?ver=40.

Day ‘X’ - Scaling the environment

This section provides details for scaling this implementation beyond the day 1 deployment.

The table below displays all of the VCSP components required to deliver a self-service capable & multi-tenant solution to approximately 60,000 O365 users. Using this design, there are no limitations on the number of tenant organizations, the data capacity or duration of retention required. As each Proxy approaches its capacity, a new one should be deployed, eventually expanding to 10 Backup for Office 365 Proxies.

Tenant Scaling

As previously explained, Tenants can perform self-service actions on their own O365 Organizations using a combination of Veeam Explorers and VBR to securely connect to the VBO service, instigate recovery operations back to O365, and retrieve/export data locally as required.

Each Tenant connects to the VCSP Cloud Connect system securely using their own credentials.

Multi-Tenant Deployment Limits

As you can see from the table above, the current release of VBO v4 supports a maximum of 10 Proxy Servers. The Day 1 deployment defined the starting point as a single Proxy with 4 CPUs and 8 GB of RAM. This is sufficient to support 750 users or approximately 1943 objects, given the assumptions at the beginning of this document.

Assuming that Tenants are likely to grow over time, both by the number of users and by the volume of data they are storing, reasonable headroom should be left within each Proxy to support such growth. Our recommendation is to add additional VBO Proxies when your existing platform begins to reach capacity. For example, if the VBO Proxies regularly run at >= 90% CPU or Memory during backup runs, add an additional proxy. The supported maximum number of Backup for Office 365 proxies is 10. At this point, a second VBO/VCC deployment is needed to provide backup services to additional users. The stated maximums can be found here: https://bp.veeam.com/vb365/guide/design/maxconfig.html

Leveraging Object Storage from Day 1 will circumvent reaching any storage capacity limits related to the Tenant growth.