Today I began my first phase of upgrading our 3.5u4 ESX environment in our Chicago office to 4.0. Upgrading vCenter is the first step. I would have preferred to create a whole new fresh install but decided I would upgrade and see if it came out ok. With snapshots and the like I always have the opportunity to go back. My next step is to change two of our hosts over to ESX 4.0 in a week or so and test it out for a couple of weeks before I fully vSphere-icize our environment. I am already fairly certain everything will be fine as I already have a 4.0 cluster going in our Zurich office. Here is a cut and paste of some braindumping I was doing into notepad as I was doing the upgrade:
upgraded memory on vCenter server from 1GB to 4GB
added a second processor to the vCenter Server
Seperate Database Server. Bumped Memory from 1GB to 3GB
Double checked all my SQL dbo perms
Made backup of the virtualcenter db
Disabled HA – Taking very long and sluggish then suddenly finished
Ran Upgrade on vCenter Server
Updating the client
re-enabled HA
Test Drove it a little bit to make sure it was performing properly
Uh oh… Trouble
Database server is cranked.. Have to give it a second CPU. Should have seen that coming
Now DB server is fine and virtual center server is cranked 100%.. lol
statsupdate eating cpu on DB server – working on it decided to service pack SQL server
Turned out to be this problem
Hmmmmm…. it appears even tho it states 2.5 this is still a bug in 4.0 and the fix works
In this version tho you have to drop the views before you create them.
Install new version of converter and update manager and tested to see if they worked.
All is running good now… Next phase re-install two of my hosts with ESX 4.0 and test for a few weeks before going all the way
Posts
No comments:
Post a Comment