API Call Cost Estimation for VBR?

[Drew Schlussel]

Found this for VBM - https://bp.veeam.com/vb365/guide/design ... orage.html and this section caught my eye -

API Call Cost Estimation
Normally public cloud providers will charge for API calls to the object storage. To help calculating the costs for these API calls, see the following data from Veeam internal tests running VB365 in Azure and backing up to Azure Blob storage.
Azure Blob API calls are charged per 10,000 calls, differ per type of call (write/read/list…) and on the Blob storage type (hot/cold…).
Please note that this data can vary based on the type and structure of the source data. It is only intended to get a vague idea of pricing.

Is there similar guidance for VBR? I'm writing an article about the costs associated with Azure blog storage and making some educated guesses (see below) that I need to fact-check as best as I can...

For a 5TB backup (5,120GB; 5,242,880MB), I would expect to see 5.2 million 1MB objects, requiring the same number of Write API calls. At $0.10/10,000 WriteOps, that's a cost of $52.42. I have no idea how many Read, List, or Other API calls to expect for the same backup job, but there's got to be some.
With the calculator in limbo, I thought I'd reach out and see what y'all know. Thanks!

[HannesK]

Hello,
and welcome to the forums.

That question is covered in the sticky FAQ

Sure, there is a few more calls than just only write (e.g. when retention kicks in, there are deletes), but that's irrelevant to calculate (except you use immutability, which is also covered in the FAQ)

Best regards,
Hannes

[Drew Schlussel]

Thank you Hannes! I should know better to read the FAQ first.
So... I'm not too far off. Instead of four (4) full, immutable backups per month, I can cut that back to approximately three (3) per month = one (1) every ten (10) days, per the FAQ note with respect to using immutability.

[jorgedlcruz]

Hello Drew,
You can use vse.veeambp.com as well. With some example workloads and retention, or even uploading your own VMware Tools, then select Object Storage and use copy, or move or both, it gives you some good estimations that you can export.

Give it a try, besides the great BP Hannes recommended.

[jorgedlcruz]

Hello,
Hannes reminded me in the morning that you were looking to get some estimations with Immutability. The good news is that the vse tool has it, but it is hidden as it is still a work in progress; plus of course, the tool should be used just as an estimation.

Immutability enabled has an impact on API calls, PUTS, etc. The VSE has a login option, I am sending to you the pass on a pm. As an example with and without immutability:

• 10TB
• 100VMs
• 10% growth
• 5% Daily change
• Retention 30 Daily, 4 Weekly, 6 Monthly
• 30 Days immutability

Normal Object with COPY/MOVE after 30 days:


Immutable 30 days Object with COPY/MOVE after 30 days:


I am sending you now on a message about how you can calculate the immutability, a work in progress.

Thanks Hannes!

[Bradato]

Hello Jorgedlcruz, greetings!
Is it possible for you to give me more information on how to get a budget of the PUT's with the immutability active? additionally, is it possible for you to share the excel file with me?
Thank you very much, I remain attentive