Skip to main content

Hi all,

I have recently deployed Veeam Backup & Replication and have started to copy backup sets into Azure blob storage for archive purposes. I've been keeping an eye on the Azure costs which seem to be a bit higher than first anticipated. So far in the past 7 days I have pushed around 4TB into the storage account. 

I see total ingress for the past 7 days as 4.12TB and total egress as 83.24GB. The egress seems high for what should be just pushing data in and forgetting about it. Does anyone have any pointers on how to fine tune the copy job and storage repository? Does that amount of egress seem normal?

My repository is configured to use cool blob storage and has vPower NFS enabled.

The copy jobs are configured for Immediate copy, include tlogs, GFS retention, not to read the entire restore point from source backup instead of synthesising it, no backup files health check, and auto compression level.

Any assistance on tuning this is greatly appreciated!

Hi @neil.b try to use azure monitoring tools, which will help you identify and mitigate the specific causes of these charges.


Thanks for the response @waqasali, unfortunately my tenant is supported by an ISP which I don’t have access to anything billing related. I have reached out to them to see if they can provide further details on the costs - I can only see ingress and egress metrics at present.

Do you know if 83.24GB egress is an expected amount over 7 days when I am only copying data to the storage? No restores have been done from that data. I suspect that the higher costs will be either egress or API call related so is there any guidance around minimising these processes? For example, do I set the copy job to “read the entire restore point from source backup instead of synthesising it”, would that make any difference? Or any other settings worth investigating?


Hi @neil.b -

Maybe @MicoolPaul has some insights?


Hi @neil.b if the process only involves pushing data without restores and mitigate this review backup configurations and adjust any settings that could trigger metadata retrievals.


Are there any guides as to what each setting in the copy job setup does and their impact on cloud storage? E.g. what settings impact metadata retrieval, what settings increase data reads and transactions etc? 


Comment