ESX 3.5 Update 5 to vSphere 5 Upgrade Path

[PezzenteInglese]

Using the Virtual Center 5 and the Vmware Update Manager inside, is it possible perform an upgrade implace from ESX 3.5 to ESX 5.0?

If not could someone explain to me which are the steps that are required for that?

Regards

Andrea

[AWo]

Check that link: http://www.vmware.com/products/vsphere/upgrade-center/resources.html

AWo

[sjwk]

Do any of those resources actually cover direct migration from ESX3.5 infrastructure to ESXi5?  They seem to be migration guides from ESX3.5 to ESXi4.

Are you indicating that it is the same process, but just using vSphere 5 instead of vSphere 4?  Or are you saying that you can only go from ESX3.5 to vSphere 4, and then to vSphere 5?

I'm in the same position - we stuck with 3.5 previously due to lack of time and concerns with the new version at that time, but do have maintenance so can upgrade to 5 (doesn't really seem worth going to 4 now!)

Steve.

[PezzenteInglese]

I'm in the same condition of Steve.

Exist, or not, a direct migration/upgrade path from ESX 3.5 to ESXi 5?

The VirtualCenter5 can manage which type of ESX version?

Kind regards

Andrea

[MauroBonder]

Hello,

To migrate from ESX to ESX(i), you need do a fresh installation.

Follow versions that vcenter 5.0 supports to manage

	Platform	VMware ESXi 5.0	VMware ESX/ESXi 4.1 U1	VMware ESX/ESXi 4.1	VMware ESX/ESXi 4.0 U3	VMware ESX/ESXi 4.0 U2	VMware ESX/ESXi 4.0 U1	VMware ESX/ESXi 4.0	VMware ESX/ESXi 3.5 U5	VMware ESX/ESXi 3.0.3 U1
	VMware vCenter Server 5.0

http://partnerweb.vmware.com/comp_guide/sim/interop_matrix.php

Please, don't forget the awarding points for "helpful" and/or "correct" answers. 

Mauro Bonder - Moderator

[PezzenteInglese]

Hi Mauro,

you are saying that I can't use the VMware Update Manager to upgrade the ESX 3.5 Update 5 to vSphere 5?

Do i Have to reinstall the VMware Host from scratch?

Kind regards

Andrea

[a_p_]

You will find the supported upgrade option in the Upgrade Guide (http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-50-upgrade...) at page 78. A direct upgrade from v3.5 is not possible. Going from v3.5 to v4.x and then to v5.0 depends on the partition layout. So IMO - at least with shared storage - it's easier to do a clean installation rather than upgrading.

Before upgrading, make sure the hardware is supported and consider to run a firmware upgrade.

André

PS: Also make sure you read the Release Notes http://www.vmware.com/support/vsphere5/doc/vsphere-esx-vcenter-server-50-release-notes.html

[MauroBonder]

Check http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-50-upgrade...

Page 70.

i´m preffer do a fresh installation.

[Eildon]

Hello,

I am slightly late to the party with this question, but here goes.

I am in the same position (v3.5 -> v5)

We are also planning to add another host

Have read in release notes vCenter Server 5.0 can manage ESXi 5.0 hosts in the same cluster with ESX/ESXi 4.x and ESX/ESXi 3.5 hosts.

Would you agree these would be the best steps for me:

- upgrade my virtual center 2.5 server to vCenter 5

- fresh install of v5 onto new host and add host to cluster

- have 2 existing hosts. Remove host 1 and fresh install of v5 and add back to cluster

- remove host 2 and fresh install of v5 and add back to cluster

????

Many thanks in advance

Steve

[a_p_]

Steve,

that sounds ok, some thoughts though. Before you start, make sure the hardware is supported for ESXi 5.0 and with re-installing the hosts consider to upgrade their firmware.

- upgrade my virtual center 2.5 server to vCenter 5

This could be quite some work, since vCenter 5 also requires a 64-bit version of Windows Server 2003 or 2008 (or the vCenter Server Appliance). I would probably do a fresh install of vCenter Server. Also don't forget that the 3.5 hosts still require the license server. Either leave the old license server online until you are done with upgrading or install it on the new vCenter Server.

André

[Eildon]

Hi André thanks for the reply, much appreciated.

I am thinking I may install vCenter 5 on another server temporarily (x64) and will leave v3.5 (and license server) on my existing server.Then get my hosts up to 5. Format my my old 3.5 virtual center server, install x64 OS and then install 5. Then tidy up the temp server.

Am I right in saying the licensing is held on the hosts now in the new version?

Cheers again,

Steve

[PezzenteInglese]

You need to have a license service for the ESX 3.5... I don't know if you can move on the Virtual Center 5 servers that is 64 bit, you should I think. (You have to export the license.dic

Virtual Center 5 can manage the licensing only for the vSphere 4 and 5. Its enought that you turn of the old. VC after the vSphere reinstallation of all the host that have to be migrated!

Kind regards

Andrea

• SENT FROM BLACKBERRY****

[Eildon]

Hi Andrea,

Thanks for replying.

Are you saying I could not run both at the same time? ....... virtual center 3.5 on the existing server (along with License server etc) and vCenter 5 on another server?

I would leave the database on the existing server and once I had my hosts set up I would move the DB to the new Vcenter server, then tidy up my old server etc (install x64, then vcenter 5), then move it back again.

By the way, I go this from the Release Notes:

• vCenter Server 5.0 can manage ESXi 5.0 hosts in the same cluster with ESX/ESXi 4.x and ESX/ESXi 3.5 hosts. It can also manage ESX/ESXi 3.5 hosts in the same cluster with ESX/ESXi 4.x hosts. vCenter Server 5.0 cannot manage ESX 2.x or 3.0.x hosts.
  

Cheers

Steve

[PezzenteInglese]

Virtual Center for 3.5 is nor required.

Virtual Center 5 can manage the 3.5

But you need to have a license service for the 3.5 because the VC 5 can't manage the ESX 3.5 licensing

Regards

Andrea

• SENT FROM BLACKBERRY****

[Eildon]

I get what you meant now, thanks for that

Steve

[esx_support]

[guardguy]

Installed 5 over 3.5 in a test VM environment with no issue but haven't been able to test on an HP server.  Anyone else been able to?   Reason why we have to install over is because VMs are running from local storage.