Scale Out Backup Repository Evolution

[Stabz]

Hello,

I m a service provider, currently I'm using a SOBR with one extent in my performance tier and one extent in ma capacity tier.
We are near the full capacity in the performance tier.

It's a hardend Linux repository, I would to know if I could add another volume on this server and add it as a new extend in my SOBR without problem of configuration/performance ?

Second question we are using only one bucket in the Capacity tier, should I consider to add another one ?

[Stabz]

Additional question, the SOBR is set with Data Locality policy. My customers have retention policy like 14D 4W 6M.
When the first extent will be full, incremental backup will failed or a new active full will be create to my new extent?

[sfirmes]

Second question we are using only one bucket in the Capacity tier, should I consider to add another one ?

Philippe, there is no requirement to have a 1:1 matching of the number of performance tier and capacity tier extents. The recommended number of capacity extents is something I typically ask the object storage provider. Some object storage platforms benefit from having multiple capacity extents, while other see no benefit and they recommend using just one.

[Gostev]

The majority of on-prem object storage devices benefit from multiple buckets because they create separate metadata database for each bucket. So it helps scalability to have many buckets.

Few exceptions include Pure and Object First (and possibly also Dell ECS), these do not benefit from multiple buckets because they load-balance under the hood.