Question on the recommendations being made in the UI, vs my present understanding. Within a B2D job, Storage > Advanced > Storage > Storage Optimization, we've got a number of storage sizes, 256kb all the way up to 4mb.
My present understanding of Azure object storage, and how I was using it for a capacity tier in a SOBR, 4MB was optimal because Microsoft uses 4MB regardless. Sending a 1MB block to them would just mean that it was 75% empty, and subsequently, 75% wasted space (which of course you are still paying for).
The UI, however, which absolutely changes it's appearance when backing up to a repo in the Veeam Vault, as opposed to an on-prem repository, retains a 1MB recommended block size.
This repo is intended as a last resort that I honestly hope I never need to use. Am I better served by changing the storage optimization size to 4MB?
-
- Expert
- Posts: 205
- Liked: 36 times
- Joined: Jul 26, 2012 8:04 pm
- Full Name: Erik Kisner
- Contact:
-
- Veeam Software
- Posts: 19
- Liked: 11 times
- Joined: Jul 13, 2020 3:47 pm
- Full Name: Kirill Chukhlantsev
- Contact:
Re: Veeam Vault - Storage Optimization Size
Hello,
Azure object storage charges you based on the actual data stored, not by rounding up to fixed block sizes like 4MB. So if you send a 1MB block, you're only charged for 1MB - there's no "wasted" space in that sense.
That said, using smaller blocks does mean more objects get created, which will increase the number of transactions (during uploads and maintenance). Larger blocks reduce the transaction count, but might not be as efficient for incremental backups, since even a small delta will trigger the read of a full 4MB block.
For Veeam Vault, the recommended 1MB block size is offered based on an optimal balance between object size and backup chain efficiency.
Hope that helps!
Azure object storage charges you based on the actual data stored, not by rounding up to fixed block sizes like 4MB. So if you send a 1MB block, you're only charged for 1MB - there's no "wasted" space in that sense.
That said, using smaller blocks does mean more objects get created, which will increase the number of transactions (during uploads and maintenance). Larger blocks reduce the transaction count, but might not be as efficient for incremental backups, since even a small delta will trigger the read of a full 4MB block.
For Veeam Vault, the recommended 1MB block size is offered based on an optimal balance between object size and backup chain efficiency.
Hope that helps!
-
- Expert
- Posts: 205
- Liked: 36 times
- Joined: Jul 26, 2012 8:04 pm
- Full Name: Erik Kisner
- Contact:
Re: Veeam Vault - Storage Optimization Size
That definitely helps, thank you! I must have confused API calls with storage usage. Thank you very much for clarifying that.
In a normal object storage repo, the extra transactions would carry a (mostly trivial) additional cost, which was why I ended up optimizing for 4MB. But since all those writes are included in Vault V2, 1MB definitely sounds like the smarter choice.
Thank you again for your help, I appreciate you taking the time to answer this question for me.
In a normal object storage repo, the extra transactions would carry a (mostly trivial) additional cost, which was why I ended up optimizing for 4MB. But since all those writes are included in Vault V2, 1MB definitely sounds like the smarter choice.
Thank you again for your help, I appreciate you taking the time to answer this question for me.
Who is online
Users browsing this forum: No registered users and 4 guests