VEEAM backups best practices
The storage team has been working on a list of technical recommendations for VEEAM backups using SCS3 clusters.
These recommendations aim to improve the performance, security, and efficiency of the clusters and as a result of your VEEAM backups.
Here are the recommendations to follow:
| Item | Value | How to configure |
|---|---|---|
| Block size | Set to 4MB (large blocks) or 8MB (extra large blocks). | Through the VEEAM interface. |
| Immutabitily Retention Period | Should be less than the backup retention period. Set a retention period of 90 days or less to limit storage usage and the number of S3 requests. |
Through the VEEAM interface. |
| S3 Repository Task Limit | Set as low as possible. Start with 2. If backups can't finish timely, increase the value. |
Through the VEEAM interface Through the registry: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\S3ConcurrentTaskLimit |
| Limit object storage consumption | Do not limit it. | Through the VEEAM interface. |
| SOBR Configuration | Create a bucket for every 100 VMs or 100TB of data to be backed up. Use multiple buckets. A big number of objects in a single bucket kills the performance of some operations (like listing). It is thus better to have more smaller buckets. |
Through the VEEAM interface. |
| Limit Deletes per Request | Limit the number of objects to delete per request to 500. | Through the registry:Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\S3MultiObjectDeleteLimit |
These recommendations are crucial to ensure smooth operation. We kindly ask you to implement them.
If you have any questions or need assistance, please do not hesitate to contact support.