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.
It's another damn patch. We are dealing with it for a week, and currently there are only 3 solutions:
1)just log into guest machine and tools change state to OK
2)restart mgmt-vmware service
3)restart vmware tools service via post processing script afterwards vcb snapshot
have a good patching :smileysilly:
I have exactly the same problem, but in my configuration (I use Networker for backups) the only problem is that status of Tools displays as "Not running". Lucky for me, all backups on machines with "Not running" Tools works fine.
In my environment Tools are running on all VM's that shows "not running" status in VC. It's hard to check if Tools are running or not, because logging in to VM automatically changes Tools status from "not running" to "Tools OK". But you can use Computer Management Snap-in and connect to remote computer (VM with "not running" Tools) and check services. In my environment VMware Tools Service is running even if VC shows "not running"
Here is the reaction of VMWare:
Apologies for the delay.
I have determined that this issue may be due to a recently discovered bug applying patch ESX350-200901401-SG. The only way to get the VMware tools back to running status is to restart mgmt-vmware service , looks like some tools functionality is getting broken when it is called by the VCB.
Restarting mgmt-vmware service
When this operation is performed, the ESX will appear as 'unresponsive' in VC until the service restarts and sends heartbeats to VC
1) Ensure VMs StartUp/Shutdown are set to 'Disabled' in VC
Configuration Tab>Virtual Machines StartUp/Shutdown state 'Disabled'
2) On the ESX server as user "root" type 'service mgmt-vmware restart'
I will place this SR against the bug report and advise you of any updates.
also need a fix for this issue.
vm's randomly display vmtools as 'not running' after running VCB, since applying the mentioned patch.
will try the service mgmt-vmware restart workaround, as Virtual Machines StartUp/Shutdown state was already set to 'Disabled'.
We have this problem too.
When we see a VM that have lost its vmtools heartbeat there are different info retrieved by the VI client depending on how you connect to your host.
If we connect directly to the ESX host were the VM is located it report back as running with heartbeat, IP addr etc.
When we connect to VC it say tools not running.
We have a case opened regarding this and apparently there have been some people reporting about this problem before us.
(as early as 6th of february)
Vmware have also confirmed that this problem is moved into their bug database for further analysis.
However we have still not received any info when this problem may be solved.
After seeing all the updates on this thread it's clear that this issue is a cosmetic UI display issue on VI Client connected with VC server it doesn't happen on the VI client connected to the ESX server and there is no problem in the working of the VCB, all the VCB operations are successful.
So in summary there is no VCB functionality loss we see due to this cosmetic UI display issue.
Actually, there is loss of functionality.
Using vcbvmname to try and resolve a VM by IP for an example will fail when VC shows tools as not running.
At least one backup application (Netbackup) uses this in the backup process, and will fail the backup if it is unable to resolve the VM by IP.
there is most definately a loss in functionality.
VCB backups randomly fail for vm's with vmtool status of 'not running'.
as soon as i recycle the vmware-mgmt service of the host ESX server, they are able to succeed.
All the VCB tests that I have carried out after this patch have been successful with every possible method , using vm ip , vm name , vm uuid. I have run VCB in a loop multiple times and have not faced any issue.
P.S : If you think that the answer is helpful please consider rewarding points.
Same problem here:
Using VI Client and VC Server Build 119598 connected to ESX 3.5 143128
VMTools show as "Not Running", however my backups still function using VCB 1.5, Backup Exec 12.5 (all available Hotfixes) and BE Agent for VMWare.
Connecting to Remote Windows MMC shows the service as running, in VC it shows as "Not Running"
Connecting VI Client directly to ESX host shows VMTools as "OK".