...
Use large storage object size in VBR and VBA ( 4MB or higher )
Assign a dedicated bucket and storage domain per client. This will allow you to take advantage of future support for separate elasticsearch indices per storage domain.
Keep VB365 and VBR in different buckets, as VB365 does not provide the ability to control storage object sizes.
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.
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?
Do not configure Swarm as the primary performance tier, we are not certified for this configuration mode.
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 |
|---|
Concurrent Connections = Backup Proxy Threads x AWS S3 SDK ( uses 8 threads per operation ) x Backup Job Total VM’s |
...
Allowed Backup Job Target Configuration
Configuring the backup job with direct to object storage as primary ( performance ) tier is not allowed, as we are not certified for it. ( Requires Veeam Ready Repo badge )
The allowed configuration mode is only as a Scale-out Repository where Swarm is the secondary, capacity backup target.
...
Additional configurable parameters on the VBR side
...