VMware 5.5 and BE2012 SP3

[gsi_office]

HI,

we updated vmware to esxi 5.5 and vcenter to 5.5

I installed SP3 on BE 2012 and then I updated BE agent on VM (win server 2003/2008).

When I updated VMtools to version 9.4.0, backup exec returns this error :

Final error: 0xe00095a7 - The operation failed because the vCenter or
ESX server reported that the virtual machine's configuration is invalid.
Final error category: Resource Errors

I disabled the VMware Filesystem Sync Driver and Volume Shadow Copy
Services Support and then i restarted the VM, but backup exec doesn't work.
(return the same error).

Could you please help me to solve this issue?

Thank You
 

[CraigV]

Hi,

While this refers to vSphere 4.1, the troubleshooting might be relevant.

http://www.symantec.com/business/support/index?page=content&id=TECH139019

Thanks!

[pkh]

After you update your VMTools, you should push out the BE remote agent to the VM again.

[gsi_office]

I tried to uninstall VMTools and BE agent. I reinstalled VMTools without VMware Filesystem Sync Driver and Volume Shadow Copy. I reinstalled BE Agent, but backup exec doesn't work (Final error: 0xe00095a7 - The operation failed because the vCenter or ESX server reported that the virtual machine's configuration is invalid. Final error category: Resource Errors).

I tried to remove VMTools and backup exec works fine.

We need VMtools to use Granular Recovery Technology.

do you have any other ideas?

[William_Donigan]

Hello,

Enable Debugging to troubleshoot the VMware agent per the following tech document –“http://www.symantec.com/docs/TECH63926”

Run a backup job on a VM that has VMware Tools installed; Collect the debug logs per the tech document above and the job log with the HOSTD log from the ESX host. You can find the location of the HOSTD log by following this VMware KB document-“kb.vmware.com/kb/2032076”

Once you have the logs please open a support case with us; you can find the contact information here -http://www.symantec.com/business/support/index?page=contactsupport&key=15047. 

[Peter_Faber]

was this fixed ???

i have the same problem, but dont have time for jet another support case... :\