On friday i was installing the I/O Error Fix Patch " KB-1008130. The install was fine and without problems. Now i got the following problem.
If i start a Backup via vcb, the VMWareTools runs and the VMWare-"Tools Status=ToolsOk".
The snapshot is done and the VMwareTools get the state "Not running"
so the backup cannot work successfull! If i start the vmware tools manually the same effect appears.
Did some tests today using vcbmounter.
Same problem as with Netbackup.
As soon as VC start creating snapshot Vmware Tools change status to "Not running".
However one difference.
vcbmounter successfully finished copying the vmdks which Netbackup fail to do when this error happen.
I'll throw my hat into the mix as well... I'm getting the same result, and I'm running NetBackup 6.5.3. Snapshot error 156.
Since we don't have a huge amount of VM's, and since it doesn't look like its affecting ALL of them, just some of them (which is strange) I found that simply logging into the vm, and logging out will cause the tool to start responding. The a restart of the Netbackup job will succeed.
Where's the bug fix VMWARE?
UPDATE: I called into Vmware's support and was informed that they are aware of the issue and have escallated to RnD for a fix. No ETA yet. Internal Vmware Bug ID: 374389
Message was edited by: EPL
So i finally recieved an answer from VMWare Support:
"A fix has been identified for patch 12, but I cannot confirm if this will be the exact release vehicle"
II am not sure what this means but i will update to VC 2.5 Update 4 (released 23 feb) somewhere his week, hope that solves it.
Lame workaround for windows VM's, but it's easier than logging into each server.... from a workstation have a batch file to restart vmtools service
<vmname> stop vmtools
<vmname> start vmtools
Argh! can't show slashes with the post
sc double backslash <servername> stop vmtools
sc double backslash <servername> start vmtools
Now just copy and paste, and put in servernames for all your vm's that you need visible for backup by netbackup and schedule it to run every day until they come out with the patch.
I was told that the patch will be released in March also.
The reason some backups fail when the status show "not running"is because they're using VCB. I have the same VMware Tools issues with the bug except the backups still run okay, but we don't use VCB. We use NFS with a Netapp appliance and call the backups via Snap Manager for Virtual Infrastructer (SMVI).
I guess using that strategy paid off in this scenario...sheww! Sorry to the others having to suffer through this until the patch is released...
upgraded to VirtualCenter U4 this morning, and the problem still exists.
netbackup calls out VCB, completes the backup, and vmtools goes to 'not running' causing subsequent jobs to fail.
also, is there some trick to getting crontab to run on ESX?
is doesn't want to run the 'service mgmt-vmware restart' command.
00 8 * * * root service mgmt-vmware restart
Simply add this line to /etc/crontab. Change the "8" to whatever hour you want in 24 hour format.
works great, thanks. i was doing it incorrectly.
Same problem, after backup by vcb a lot of vm report a "tools not running" state.
I don't want to restart mgmt service by cron because this causes a "host disconnect" alarm and sametime DRS problem
We are waiting for a ESX-patch that we hope will be avaible soon.
answer from VMware support:
This is a known issue with VCB, and our engineers are working on the resolution.
The possible workaround to this issue at the moment are:
1. Restart mgmt-vmware service immediately once the backup job is done. This will bring the tools status to OK. One can write a cron job to do it periodically.
2. Log in and Log out OR simply log out (if already logged in) from the VM. This will cause the tools status to go "OK" if it was showing as "Not running" before.
3. Use VCBMounter to look for VM name or UUID rather than VM IP. VM IP will only work when the status of tools is "OK", but VM name and UUID will work even if the tools status shows as "Not running".
The patch will be available as soon as our engineers will find the root cause of the issue and write appropriate patch.
This could take weeks or months.
We have the same problem with a customer of ours.
VC says VMware tools are 'not running' while the are.
Because of this VCB Failes!
I have opened a SR at VMware, and they answerd me that it will be fixed in update 4 of ESX.
We can't wait until then for this to be solved, so they say to use the Crontab workaround.
But because of our monitoring, if we do this a support engingeer will be notified everyday when the crontab runs, and VC looses his connection.
So for us this isn't a solution either.
Has anyone heard something of a temporary fix for this problem?