lobo519 wrote:The static route that is added to the Veeam server by the job on our main site is 10.10.10.0 255.255.255.0 192.168.5.5.
192.168.5.5 = vlab appliance at our colocation which is on a site to site VPN with our main site..
10.10.10.0 = Masquerade IP
What am I missing?? I am thinking its a routing issue but not sure where the break down is..
You're right, it's a routing issue. Veeam can only add a static route to the proxy appliance NAT to your Veeam server, it can't add it to your routers or even to the correct gateway. Notice about that we added a route to 192.168.5.5 because we expect 192.168.5.5 to be on the same network with the Veeam server. In your setup, it is not, it's remote, so you would need a static route to your local gateway, and then your gateway (and any other gateways in between) would also need this route added.
It's completely possible to actually do this, but it's a complex setup. There's already some threads where I have outlined the required steps, but effectively it involved making sure that your entire network will properly route the NAT network to the proxy at the remote site.
Other options include configuring a layer-2 bridge between the two sites, from the Veeam server to perhaps another server at the remote site or I've known one customer that used a VPN configuration, I think using OpenVPN.
Another, sometimes simpler option is to just install a copy of Veeam at the remote site and use this instance to run the SureBackup job.