Best Practice for SureBackup Virtual Lab Proxy Appliance

[sarah.m]

Hi community,

I attempted to submit a support request first, as we are paying for support, but we are still using version 9.5 of Veeam B&R which is no longer supported. We cannot upgrade due to external integrations that don't support newer versions of Veeam yet. Hopefully I am following the guidelines of the forum by posting this.

I have Veeam B&R installed on a vm on 172.16.200.x network. The vms I want to verify are all on 192.168.3.x network.

Is it best practice to setup the production network of the proxy appliance on the 192.168.3.x network and add a static route? Or would it be better to setup the production network on the 172.16.200.x network and add static mapping to the specific vms?

My understanding from the documentation, is that if the production network matches the network of the Veeam server, the route is created automatically. When I set up the proxy appliance on the 172.16.200.x network I can see the route gets created from the logs but it cannot resolve the IP of the vms on the 192.168.3.x network. From the 172.16.200.x network, I can ping any vms on the 192.168.3.x network so I am not understanding why it can't route inside the virtual lab.

I may be misunderstanding how the routing works, so any insight would be greatly appreciated!

[HannesK]

Hello,
and welcome to the forums.

It's easier to put the proxy appliance in the same network as the backup server. I always recommend that, because then one does not need static routes in the physical network. And always use "advanced single host".

https://www.veeam.com/how-to-videos.html -> Data Reuse has some videos (also youtube and others have)

Best regards,
Hannes

[mcz]

...also be aware that you're kind of exposing the vm's to be verified via the proxy appliance. So I'd advice to only put the proxy appliance into a trusted, isolated network.

[HannesK]

What do you mean with "expose"? The mapped network only exists on the backup server in this scenario. No machine except the backup server can access the virtual lab without setting static routes.

The isolated VMs are on a dedicated vSwitch and routing (duplicate IPs / NAT) makes it impossible to break anything in production (as long as one keeps the settings Veeam configures and does not configure anything else that could have impact).