Upgrade vCenter v4.0 to v4.1

[ollie2001]

Afternoon all

Planning a vCenter upgrade from 4.0 to 4.1 and wondered if this is the best way to go about it (and quickest/easiest).

Currently vCenter lives on a Win2003R2 SP2 32bit server called PCC-VC01. I'm aware 4.1 needs a 64bit OS so was planning the following:

1. Take full backup of remote SQL 2008 DB

2. Turn off current vCenter Server

3. Delete AD computer account

4. Join new vCenter server under same name (PCC-VC01), OS Win2008R1 SP2 64bit

5. Install vCenter 4.0 (same version that was on previous vCenter server).

6. Point it to existing remote DB

7. Test all is well and everything works as expected

8. Upgrade vCenter on new vCenter server as per http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=102210... article

Would that sound the easiest way to cut over to vCenter 4.1?

Thanks all!

[Troy_Clavell]

if you are building a new Host OS, there is no need to install vCenter 4.0 then upgrade to 4.1 Just install 4.1. Make sure you create your 64bit DSN

[ollie2001]

Thanks for the quick reply. Will that update the remote SQL DB correctly? Or assume it's a new install and try to overwrite it?

[Troy_Clavell]

yes, it will make all the necessary schema updates on your DB instance. When installing vCenter after you've created and tested your ODBC connection, you can "use existing db", which will be in the drop down list.

Also, ensure you get all your sysprep files placed properly.

http://kb.vmware.com/kb/1005593

[ollie2001]

Thanks Troy! Sounds good. Takes 1 step out at least.

Thanks for the heads up about the sysprep files to, something I probably would have forgotten about until it came round to deploying a new VM

[Troy_Clavell · Accepted solution]

you're welcome. After you install of vCenter 4.1, you're inventory will come back just as it was prior to the upgrade.

One thing I do during upgrades is to turn DRS to 5 stars. What happens is sometimes the upgrade triggers a lot of DRS events because hosts are in in out of connection states due to the vCenter agent and HA agent upgrades. Once all hosts are happily connected in inventory, I usually go back to our 3 stars fully automated.

Good Luck!

[ollie2001]

Thanks for all that advice Troy. Much appreciated.

A couple of second opinions would be great before I take the plunge

[piaroa]

Hey ollie,

I'll be moving to vCenter 4.1 as well, from a physical Win32 server to a VM with Win64. The steps you outline are the same I plan on following, except installing 4.0 on the new vCenter, I'll go straight to vCenter 4.1.

I don't know if it's better to remove the hosts from the old vCenter before powering it off, or just power off and Add them to the new vCenter 4.1.

If this post has been helpful/solved your issue, please mark the thread and award points as you see fit. Thanks!

[ollie2001]

Thanks guys, all went as planned!

Only slight blip I had was the Update Manager didn't work properly after the upgrade. It wouldn't "scan" hosts anymore, did a bit of digging and found I had to wipe the Update Manager DB (essentially start from scratch) and that seemed to work!

All the points have been dished out...

Cheers