Veeam Server and Virtual Lab on different subnet 00627141

[dtwiley]

Hi again, I've had a good read of the documentation and I understand how the virtual lab proxy works but i'm struggling to get successful ping tests from the backup server which is on another subnet in another site.

My setup is as follows:

Veeam Backup Server: 192.0.0.99 (I know, we inherited it)
Production Server eg: 192.168.100.20
Virtual Lab Router Server: Production LAN 192.168.100.252 / Isolated LAN 192.168.254.0/24

When the lab comes online I can see a static route being injected in the Veeam server giving it a route to 192.168.254.0/24 via 192.168.100.252 which we know it can reach as its default gateway has routes to this subnet.

So when the recovered server comes online it has a masquerade IP of 192.168.254.20 which the Veeam server knows how to reach as a result of the injected route, so why do ping tests fail?

If I manually add a static route to a server in the 192.168.100.0/24 range then I can ping the masquerade IP with no problems.

One of the reasons the Veeam Backup server is off of the subnet is because I have a tape drive directly attached to it on premise, whereas the production environment is in a datacentre.

Does the Veeam Backup server HAVE to be on the production LAN or is there a workaround, I've read the notes for manually configuring the network but this only appears to be relevant if the Veeam Server is on a different VLAN on the same VMware environment.

[nefes]

Hello Dave,
If I understand you correctly, 192.0.0.99 and 192.168.100.252 are in different sites?
If so, when you try to ping some address in 192.168.254.0/24, traffic goes to your router at Backup Server side, which is not aware of 192.168.254.0/24 subnet.
By default, when Backup Console and Virtual Lab are in the same subnet, static route on backup console will bypass gateway and ping will go directly to Lab.
In your case you will need to set up routing on your hardware manually, or deploy additional Backup Console in Prod network.

[dtwiley]

That's correct, I understand what you say however when I start the lab it injects a route into the Backup server (route add 192.168.254.0 mask 255.255.255.0 192.168.100.252), shouldn't this do the same thing? If I add the routes into my infrastructure how do I stop Veeam Backup injecting the route locally?

[dtwiley]

FYI I made the infrastructure change on the switches and it now pings Proceeding with SureBackup Setup

[nefes]

I'm not a networking guru, so my explanation will be in plain words.
Let's say you have local route on server A, that says that packets to C should go through B.
When you have server A and server B in same subnet, this route will bypass gateway in the network, and all packets will go directly from A to B and then to C.
When A and B are in the different networks, path from A to B contains router. But when router gets the packet, that is addressed to C, it does not know, that such packet should go through B and drops it.

Glad that you are up and running but will leave the explanation above for future readers.

[foggy]

Actually, the need to manually add the corresponding route is covered in the user guide.