...
This information was gathered from support cases as well as certification testing of Veeam V12.
The following acronyms are used in this article for clarity purposes:
VB365 = Veeam Backup for Microsoft 365
...
VBR = Veeam Backup and Replication
Veeam Backup for Microsoft 365 ( VB365 )
| Warning |
|---|
VB365 does not support versioning or object locking. |
Veeam Backup for Microsoft 365 VB365 only has a single way to configure the number of threads (default is 64 ) it uses to communicate with the backup repository. Reference: https://helpcenter.veeam.com/docs/vbo365/guide/vbo_threads_and_limit.html?ver=70
In a mixed environment if your backup repository is overwhelmed with too many concurrent connections we recommend reducing the backup proxy threads.
VB365 stores data items in chunks to the object storage repository. These chunks are before compression 5MB for Exchange data and 8MB for SharePoint and OneDrive data. Veeam documentation says that you can assume 40-50% compression efficiency.
| Note |
|---|
VB365 has hardcoded chunk sizes , those are not configurable. |
| Note |
|---|
VB365 stores meta-data in their own objects. These objects are small in size (100KB or less) and can make up for up to 50% of the overall number of objects in an object storage repository. |
Source reference material: https://bp.veeam.com/vb365/guide/design/sizing/objectstorage.html
Veeam Backup and Replication ( VBR )
...
Using larger block size can yield up to 3.5x faster performance. We recommend at least 4MB block size.
This is done in the backup job properties → Storage section → Advanced Settings → Storage Tab.
...
| Note |
|---|
Setting the block size to 8MB for best performance requires a PowerShell script, Example: |
...
Your Performance Tier has an option to user use per-machine backup files, which is the recommended option, this increases the number of concurrent threads VBR uses , but in some scenario’s this can overwhelm your backup repository.
Example: if you setup a backup job to backup 2 VM’s and have this option enabled as well as 8 backup proxy threads then Veeam will use 128 concurrent connections to communicate with the backup repository.
| Info |
|---|
Concurrent Connections = Backup Proxy Threads x AWS S3 SDK ( uses 8 threads per operation ) x Backup Job Total VM’s |
...
Additional configurable parameters on the VBR side
...
Max Concurrent Tasks per Backup Proxy
...
, by default Veeam will set this according to the amount of CPU cores detected by your VBR server.
...
Network Traffic Throttling on the backup proxy
...