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.

...

1. Use large storage object size in VBR and VBA (4MB or higher)

2. Assign a A new dedicated bucket and storage domain per clientmust be used for every SOBR and workload ( VB365 backup, archive backup jobs etc ) . This will allow you to take advantage of future support for separate elasticsearch indices per storage domain.

3. Keep VB365 and VBR in different buckets, as VB365 does not provide the ability to control storage object sizessupport versioning or object locking.

4. Veeam backup agent (VBA) now allows direct to cloud backup, it does however not provide you with a way to limit concurrent connections via the Proxy Threads like VBR does. You will need to define this at the load balancer level. Some examples are provided at the end of this article.

5. Be mindful of the capacity requirement if your backup schedule is aggressive and rapidly deletes data. Deleting data in Swarm is not immediate; it relies on a background health process to convert deleted (trapped) space back into free space and you will need sufficient free space to ingest new data while the trapped space reclamation occurs. For more information see KB article How do I fix trapped space?

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.

...

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.

...

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.

...

...

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

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.

...