SUREBACKUP PING TEST FAILED

[agmavarok]

Hi,

on Surebackup job, i've a issue on ping test.
the request failed on time out after 3 tests.
The Veeam server is an other VLAN than the production servers.
there 's no firewall rules on ICMP between veeam server and proxy appliance.
I try on Network configuration on Vlab , basic single host and Advanced single host, same problem.
on Advanced Single host Config :
Ip proxy appliance : 10.200.0.80 /24 GW 10.200.0.254
Network Settings : Appliance IP : 10.200.0.254 Masquerade ip : 10.255.255.x.
PS : the 2 vlans are routable

Any help appreciate.
Regards

virgil

[Mildur]

Hi Virgil

Can you ping the original vm from the backup server?
The only firewall which is able to block something in a surebackup job is the windows firewall.

The proxy appliance IP should be in the same subnet as the backup server. It makes it easier to access the isolated network.

Additional info from the guide:

- If you assign to the proxy appliance an IP address from the same network where the backup server is located, Veeam Backup & Replication will automatically add a new route to the routing table on the backup server.

- If you assign to the proxy appliance an IP address from a different network, you will have to manually add a new route to the routing table on the router in the production network. If you do not add a new route, tests and application scripts will fail and you will not be able to access VMs in isolated networks.

[PetrM]

Hello,

It seems strange that "proxy appliance IP" and "appliance IP" belong to the same subnet: 10.200.0.x/24. I assume that "appliance IP" means the proxy appliance address in the isolated network which is configured in this step. It should be the same as gateway IP of the production network to which VMs are connected.

Thanks!

[agmavarok]

Hi teams,

@ Mildur : the proxy appliance is on the same subnet that the production server
The Firewall is offline on both servers ( VBR server and production server )
I can ping from VBR to production servers
@ PetrM -> "Typically, the IP address set for the proxy appliance coincides with the IP address of the gateway in the corresponding production network." - > is OK

Regards

[PetrM]

Hello,

In this case, I suggest to check that VMware tools on failed VMs are up to date and open a support case. At first sight, configuration seems to be correct so I'd consider it as a technical issue.

Thanks!