[Request]
The Best Practice sizing page provides information on memory, CPU design, Microsoft 365 throttling, and more.
In addition, could you please include more detailed information, such as concrete configuration examples and the expected or measured results?
[Background]
I conducted a performance evaluation.
I was unable to determine whether the observed performance was sufficient.
Providing concrete performance data for environments built based on the configurations described in the Best Practice would allow me to determine whether the performance observed in my environment is sufficient.
[Example]
Using an environment designed based on the information described in the Best Practice, I would like to see the following details:
- Configuration diagram
- Number of each component(Server, Prxoy, Repository, etc.)
- Memory and CPU specifications for each machine
- Microsoft 365 environment details(number of users, total backup data volume)
- Results
- Throughput
- Processing time
- Overall processing time
- Processing time per wokflow(Outlook, OneDrive, SharePoint, Teams)
Thanks,
-
Tatsuya
- Novice
- Posts: 7
- Liked: 1 time
- Joined: Dec 05, 2025 3:20 pm
- Full Name: Tatsuya Yamada
- Contact:
-
Polina
- Veeam Software
- Posts: 3890
- Liked: 976 times
- Joined: Oct 21, 2011 11:22 am
- Full Name: Polina Vasileva
- Contact:
Re: Request to Add Performance Results to Best Practice
Hi Tatsuya,
We cannot provide such benchmarks from our test environments, and even if we could it wouldn't help you much. We provide best practice on infrastructure components placement and configuration, but processing times also depend on the tenant size and its throttling qouta, complexity of the structure of your data (i.e. hierarchy within your protected SharePoint, mailboxes folders hierarchy, number of file versions to protect, etc).
Overall, your environment is sufficient if your backups fit your allowed backup windows and you meet your business SLAs for backup.
Thanks
We cannot provide such benchmarks from our test environments, and even if we could it wouldn't help you much. We provide best practice on infrastructure components placement and configuration, but processing times also depend on the tenant size and its throttling qouta, complexity of the structure of your data (i.e. hierarchy within your protected SharePoint, mailboxes folders hierarchy, number of file versions to protect, etc).
Overall, your environment is sufficient if your backups fit your allowed backup windows and you meet your business SLAs for backup.
Thanks
-
Tatsuya
- Novice
- Posts: 7
- Liked: 1 time
- Joined: Dec 05, 2025 3:20 pm
- Full Name: Tatsuya Yamada
- Contact:
Re: Request to Add Performance Results to Best Practice
Hi Polina-san,
While I understand that meeting the business SLA requirements is a key evaluation point, the current output from the calculation system does not appear to provide sufficient information to determine whether the SLA can realistically be met.
To support this assessment, Veeam provides a calculation system.
We entered our expected number of users and total data volume and obtained the following estimation results:
Repository: 73,064.3 TB
Proxy: 44
However, based on these results alone, it is difficult to evaluate whether the proposed configuration would meet our SLA targets.
I have a few questions regarding these results:
- Does this calculation take throttling into account?
- Does the number of proxies refer to the number of Proxy Pools?
- How should the proxies be distributed?
(For example, there is no guidance on how many proxies should be allocated specifically for SharePoint, etc.)
To better assess SLA feasibility, could you provide more detailed and practical information in the Calculate output?
Best Regards,
While I understand that meeting the business SLA requirements is a key evaluation point, the current output from the calculation system does not appear to provide sufficient information to determine whether the SLA can realistically be met.
To support this assessment, Veeam provides a calculation system.
We entered our expected number of users and total data volume and obtained the following estimation results:
Repository: 73,064.3 TB
Proxy: 44
However, based on these results alone, it is difficult to evaluate whether the proposed configuration would meet our SLA targets.
I have a few questions regarding these results:
- Does this calculation take throttling into account?
- Does the number of proxies refer to the number of Proxy Pools?
- How should the proxies be distributed?
(For example, there is no guidance on how many proxies should be allocated specifically for SharePoint, etc.)
To better assess SLA feasibility, could you provide more detailed and practical information in the Calculate output?
Best Regards,
Who is online
Users browsing this forum: Google [Bot] and 9 guests