Veeam Backup for Microsoft Azure (external repository)

[azizm]

Hello,

A feature I would love to have would be Microsoft Azure Blobs as an external repository. Veeam SOBR just doesn't work for what we want, even with v10.

According to this post thread (object-storage-f52/v10-rtm-don-t-work-w ... 64508.html), this feature is "coming later this year". Would that be Q2/Q3/Q4 2020?

We would like to keep only backup jobs on the local storage, backup copy jobs should only be in Azure. It seems we can't do this with SOBR and v10 as SOBR requires 2 "Restores Points to keep" minimum.

Thanks,
Aziz

[dalbertson]

You are mistaking the freatures. External repo is not meant for cloud tier. It is used with a upcoming product for backing up instances inside of azure.

For cloud tier you can create an an object storage repo.
https://helpcenter.veeam.com/docs/backu ... ml?ver=100

[nielsengelen]

There seems to be some confusion here. The external repository option means you can add either Veeam Backup for AWS or Azure (coming soon) as an external repository so you can see the backups created by the specific product. Veeam Backup for Microsoft Azure allows you to create backups for your Azure virtual machines onto Blob storage.

Within SOBR you can add Object Storage and use that to send a copy to S3/Azure Blob.

[azizm]

You are mistaking the freatures. External repo is not meant for cloud tier. It is used with a upcoming product for backing up instances inside of azure.

For cloud tier you can create an an object storage repo.
https://helpcenter.veeam.com/docs/backu ... ml?ver=100

Got it, I was mistaking a different feature.

Two questions.

1. Why can't we reduce the minimum requirement for SOBR 'Restores Points to keep' from 2 to 0? I don't want any to stay on disk, age out then go to Azure and then be deleted from disk.

2. Will we ever get the ability to add Azure/AWS Storage or blobs as external repositories?

Thanks.

[dalbertson]

1. I’m not sure I fully understand what you are asking here. But best practices are to keep recent backups local for restore performance and cost considerations. Cloud object storage is not designed or priced for the primary backup storage use case at this moment.

2. External repository will be used with Veeam Backup for Azure when it is released. It will be used to mount the Azure blobs storage containers with backups from that product and used to leverage VBR to easily work with those backup files.

[nielsengelen]

2. You can use Azure/AWS Object storage in VBR by using the Cloud Tier (Capacity tier).

Some more information on this:
- Capacity tier in our user guide
- Veeam Cloud Tier whitepaper
- Veeam's blog post
- Veeam's blog post on v10 changes

[Gostev]

2. Will we ever get the ability to add Azure/AWS Storage or blobs as external repositories?

I think you keep confusing the terminology, and really you wanted to say "as backup repositories". In other words, you're asking about direct backup to cloud object storage. Am I correct?

If yes, can you comment how are you planning to achieve the 3-2-1 rule in this scenario? In my mind, this has been the biggest question about backing up directly to cloud.

Also, there are some technical challenges to consider:

1. Backup: going direct to cloud means longer backup windows, so longer VM snapshot life time and corresponding impact on production environment. Is this not a concern?

2. Restore: restoring directly from cloud means at least a few time longer restores than from local storage. Is fast restore not required in your case?

I guess I'm just trying to understand what kind of environment are we talking about here. Is it something very small, without any I/O intensive workloads, and without strict RPO/RTO requirements?

[syedzeeshan]

When we sent backup using scale out repos to azure blob the backups are dedup or dehydrated?

[nielsengelen]

@syedzeeshan your question was already answered in the other topic.

[syedzeeshan]

Ok thanks for replying back

But the want to use external repo where I can connect azure cloud box and transfer all data on the box later on azure will ship to connect to our blob storage it will work?

Below scenario for scale out I am assuming

E.g I have sql server 1Tb when veeam backup with applaince dedup its size is reduced to 400gb

When scale out repo will sent this backup it will be 1tb first time ?

If I keep 3 restore points the incremental deltas are smaller in size like 50gb

On scale out since its second backup it will same size or reduced

The issue is sending dehydrated data will have major impact on our internet link

[nielsengelen]

This is explained in our user guide on how to use Azure Data Box.

[syedzeeshan]

Thank you really appreciated