Virtual Lab - Ping Fails

[cvacanti]

Support case: 00701892

I set the vNIC for the virtual lab to the gateway IP of our production servers. I've also set the subnet mask as the same as our production network. I've verified that the route shows up in my route print on the veeam server when I run a surebackup. However the pings continue to fail. The virtual lab and the veeam server are on the same host and that the networking vswitch is there and the vms are attached to it.

What else can I try?

Chris

[foggy]

Is there any firewall enabled inside the guest (for example, Windows firewall could block pings for public networks)?

[cvacanti]

There's a KB from Veeam that discusses that. You run a command on the production VM, back it up, then run the surebackup and the firewall will not be on. I've done that already.

[Vitaliy S.]

What about other checks? Do they also fail?

[cvacanti]

Heartbeat passes. Ping fails. Application check fails.

[Vitaliy S.]

Heartbeat information is received via VMware Tools, as to other checks then they are using network connection. Let's see what your support engineers finds out after reviewing your logs and configuration.

[cvacanti]

Figured this out - it wasn't anything to do with the virtual lab exactly.
See if this solves your issue:

Setup your surebackup with zero checks, no heartbeat/pings/applications.
Ensure that "Leave power on" is enabled on the virtual lab.
Add 1 vm to the application group.
Start the surebackup.

Once the VM in the lab is powered on open the VM console, login with local creds, and verify if the firewall is on in the vm set to public. If so turn it off...and test your pings. They should work. Look here at setting this rule on the prod vm so that when it is in the lab pings work: http://support.microsoft.com/kb/947709