Surebackup job - Where does the ping setting get its info?

[Dave-Departed]

Hi All,

Can anyone tell me where the Ping test portion of a SureBackup job gets its info from, please?

I ask because I've just set one up, and it's to test my Exchange 2010 infrastructure. My App Group contains a DC, a DAG member and a CAS/HT server, and the SB job is linked to the other DAG member job.

I just tested it, and the DC/DAG member in the App Group both passed their ping tests fine, yet the CAS/HT VM failed because it tried to ping an address that doesn't even exist on our production network? I looked, and the other DAG member/DC both seemed to pick random IP addresses to ping, and got lucky!

[Gostev]

Hi Dave, we obtain the IP address from VMware Tools within the VM (once it boots and gets assigned the IP address). Thanks!

[Bunce]

Hi All,

I just tested it, and the DC/DAG member in the App Group both passed their ping tests fine, yet the CAS/HT VM failed because it tried to ping an address that doesn't even exist on our production network? I looked, and the other DAG member/DC both seemed to pick random IP addresses to ping, and got lucky!

Take a look at the DAG's replication network IP's.

[Dave-Departed]

Thanks, guys.

But why would VMware Tools pick an address that doesn't exist (there is no device on our production network with that IP, and there certainly isn't within the App Group) to ping? What are the criteria for VMware Tools to pick that IP?

Bunce, it's not the replication network IPs, they are on a 172.16 subnet, whereas the production network is a 192.168 (the nonexistant IP I'm referencing is also on a 192.168, and so are the other IPs that the other VMs within the SureBackup job ping (successfully).

Thanks

Dave

[Bunce]

Hmm - does the vsphere client show as the IP's of that VM? It will show multiple if the tools detect them..

Ipconfig from within the VM itself doesn't give you anything unexpected?

[Dave-Departed]

I've not managed to check those things, as the job fails as soon as the ping test fails, and the VMs are torn down. I guess I could just check the tickbox to leave the VMs up after the job?

[Bunce]

Yeah disable all the tests and leave it running. You can at least then see what's being spun up.

[Vitaliy S.]

I would also suggest reviewing what IP address is returned by the VMware Tools in the lab. BTW, do you run Windows Server 2008 R2 or Windows Server 2012 on the CAS/HT VM?

[Dave-Departed]

All VMs involved are 2008 R2.

[Vitaliy S.]

Just a wild guess - could this be a similar issue?

[dellock6]

I was going to suggest the same, all 2008R2 need to be patched with that fix to properly work in SureBackup, or even clone and deploy operations.

Luca.