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?
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?
Statistics: Posted by ekisner — Jun 16, 2025 3:56 pm
![VA – DVD-Audio Music Sampler Vol.2 (2003) [DVD-Audio ISO]](http://imghd.xyz/images/2026/05/13/4lSo1rN.jpg)
