Optimizing Backup Performance

[Tatsuya]

I am evaluating the performance of the initial (full) backup with the following configuration.
However, the backup still takes a long time.
[Questions]
Q1: Even with a Backup Application configured, will the performance be at the level expected in the "Test Results"?

Q2: My OneDrive Proxy Pool consists of 5 Proxy servers.
However, based on Amazon CloudWatch metrics, it shows that only 2~3 proxies are actively being utilized.
How can I ensure that all(5) proxies configured in the Proxy Pool are effectively used?

Q3: I am considering deploying VB365 for an environment with approximately 15,000 employees.
I do not yet have the exact data volume and the expected daily data growth rate.
However, the current performance in my test environment, the initial backup will take a very long time.
Besides configuring additional Backup Applications or improving Proxy Pool utilization, are there any other methods to significantly increase the backup speed?

[Configuration]
- VB365 version: 8.2.0.2008 P20251007
- EC2 Instance Type for VB365 Server/Proxy: c5.2xlarge(vCPUs:8, Memory:16GiB)
- VB365 Server/Proxy OS: Windows Server 2022
- Repository: Amazon S3
- Proxy Pools:
- Dedicated for Exchange Proxy Pool: 2 proxies
- Dedicated for OneDrive Proxy Pool: 5 proxies
- Dedicated for SharePoint Proxy Pools: 2 proxies
- M365 User Count: 25 Users
- Data Size:
- Exchange: 1.8GB
- OneDrive: 1TB
- SharePoint: 1.1TB
- Number of Backup Jobs (run in parallel):
- Exchange Job: 1
- OneDrive Job: 10
- SharePoint Job: 1
Number of Backup Application: 1
# Note: I am currently evaluating only the initial full backup.

[Architecture Overview]
+------------------+ +-----------------+ +-------------------+
AWS S3(Buckets) |Exchange Repo| |OneDrive Repo| |SharePoint Repo|
+------------------+ +-----------------+ +-------------------+
| | |
+-----------------+ +------+ +------+ +------+
AWS EC2 | VB365 Server | |Proxy| ×2 |Proxy| ×5 |Proxy| ×2
+-----------------+ +------+ +------+ +------+
| | | |
+----------------------+ | | |
|Exchange Job ×1 | +------------------------+ +-----------------------+ +-------------------------+
(VB365) |OneDrive Job ×10 | |Exchange ProxyPool| |OneDrive ProxyPool| |SharePoint ProxyPool|
|SharePoint Job ×1| +------------------------+ +-----------------------+ +-------------------------+
+----------------------+
↓Read ↑Write
==================================================================================
+--------------------------------------------------+
| Organization |
| +--------------------------------------------+ |
| | Backup Application | |
| +--------------------------------------------+ |
| |
| User-1 ... User-25 |
M365 | +------------+ +------------+ |
| |Exchange| |Exchange| |
| +------------+ +------------+ |
| +-----------+ +-----------+ |
| |OneDrive| |OneDrive| |
| +-----------+ +-----------+ |
| +--------------+ +-------------+ |
| |SharePoint | |SharePoint| |
| +--------------+ +-------------+ |
+--------------------------------------------------+

[Test Results]
Bottleneck Job Processing Read Write Duration Objects Transferred
Source Outlook 10.9MB/s 13.4MB/s 35.8MB/s 2:46 62 1.8GB
Source OneDrive-1 7.0MB/s 24.4MB/s 53.2MB/s 3:20:50 2 82.1GB
Source OneDrive-2 7.0MB/s 26.3MB/s 69.7MB/s 3:20:38 2 82.1GB
Source OneDrive-3 7.0MB/s 20.5MB/s 53.2MB/s 3:21:01 2 82.1GB
Source OneDrive-4 7.4MB/s 262.2MB/s 60.9MB/s 3:10:14 2 82.1GB
Source OneDrive-5 7.2MB/s 32.4MB/s 69.7MB/s 3:13:44 2 82.1GB
Source OneDrive-6 10.5MB/s 26.4MB/s 63.0MB/s 3:20:28 3 123.1GB
Source OneDrive-7 11.2MB/s 28.1MB/s 61.0MB/s 3:07:41 3 123.1GB
Source OneDrive-8 11.5MB/s 29.1MB/s 73.2MB/s 3:03:09 3 123.1GB
Source OneDrive-9 11.1MB/s 26.3MB/s 63.0MB/s 3:08:47 3 123.1GB
Source OneDrive-10 11.2MB/s 28.6MB/s 63.1MB/s 3:07:41 3 123.1GB
Source SharePoint 74.4MB/s 62.3MB/s 134.0MB/s 4:17:23 63 1.1TB

[tomsinner]

Have you been able to confirm whether your proxy instances are hitting any specific resource ceilings during the OneDrive jobs? I’m curious whether the under-utilization of proxies might be related to throttling rather than VB365 job distribution.
Pips NYT

[Polina]

Hi Tatsuya,

First backups are expected to take more time. Typically, throttling limits are hitted more heavily during the initial backup. For Exchange, you can request Microsoft to temporarily release it for your tenant, while for SharePoint it's not possible. Multiple applications that you can configure today for SharePoint processing soon will be deprecated to address Microsoft one-app requirement.

It's hardly possible to saturate 5 proxies with protection of 25 users. The load is distributed automatically, and if you see that some of the proxies are not heavily used it simply means that those resources are currently not needed.

Thanks!