Discussions specific to object storage support as backup target
Post Reply
wa15
Expert
Posts: 256
Liked: 19 times
Joined: Jan 02, 2014 4:45 pm
Contact:

Veeam and Azure Blob Storage API calls

Post by wa15 » Mar 15, 2019 12:43 am

We are considering long-term archiving to cloud instead of tape. Looking at Azure Blob pricing, they charge let's say $0.010 per 10,000 write operations and 0.050 per 10,000 list/create operations for the cold-tier.

How does one go about knowing how many write operations or list/create operations Veeam does with SOBR? Trying to get an estimate of how much our monthly cost with Azure would be which requires having an idea of the number of read/write operations. How does one go about estimating this?

HannesK
Veeam Software
Posts: 4630
Liked: 599 times
Joined: Sep 01, 2014 11:46 am
Location: Austria
Contact:

Re: Veeam and Azure Blob Storage API calls

Post by HannesK » Mar 15, 2019 7:01 am 1 person likes this post

Hello,
the "educated guess" is approximately 1 PUT per 1MB of source data size for each full or incremental backup that is offloaded. Not counting deduplication between multiple full backups. That represents 99% of the API costs. Other PUTs and GETs are not really relevant. This is only for backup. Restore is a different story of course.

Best regards,
Hannes

wa15
Expert
Posts: 256
Liked: 19 times
Joined: Jan 02, 2014 4:45 pm
Contact:

Re: Veeam and Azure Blob Storage API calls

Post by wa15 » Mar 15, 2019 7:06 pm

Thanks Hannes. That helps.

Let's say our single full backup is 15TB, and we want to backup twice a month. Very first backup would be a full 15TB. Then the second backup would also be a full backup, but would be deduplicated with the first one. Is there extra extra API calls for that deduplication? Asking because you mentioned "Not counting deduplication between multiple full backups"

Also, any idea for read API calls in case of restore?

HannesK
Veeam Software
Posts: 4630
Liked: 599 times
Joined: Sep 01, 2014 11:46 am
Location: Austria
Contact:

Re: Veeam and Azure Blob Storage API calls

Post by HannesK » Mar 18, 2019 6:47 am 1 person likes this post

Hi,
Then the second backup would also be a full backup, but would be deduplicated with the first one
yes, correct.
Is there extra extra API calls for that deduplication?
not really. It's not classic deduplication where blocks are moved. it's similar to ReFS block cloning.

Best regards,
Hannes

wa15
Expert
Posts: 256
Liked: 19 times
Joined: Jan 02, 2014 4:45 pm
Contact:

Re: Veeam and Azure Blob Storage API calls

Post by wa15 » Apr 12, 2019 12:07 am

Thanks. To follow up, any ideas on the number of API calls in case of restores? Is there a ballpark figure per MB of data restored?

HannesK
Veeam Software
Posts: 4630
Liked: 599 times
Joined: Sep 01, 2014 11:46 am
Location: Austria
Contact:

Re: Veeam and Azure Blob Storage API calls

Post by HannesK » Apr 12, 2019 7:15 am

Hello,
it is not really possible to estimate restore calls. Example: if parts of the required data are still available in a local repository, we we use that.

Best regards,
Hannes

Gostev
SVP, Product Management
Posts: 25454
Liked: 3860 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Veeam and Azure Blob Storage API calls

Post by Gostev » Apr 12, 2019 12:34 pm

Worst case scenario is the number of non-zeroed 1MB blocks in the restored machine's disks. Usually less since we get matching blocks from local SOBR extents, as Hannes noted. Thanks!

wa15
Expert
Posts: 256
Liked: 19 times
Joined: Jan 02, 2014 4:45 pm
Contact:

Re: Veeam and Azure Blob Storage API calls

Post by wa15 » Apr 12, 2019 8:34 pm

Thanks guys!

wa15
Expert
Posts: 256
Liked: 19 times
Joined: Jan 02, 2014 4:45 pm
Contact:

Re: Veeam and Azure Blob Storage API calls

Post by wa15 » Jan 22, 2020 12:52 am

Bringing this thread back to life again for one more question:

We offloaded about 30TB of VBKs to Azure for an initial offload, resulting in about 24 million PutBlob operations. Do we expect this same number of Put operations for the next VBK offload? Or will that number go down since Veeam only offloads new data?

wa15
Expert
Posts: 256
Liked: 19 times
Joined: Jan 02, 2014 4:45 pm
Contact:

Re: Veeam and Azure Blob Storage API calls

Post by wa15 » Jan 22, 2020 1:24 am

In addition to the question above, what type of Azure API call is triggered when old backups are removed out of Veeam? And how many operations approximately per lets say 1TB of data?

HannesK
Veeam Software
Posts: 4630
Liked: 599 times
Joined: Sep 01, 2014 11:46 am
Location: Austria
Contact:

Re: Veeam and Azure Blob Storage API calls

Post by HannesK » Jan 22, 2020 7:14 am 1 person likes this post

Hello,
no, there will be less data transfer / put operations for the next VBK. Veeam will only offload the required data (incremental) to object storage. The concept of "real full backups" does not exist for object storage.

Imagine it like a REFS repository. The amount of data transferred is like an forever incremental chain.

For deletion: same like for upload. If you go into the storage account, you can see all the files. The opposite of "put" is "delete blob".

I just did the math on your 30 TB / 24 Mio puts and you have less than one put per MByte (did you change block size?)... in general it's about more or less one operation per MByte

Best regards,
Hannes

wa15
Expert
Posts: 256
Liked: 19 times
Joined: Jan 02, 2014 4:45 pm
Contact:

Re: Veeam and Azure Blob Storage API calls

Post by wa15 » Jan 22, 2020 7:01 pm

Thanks Hannes.

Regarding put operations for our 30TB offload, I think it is closer to 30 million as I didn't have the graph scaled correctly (and our offload is really closer to 29TB but I was rounding up) so the 1 put per MB is about right.

Post Reply

Who is online

Users browsing this forum: veremin and 2 guests