Deploy Veeam Proxy in Azure

[Argon]

Hello,

We want to restore backups from our On-Prem environment into Azure. We have a permanent VPN connection between our On-Prem environment and Azure.
As a test we deployed a new Veeam Proxy into Azure (Add Proxy --> Azure) and came to the conclusion that there was a public IP assigned to it. Since we see Azure as a remote branch that is connected via VPN, we don't need that public IP.

Afte a little search I found the following KB: https://www.veeam.com/kb4014
I've created the Registry key on our On-Prem VBR server, rebooted the server and deployed a new Veeam Proxy in Azure (Add Proxy --> Azure).
When I logged into Azure I can see that the Veeam Proxy had 2 NIC's again. 1 with a public IP, the other with an IP in our Private range.

Now my question is: is it even possible to push a Veeam Proxy into Azure without a public IP assigned to it? Or did I something wrong and is this the reason why I still see 2 IP's attached to it?

Thanks!

[HannesK]

Hello,

is it even possible to push a Veeam Proxy into Azure without a public IP assigned to it?

yes, that's possible. There are two ways. The way described in the KB article and if you add a Windows VM in Azure as Managed Server to VBR. Any managed Windows server can be assigned to the Azure proxy role.

Did you try to connect to the internal IP address (directly or DNS?)? Is it working?

Best regards,
Hannes

[A.Bish]

Hello

We have deployed the Azure Restore Proxy VM with no issues. However we have 2 sites with separate VBR instances, both are copying backups to Azure blob.

We have connected the repositories to each other the other sites, imported backups successfully.

In case of a DR situation, we are looking to use the other site to manage the restore to Azure from the blob,

The challenge we are having is connecting the Azure Restore Proxy to both sites. The initial site used to create the proxy is fine, the second site is trying to create another proxy.

How can we use the same proxy for both sites as have a proxy for each site is an unneeded cost and overhead of management.

[HannesK]

Hello,
and welcome to the forums.

From a cost perspective, I would probably deploy a new proxy when the DR case happens. There should be enough time while the import happens.

and if you add a Windows VM in Azure as Managed Server to VBR

did you try that? adding a Windows VM to both VBR servers? I mean, it creates upgrade dependencies and I recommend to avoid it. But technically that should work

Best regards,
Hannes

[A.Bish]

Hello Hannes

Thanks for the quick reply.
So in general i could create 1 VM for each site (Site A and Site B). I could test the restore from both sites. If successful, document the creation of the VM. Power it down, delete it and create it on demand when there is a disaster.

Adding the one VM to both VBR servers i don't see as possible. The wizard forces you to create one rather than allowing to add an existing.

[HannesK]

The wizard forces you to create one rather than allowing to add an existing.

uhm no...it can be selected during restore (or I missed something in the question)