VMware Cloud Community
fgl
Enthusiast
Enthusiast

How long to update ESX host to U2 via update manager?

How long does it take to up a vSphere 4u1 host to 4u2 via the update manager? Reason I'm asking is that the task seems to get stuck at 33% for over an hour and when I login to the host and do a 'top' I see zero cpu usage. I've tried rebooting the host and cancelling and rebooting the vcenter server and each time it gets to 33% and just stays there forever. I've also tried just doing a 'stage' of the updates and same thing it just go to 33% and stays there for hours. I don't think this is normal as all previous updates I've done went fairly quick.

Reply
0 Kudos
4 Replies
krowczynski
Virtuoso
Virtuoso

Hi,

for the first host it was about 1,5 hours and the other hosts, gone quicker!!






MCP, VCP

MCP, VCP3 , VCP4
Reply
0 Kudos
JimKnopf99
Commander
Commander

hi,

check if all vm could Be Moved to an other Host.

That could also Be the reason for that.

Frank






If you find this information useful, please award points for "correct" or "helpful".

If you find this information useful, please award points for "correct" or "helpful".
Reply
0 Kudos
fgl
Enthusiast
Enthusiast

JimKnopf99, I always migrate off all VMs and put the host into maintenance mode first before I use update manager.

Krowczynski, 1.5 hours is a long time (it take me less time to build a new host from scratch) but I will try again before I leave work and see if it finishes when I return the next morning.

Reply
0 Kudos
lamw
Community Manager
Community Manager

I had just finished upgrading half my lab environment and it took slightly longer on ESX than on ESXi using VUM, but still < 1hr

Have you taken a look at /var/log/vmware/esxupdate.log to see where it's at in the process? One issue we hit when patching a large environment is if you stage the patches in advanced, there is a validation process that goes through the entire inventory to ensure both the consistency of the host and VMs.This was the case when remediating at the cluster level, it had to inventory the entire cluster before it would start patching. This was easily identifiable by logging on the VUM server and looking at the logs there as VUM itself was doing the processing, you may want to take a look there if it's happening to more than just this host.

=========================================================================

William Lam

VMware vExpert 2009,2010

VMware scripts and resources at:

Twitter: @lamw

Getting Started with the vMA (tips/tricks)

Getting Started with the vSphere SDK for Perl

VMware Code Central - Scripts/Sample code for Developers and Administrators

VMware Developer Community

If you find this information useful, please award points for "correct" or "helpful".

Reply
0 Kudos