Feature Request-Second backup copy for VM protection over BLOB directly

[NK100251]

Hi,

As of now there is no method to perform direct backup copy for VM backups via Veeam-Azure appliance.

It either needs to be added with Windows repository (SOBR) and tier to blob. Which is difficult task as we need to maintain & size the windows server for backups.

Please add the direct second backup copy feature to azure blob storage account.

[nielsengelen]

Hi Neha,

You can use the built-in schedule to use different repositories per schedule. You can configure to create daily and weekly backups in 1 region and then use Archive Tier for your monthly and yearly backups (as an example). Have you considered this as an option?

[NK100251]

Hi nielsengelen,

We have Data domain as backup repository added on VBR server. I don't see any option to add data domain on Veeam backup for Microsoft Azure appliance.

Can you please explain what steps you are suggesting to perform as an alternative?

[nielsengelen]

This is not possible at the moment and there are no short-term plans to add support for DataDomain directly in VB for Azure. I was confused by your initial request to have an additional copy to blob storage however your end target is DataDomain.

Copying to other storage can be done using VBR and SOBR or backup copy jobs. We’ll consider an enhancement for a future release to copy directly but I can’t provide an ETA when this will be possible.

[HannesK]

Hello,
if I understood you correctly, then using the external repository with a backup copy job to data domain can solve the request today.

It either needs to be added with Windows repository (SOBR) and tier to blob.

I got lost here, can you maybe explain a bit more about your setup? Veeam Backup for Azure (separate product or as plugin to VBR) does not have Windows repositories or SOBR. In VBR, there is SOBR with (capacity) tier, but this is only for backups managed by VBR. It's not doing anything with backups of Veeam backup for Azure. To connect VBR with Veeam backup for Azure, the "external repository" is the way to go.

Just to be 100% clear: is the request about the product "Veeam Backup for Azure" or "Veeam Backup & Replication" or the combination of both products?

Best regards,
Hannes

[micoolpaul]

Hi nielsengelen,

We have Data domain as backup repository added on VBR server. I don't see any option to add data domain on Veeam backup for Microsoft Azure appliance.

Can you please explain what steps you are suggesting to perform as an alternative?

Are you using the VBfMA plug-in? If so you can create a backup copy job from Azure to a traditional VBR target such as data domain

[jorgedlcruz]

Hello,
Good point by Michael, directly from the Veeam Backup for Azure interface you would not be able to select a Datadomain Repository. But if you have already a Veeam Backup and Replication on-prem, you can follow the next steps to add your Veeam Backup for Azure Appliance.

Once you have that working, you will be able to see the Veeam Backup for Azure Policies, and Repositories, on VBR are called External Repositories.

Now, you can start doing what you just mentioned:

• Backup Copy Jobs to DataDomain (this will be a download from Azure Blob to on-prem, saying this to bear in mind the egress charges on Azure)
• Or, even Tape if you prefer!

One of my favorite options of all of this process is that you can Restore anywhere, back to Azure, perhaps AWS EC2, maybe on-prem VMware.

Let us know if this could work for you.

[NK100251]

@jorgedlcruz: We are looking second copy option over Azure blob storage not on-prem data domain target appliance. The reason is, all servers running over Azure are not going to be migrated on-prem. They will continue to run over Azure cloud. Hence looking for second copy option over Azure blob storage.

[micoolpaul]

Hi,

Think we’ve been confused by your prior mention of a data domain if it’s irrelevant to what you’re trying to achieve.

At the moment native VBfMA “Backup Copies” would be using the VBR plug-in, there’s some extra redundancy you can leverage with backup archiving but that isn’t a 1:1 backup to backup copy relationship.

I’d be surprised if we don’t see backup copies in an upcoming version.

I’d also suggest that, although you don’t want backups to be restored to on-premises, you consider a backup to on-premises or another cloud as part of your 3-2-1-1-0 backup strategy.

To do this you’d use the VBR plug-in. It’ll protect you if anything were to happen to your Azure tenant that your backups reside in.

[NK100251]

Hi Michael,

Thanks for your reply. As there is no option for second copy over Azure. I want to know whether there is any plan to add this feature in upcoming Veeam release version? This is one of the important point to secure two copies of data in Azure.

[nielsengelen]

You can already use multiple repositories within the schedule to have your backups in other regions. For a second copy, you’ll have to use VBR now. On adding this change within VBA, would you require this for every type of schedule?