Multi Cloud

[danistadelmann]

Hi floks

Our customer defined the requirement that Veeam Backup for Azure data need to be copied into AWS S3 immutable. The only way possible these days is: creating a VM with Backup & Replication configure an "Azure IaaS Copy Job" which reads the data from blob to local disk and from there into AWS S3 immutable. Are there any planning for implementing this possibility directly into Veeam Backup for Azure? The current setup is quite stupid and expensive.

Kind regards
Daniel

[dalbertson]

Hi Daniel, would you expect going direct from azure to s3 to be any cheaper?

[danistadelmann]

Hi Dustin, yes correct. Without the need to rehydrate the data from blob and storing the same data on managed disk only for ability to copy into s3.

[dalbertson]

This would not work that way. Any read or copy of data from blob would have a cost. Any egress outside of Azure would have a costs.

I can understand the want for a copy to aws. But it would not be any cheaper than the current method.

[danistadelmann]

I have to disagree. With the direct copy to aws I no longer have to cache / temporarily store the data and pay this managed disk.

[dalbertson]

This is different then, you want to be able to have an AWS S3 bucket as a repo in Veeam Backup for Azure so that it writes the data directly to AWS and not write to blob first and then copy to aws.

There would still be internet egress charges in this use case but not the blob egress.

[danistadelmann]

Correct and this is also expected but the costs will massivly decrease for this setup. Are there any planning for S3 as backup repo in Veeam Backup for Azure?

[dalbertson]

Would this be a one time migration use case?

Think about restorations if not, any restore is going to have egress charges and other fees. The latency and speed of writing across the internet would make an impact on performance. The demand for such a use case has not been seen.