The purpose of this internal KB is to provide our recommendations for use of Veeam V12.
This information was gathered from support cases as well as certification testing of Veeam V12.
Veeam Backup for Microsoft 365 ( VBO )
Veeam Backup for Microsoft 365 does not support versioning or object locking.
Veeam Backup for Microsoft 365 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.
Veeam Backup and Replication ( VBR )
Make sure to install and use V12 Cumulative Patch 2 or higher which was released on April 12, where they increased the concurrent delete threads from 1 to 10, affecting the performance of all their backup jobs.
Reference: https://www.veeam.com/kb4420
DataCore recommends setting the storage optimization block size to 4MB for best performance. This is done in the backup job properties → Storage section → Advanced Settings → Storage Tab.
By default our cloud gateway uses 50 threads to execute S3 MultiDelete requests, you can improve performance by increasing MaxRecursiveDeleteThreads to 250 in /etc/caringo/cloudgateway/gateway.cfg
Note: MaxRecursiveDeleteThreads must always be lower than threads and maxConnections
so if you set MaxRecursiveDeleteThreads then we recommend also changing:
threads = 400
maxConnections = 400
MaxConnectionsPerRoute = ( maxConnections / Total Swarm Storage Nodes / Total Gateways )
Your Performance Tier has an option to user 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.
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
Backup Proxy Settings
Max Concurrent Tasks per Backup Proxy
Network Traffic Throttling on the backup proxy
New in V12 is the ability to set multiple traffic rules per backup proxy
Object Storage Repository Settings
Limit the concurrent tasks against the backup repository if it is overwhelmed
