Failing backups and replicaion

[Yuki]

We had to power down all systems today in order to make power system upgrades and to redistribute the power load.

After all systems came up - some VMs are failing to backup or replicate

3/2/2013 10:58:25 PM :: Queued for processing at 3/2/2013 10:58:25 PM
3/2/2013 10:58:27 PM :: Required backup infrastructure resources have been assigned
3/2/2013 10:58:28 PM :: VM processing started at 3/2/2013 10:58:27 PM
3/2/2013 10:58:28 PM :: VM size: 60.0 GB (20.5 GB used)
3/2/2013 10:58:28 PM :: Using source proxy MAIL-FE [hotadd]
3/2/2013 10:59:16 PM :: Failed to prepare guest for hot backup. Error: Failed to connect to guest agent: unable to obtain guest IP address.
3/2/2013 10:59:16 PM :: Removing VM snapshot
3/2/2013 10:59:23 PM :: Error: Failed to connect to guest agent: unable to obtain guest IP address.
3/2/2013 10:59:23 PM :: Network traffic verification detected no corrupted blocks
3/2/2013 10:59:23 PM :: Processing finished with errors at 3/2/2013 10:59:23 PM

Replica - This VM failed once, but completed on next run

3/2/2013 1:44:28 PM :: Task failed Error: Child object with ref "vm-21" for object "Datacenters" (group-d1) was not found.
3/2/2013 1:44:28 PM :: Network traffic verification detected no corrupted blocks
3/2/2013 1:44:29 PM :: Processing finished with errors at 3/2/2013 1:44:28 PM

[Vitaliy S.]

Hi Yuki,

IP address is detected by means of VMware Tools, so make sure all tools are running and up to date. As to the second error message, then it looks like you've re-registed the VM in question in the VI, which led to the the moref ID change? Is it the case?

Thanks!

[Yuki]

Privet!

No, we haven't touched the source VMs at all. We only powered them down along with physical hosts in order to add more batteries to our UPS systems. Once servers came up, we re-enabled our regular backups and replication jobs.

[Yuki]

I've went into vSphere client and did "Install/Update VMware tools", after that did "Retry" in Veeam and that resolved the issue on the VM that would fail to be backed up saying that Veeam couldn't connect to its IP.

[Vitaliy S.]

Good to know that you've solved it!

[TomBlue]

I had the same issue after rebooting any host because of firmware updates. Update/reinstall of VMware tools solved "IP problem" for two VMs too. But I do not know why this problem has arised though VMware tools were actual and up and running before? Just be curious.

[Vitaliy S.]

IP address and other VM related info is retrieved through VMware Tools, sometimes these tools do not provide any info for various reasons.