I am getting ready to install a new host into our vm cluster of 2 hosts running ESX 3.0.1 with all patches. Once I get the new host running, I need to vMotion the guests to the new host, remove an old host from the cluster and rebuild another new host on new hardware, then do the same for the third.
Should I install the new host servers with ESX 3.0.2, or install ESX 3.0.1 and upgrade to ESX 3.0.2 after I've rebuilt all the hosts on new hardware? Ultimately, I want to get all hosts to 3.0.2. I'm thinking if I can vMotion from ESX 3.0.1 to ESX 3.0.2 I am better off with a fresh build of 3.0.2 than an upgrade. Also, at what point should I upgrade VC?
Hello,
Either way should work, however if you install with 3.0.2 from the getgo you minimize reboots and down time.
You should upgrade VC first if you are install 3.0.2 on the new host. It is required in order to properly manage 3.0.2.
Backup your DB
Perform the VC Upgrade
Install new host,
add host to cluster
vMotion VMs to new host,
remove old host,
...
Best regards,
Edward
Hello,
Either way should work, however if you install with 3.0.2 from the getgo you minimize reboots and down time.
You should upgrade VC first if you are install 3.0.2 on the new host. It is required in order to properly manage 3.0.2.
Backup your DB
Perform the VC Upgrade
Install new host,
add host to cluster
vMotion VMs to new host,
remove old host,
...
Best regards,
Edward
I am getting ready to install four new hosts and I was planning on building them with 3.0.2 to get ahead of the game...
Thanks!
That is the direction I was leaning, but just wanted an outside opinion. I've got the new versions of VC and ESX downloading now.