Skip to main content
  • EN

We've got a new blog post! This month, we're diving into the art of fine-tuning Veeam VBR for on-prem object storage. In this post we show how to optimize performance for Scale-Out Backup Repositories (SOBR) with a Capacity Tier, specifically addressing the challenges of using on-premises S3-compatible appliances. This with the registry key “S3ConcurrentTaskLimit”

Click here to read the full blog post and learn more about Veeam registry keys!

 

Oh...now that’s quite cool ​@kristofpoppe . Wasn’t aware there was a key to optimize SOBRs! Thanks for sharing!

Hi ​@kristofpoppe .First of all thanks for sharing this info. If I correctly understood adding this regkey, VBR server istruct the gateways to use more tasks with limit settings. But it depends from more factors as computational resources of proxies and maximum streams for every S3 storage permit. 

It's Correct? 

Thanks 

Hi ​@kristofpoppe .First of all thanks for sharing this info. If I correctly understood adding this regkey, VBR server istruct the gateways to use more tasks with limit settings. But it depends from more factors as computational resources of proxies and maximum streams for every S3 storage permit. 

It's Correct? 

Thanks 

Hi ​@Andanet The regkey is more a tool to limit the number of concurrent streams to the Object Storage so that this storage can ‘follow’ and you’re not overwhelming it with multiple streams which all require some CPU power of the object storage device. When lowering the value less streams are generated at the same time. Most of the cases the CPU issue is not in the proxy but in the CPU capabilities of the storage device. If you look at QNAP QuObjects you will see that it’s easy to saturatie the Intel Celeron which is inside of the device.

This is a great key and been asked by support to use it a few times to help with things.  Works great 👍 

Hi ​@kristofpoppe .First of all thanks for sharing this info. If I correctly understood adding this regkey, VBR server istruct the gateways to use more tasks with limit settings. But it depends from more factors as computational resources of proxies and maximum streams for every S3 storage permit. 

It's Correct? 

Thanks 

Hi ​@Andanet The regkey is more a tool to limit the number of concurrent streams to the Object Storage so that this storage can ‘follow’ and you’re not overwhelming it with multiple streams which all require some CPU power of the object storage device. When lowering the value less streams are generated at the same time. Most of the cases the CPU issue is not in the proxy but in the CPU capabilities of the storage device. If you look at QNAP QuObjects you will see that it’s easy to saturatie the Intel Celeron which is inside of the device.

Ok perfect. But this means best way to use is with low level storage instead enterprise S3 appliance.

Hi ​@kristofpoppe .First of all thanks for sharing this info. If I correctly understood adding this regkey, VBR server istruct the gateways to use more tasks with limit settings. But it depends from more factors as computational resources of proxies and maximum streams for every S3 storage permit. 

It's Correct? 

Thanks 

Hi ​@Andanet The regkey is more a tool to limit the number of concurrent streams to the Object Storage so that this storage can ‘follow’ and you’re not overwhelming it with multiple streams which all require some CPU power of the object storage device. When lowering the value less streams are generated at the same time. Most of the cases the CPU issue is not in the proxy but in the CPU capabilities of the storage device. If you look at QNAP QuObjects you will see that it’s easy to saturatie the Intel Celeron which is inside of the device.

Ok perfect. But this means best way to use is with low level storage instead enterprise S3 appliance.

Correct, for every local appliance check where the bottleneck is. If it’s the appliance, this regkey could limit the load to it.

Terms & ConditionsAccessibility statement