VMware Cloud Community
jvillanuevamtz
Contributor
Contributor

Migration VCenter 5.0

Hi everybody

     I decided to install a brand new VCenter 5.0 insted of migrating from 4.0 to 5.0, the trail license key it's about to expired in the 5.0 since the 60 days are almost done.

    The way I am doing the migration it's to disconnect the Host, eliminated in the 4.0 and then add it in the 5.0, but there are still Hosts in the 4.0 since they are in a Cluster, what happend if I to the same thing with this hosts???, does it affect the Cluster???, they are production VM's so i want the run the minimal risk of affecting the users.

   Another thing i want it to do it's to turn down VCenter 4.0 and the just add the Hosts in to the VCenter 5.0, but i don't know if this would affect the VM's, since the Cluster unite the resources of the hosts that are in there.

0 Kudos
7 Replies
eeg3
Commander
Commander

The virtual machines will persist on the host once the host is disconnected, and will populate in to the new vCenter once connected to it. You will not have HA/DRS and other cluster-specific features during the move, but your virtual machines will not go down unless you power down the ESX host(s). Once attached to the new vCenter, you would want to put them back in a cluster.

I would recommend reading the Upgrade Guide and compatibility matrixes. For example, 4.0u2 is not compatible with 5.0, but is compatible with 5.0u1.

Blog: http://blog.eeg3.net
BharatR
Hot Shot
Hot Shot

Hi,

Another thing i want it to do it's to turn down VCenter 4.0 and the just add the Hosts in to the VCenter 5.0

Agree with eeg3 as the ESXi 4.0 Update 2 is not supported for use with vCenter Server 5.0. For more  information, see the VMware Product Interoperability Matrix.

Best regards, BharatR--VCP4-Certification #: 79230, If you find this information useful, please award points for "correct" or "helpful".
firestartah
Virtuoso
Virtuoso

Hi

Just remember that to remove a host from a cluster it has to be powered down and if you need all the virtual machines on there to remain powered up you will need to vmotion them off,power off the esx host, remove it from the cluster and then what i would recommend is readd the host but outsdie the cluster,vmotion the vm's back to the host and then disconnect the host. This way you won't lose any connectivity.

Also as mentioned check your compatibilities especially VMFS and that all your hosts are on the HCL for vSphere 5.

have a look at this link for the upgrading

If you found this or other information useful, please consider awarding points for "Correct" or "Helpful". Gregg http://thesaffageek.co.uk
0 Kudos
eeg3
Commander
Commander

You do not need to power down the host to move it: http://www.yellow-bricks.com/2009/04/17/the-basics-moving-hosts-from-one-vcenter-server-to-the-other...

Blog: http://blog.eeg3.net
0 Kudos
firestartah
Virtuoso
Virtuoso

True you can disable HA and DRS to get it out of the cluster  Smiley Happy I just do it that way for piece of mind in knowing that if there was a problem while i was doing the migrations that HA would still be available.

If you found this or other information useful, please consider awarding points for "Correct" or "Helpful". Gregg http://thesaffageek.co.uk
0 Kudos
jvillanuevamtz
Contributor
Contributor

Hi fire;

   The steps you said are the reason I leave the Clusters at the end, since my Infrastucture isn't that big but the VM are important and there are used 24 hrs a day i could not turn them down and all of my other ESX Host I have already migrated them or are not compliant to a live migraton (Vmotion) I had to seek for other choices

0 Kudos
jvillanuevamtz
Contributor
Contributor

Thank you very much egg3;

     This was the solution, i just disconnect the ESX Hosts and then removed them from inventory and the VM's, yes the HA/Cluster was not available at the time I did this migration, but it was worth it since there was no down time in my machines.

     When migrating host's to an already created Cluster, I choose to generate a "granted from 192.168.1.XX" to keep the Resource Pools in the Host's, then moved manually the VM's  to their respective RP.

     Thank you very much to you all....

0 Kudos