| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
The purpose of this KB document is to provide our recommendations for the use of Veeam V12.
This information was gathered from support cases as well as and certification testing of Veeam V12.
...
When using multiple gateways in your environment make sure to use a real load balancer, DNS round robin is not a valid load balancing configuration. We recommend using the least connection load balance algorithm.
| Info |
|---|
Least Connections:The system passes a new connection to the gateway that has the least number of current connections in the pool. |
...
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.
| Info |
|---|
ImportantVB365 has hardcoded chunk sizes, those are not configurable. |
...
Veeam Backup and Replication (VBR)
| Info |
|---|
ImportantMake sure to install and use V12 Cumulative Patch 3 or higher, where the concurrent delete threads were increased from 1 to 10, affecting the performance of all their backup jobs. Reference: https://www.veeam.com/kb4420 |
| Note |
|---|
WarningData in an object storage bucket or container must be managed solely by Veeam Backup & Replication, including retention and data management. Enabling lifecycle rules is not supported, and may result in backup and restore failures. For more information, see https://helpcenter.veeam.com/docs/backup/vsphere/object_storage_repository_cal.html?ver=120#general-considerations-and-limitations. |
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 |
|---|
WarningBe aware that backup copy jobs inherit the Storage optimization of the backup job its backing up, you will not be able to modify it on “backup copy” type jobs. |
...
By default, the cloud gateway 7.10.4 uses 50 threads to execute S3 MultiDelete requests, you can improve performance by increasing MaxRecursiveDeleteThreads recursiveDeleteMaxThreads to 250 in /etc/caringo/cloudgateway/gateway.cfgMaxRecursiveDeleteThreads
| Note |
|---|
recursiveDeleteMaxThreads can overwhelm your Elasticsearch cluster if its not sized for the workload, in some situations you may have to reduce this configuration to get less CPU load on Elasticsearch. |
recursiveDeleteMaxThreads must always be lower than threads and maxConnections
so if you set MaxRecursiveDeleteThreads recursiveDeleteMaxThreads then we recommend also changing:
...
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 |
|---|
ImportantConcurrent Connections = Backup Proxy Threads x AWS S3 SDK (uses 8 threads per operation) x Backup Job Total VM’s |
...