Capacity Tier drop-down box is empty

[bwright97]

Good afternoon everyone,

I'm running VBR 11.

Under Backup Infrastructure I've created two: (1). Performance Tier (2). Capacity Tier (Azure Archive Storage).

When I add a Scale-out Repository, there are a few steps
a. I can add the Performance Tier repository no problem. I've given the options seen in the Backup Repositories list.
b. The Placement Policy is next, which is an easy selection
c. The Capacity Tier selection is where I have my problem. When I click on the checkbox "Extend scale-out backup repository with object storage", and then click the drop-down box so I can select the Capacity Tier backup repository configured earlier, there is nothing in the list, it's an empty list.

Any ideas on what I'm doing wrong?

Thank you,

Bill.

[Mildur]

Hi Bill

Capacity Tier (Azure Archive Storage).

Azure Archive Storage can only be used for the Archive Tier, not for the capacity tier.
Add Azure Blob (Hot or Cool Tier) as object storage and you can choose it as the capacity tier in the SOBR settings.

Thanks
Fabian

[bwright97]

Perhaps this is a question for another time, but how do I take advantage of the Azure Archive Tier in Veeam? I'd like to use the Azure Archive for long-term backups due to cost. I guess my question is, if I can only use the hot/cool tier through SOBR, how do I then get that backed up data in the cool tier, into the archive tier?

[Mildur]

The offload happens from the performance tier to the capacity tier and then to the archive tier.
You can control when the older GFS restore points are moved from the capacity tier to the archive tier inside the SOBR settings.

For the capacity tier, I recommend to use the hot tier. Cold tier can lead to higher costs than the hot tier.

Thanks
Fabian

[bwright97]

You're awesome Fabian, thank you.

[bwright97]

Hi Fabian (or anyone else )

Are there examples online somewhere to show that the cool tier can lead to higher costs than the hot tier? I know my manager is going to ask to have some justification as to why we are using the more expensive Hot tier than the Cool.

Thanks!

Bill.

[Mildur]

Cool tier has higher transaction costs (from the price list below it costs twice as for the hot tier) and you have to keep the objects for a minimum of 30 days in that tier or there is an early deletion fee.

Best to calculate the required API calls and then compare the prices.

https://azure.microsoft.com/en-gb/prici ... s/#pricing

You can also use an alternative like wasabi which doesn‘t have this transaction costs, if you want to save money. But then you won‘t be able to use the archive tier.

[bwright97]

Thank you, much appreciated.