Cannot add Vault Repo for Azure

[dhayes16]

Hello All.
We recently upgraded our on-prem VBR to the latest 13.01 update. And since we are using Azure workloads we upgraded the Azure appliance to the latest build as well.

At the present time we have an on-prem VBR 13.01 server backing up local Hyper-VM's to an on-prem Linux Hardened Repo. Then we have a backup copy job for those VM's targeting Veeam Vault (Advanced). It works perfectly. Now, we also have Veeam VM's as well currently backing up to BLOB storage in the same tenant. We would now like to change the backup policy to send the backups to the new veeam vault instead of BLOB storage (That will eventually just age out). When I try to add the repository via settings/repositories and select Veeam Vault as the type the vault does not show up. As a test I created another vault in the same veeam vault advanced and it does not see it either. So I have the following questions:

#1) How to I resolve the issue above? Do all repos need to be added via VBR 13.01 on prem and will they just appear in Azure as a repo to use? I plan to just repoint the policy to the new veeam vault repo once I can see it.

#2) Somewhat related but to adhere to the 3-2-1 rule I would like to create a backup copy job to send the Azure VM's backup to the LOCAL on-prem linux hardened repo and perhaps create some surebackup jobs.

#3) Since we are running Veeam Vault Advanced and the repo is in the same region (US EAST2) will we be avoiding egress / ingress costs? (assuming I create the backup copy job from the veeam vault to use the repository and NOT the backup job).

As always thank you for any feedback.

Dave

[nielsengelen]

1. I would recommend to open a support case for insight on why this is not available.
2. You can use backup copy job feature within VBR to copy Azure VM's to another repository but this is currently not supported for Veeam Vault. SureBackup however is not available for Azure VMs.
3. Normally there are no costs for this unless it passes via a public network. I would recommend to analyze your cost explorer to see how this is handled and data flows.

[dhayes16]

Thanks.

#1) I opened a ticket..Case 08011471
#2) If that is the case and the vault is a primary repo then how would we accomplish 3-2-1? Is the vault meant for a secondary repo and not primary?
#3) OK...It would be pulling from the veeam vault and since it is the advanced version of vault we assume there would be no egress fees.

Thank you

[nielsengelen]

2. We do have this on the roadmap but I do not have any ETA for the future yet.
3. There shouldn't be any egrees fees but it's hard to 100% confirm this depending on the full setup. That is why I suggest to analyze it so that if you do see fees, it may require some specific changes to the configuration.

[andre.simard]

Hi,
Case #08072669
I’m not sure whether this is the exact same request as the original post, but in our case we are using Veeam Vault as the primary repository in Veeam Backup for Microsoft Azure.

Our requirement is to configure this Veeam Vault repository as an external repository in Veeam Backup & Replication (VBR) so that we can run a Backup Copy job and remain compliant with the 3-2-1 rule.

At the moment, this does not seem to be possible. In the Veeam v13 documentation (link below), a workaround is mentioned; however, Veeam Support does not appear to be aware of this option.

https://helpcenter.veeam.com/docs/vdc/u ... soft-azure

Could you please confirm whether there is an official or supported procedure to perform a Backup Copy of Azure VMs to Veeam Vault? If so, we would appreciate the correct steps or guidance.

Thank you.

[nielsengelen]

Hi Andre,

Can u help me understand on which build version of VBR v13 you are?

[andre.simard]

Hi.

Latest v13 version.

Thank you

[Vitaliy S.]

@andre.simard , to peform backup copy, you need to request shared keys access via the support team (the documentation is correct). If your engineer cannot help, just ask for escalation until it gets to the correct support queue.

In the next update of Veeam B&R, shared keys will not be required; you will be able to use an Entra ID app to connect to the external repository. Hope it helps!