VMware Cloud Community
DMoss57
Contributor
Contributor
Jump to solution

Ripping a 4.1 Host into a new 5.5 Cluster WITHOUT access to the 4.1 vCenter Server

I have a customer that has his 2 vSphere 4.1 hosts in a vCenter 4.1 cluster that is NOT under his control or access. vCenter server access is with a 3rd party he is nervous about his account being taken over by a new provider. I am looking for the safest method (preferable non-disruptive) to import these 2 hosts into a brand new vSphere 5.5 cluster with 2 new hosts and vCenter 5.5 server. He does have access to the individual hosts through the vSphere Client as well as his local NAS based storage where the VM's reside. The end result is to vMotion and Storage vMotion the VM's onto the new hosts and new storage non-disruptively then retire the old hosts.

Reply
0 Kudos
1 Solution

Accepted Solutions
vThinkBeyondVM
VMware Employee
VMware Employee
Jump to solution

This is possible without any downtime to the VM. However, as you are going to deploy new fresh vCenter again, you will have to configure HA/DRS settings again. Also, Since you do not have control on old vCenter, performance data from old vCenter you may not get as well. If you do not bother about performance data, you are good to go.

Here is how you can do this migration:

1. Deploy new vCenter: For your requirement : vCenter appliance will work just fine: Refer:http://www.virten.net/2013/09/vmware-vcenter-server-appliance-5-5-vcsa-limitations/

2.Create the cluster on new vCenter, configure the same.  first add your new ESXi host 5.5 into cluster. Make sure shared storage on old ESXi host is visible on new host as well. If it is not possible, you can perform vMotion without shared storage as well. Refer:VMware vSphere 5.1

3. Now you can add your old host into new cluster, make sure vMotion requirement are configured already :

vSphere 5.5 Documentation Center

4. Add your old host to new cluster. once you add these ESXi host in new vCenter, both will be disconnected automatically from old vCenter. if your hosts CPUs are different, you will have to enable EVC: Make sure you understand impact of EVC, configuring the same.

Refer: VMware vSphere 5.1

VMware KB: Enhanced vMotion Compatibility (EVC) processor support

VMware KB: EVC and CPU Compatibility FAQ

VMware KB: Enabling EVC on a cluster when vCenter Server is running in a virtual machine

5. you can migrate your old host VMs to new host, once migration is over, you can keep your old host into maintenance mode, and remove the same.


----------------------------------------------------------------
Thanks & Regards
Vikas, VCP70, MCTS on AD, SCJP6.0, VCF, vSphere with Tanzu specialist.
https://vThinkBeyondVM.com/about
-----------------------------------------------------------------
Disclaimer: Any views or opinions expressed here are strictly my own. I am solely responsible for all content published here. Content published here is not read, reviewed or approved in advance by VMware and does not necessarily represent or reflect the views or opinions of VMware.

View solution in original post

Reply
0 Kudos
3 Replies
vThinkBeyondVM
VMware Employee
VMware Employee
Jump to solution

This is possible without any downtime to the VM. However, as you are going to deploy new fresh vCenter again, you will have to configure HA/DRS settings again. Also, Since you do not have control on old vCenter, performance data from old vCenter you may not get as well. If you do not bother about performance data, you are good to go.

Here is how you can do this migration:

1. Deploy new vCenter: For your requirement : vCenter appliance will work just fine: Refer:http://www.virten.net/2013/09/vmware-vcenter-server-appliance-5-5-vcsa-limitations/

2.Create the cluster on new vCenter, configure the same.  first add your new ESXi host 5.5 into cluster. Make sure shared storage on old ESXi host is visible on new host as well. If it is not possible, you can perform vMotion without shared storage as well. Refer:VMware vSphere 5.1

3. Now you can add your old host into new cluster, make sure vMotion requirement are configured already :

vSphere 5.5 Documentation Center

4. Add your old host to new cluster. once you add these ESXi host in new vCenter, both will be disconnected automatically from old vCenter. if your hosts CPUs are different, you will have to enable EVC: Make sure you understand impact of EVC, configuring the same.

Refer: VMware vSphere 5.1

VMware KB: Enhanced vMotion Compatibility (EVC) processor support

VMware KB: EVC and CPU Compatibility FAQ

VMware KB: Enabling EVC on a cluster when vCenter Server is running in a virtual machine

5. you can migrate your old host VMs to new host, once migration is over, you can keep your old host into maintenance mode, and remove the same.


----------------------------------------------------------------
Thanks & Regards
Vikas, VCP70, MCTS on AD, SCJP6.0, VCF, vSphere with Tanzu specialist.
https://vThinkBeyondVM.com/about
-----------------------------------------------------------------
Disclaimer: Any views or opinions expressed here are strictly my own. I am solely responsible for all content published here. Content published here is not read, reviewed or approved in advance by VMware and does not necessarily represent or reflect the views or opinions of VMware.

Reply
0 Kudos
DMoss57
Contributor
Contributor
Jump to solution

Vikas,

So the bottom line is that I will not have any resistance from the 4.1 vCenter control. The Host will come over the the 5.5 side without issue or resistance, then?

Thanks for the other links as well. The old servers SuperMicro's and the new are UCS 220 M3's, so I am likely to have to enable EVC to execute the vMotion I need.

Nice write-up and I appreciate the quick response.

DM

Reply
0 Kudos
vThinkBeyondVM
VMware Employee
VMware Employee
Jump to solution

Yes, as I said, once you straightway add your ESXi host to new vCenter, it will give you one warning as shown in below snapshot:

Adding host to anotherVC.png

If you continue above UI workflow, ESXi host will be disconnected from older vCenter automatically.

Other way of doing the same is as follows:This is recommended way:

1. First set your DRS in manual mode, disable HA on older cluster.(old vCenter): But if same cluster has other ESXi host those you are not moving /owning, then this step need to be skipped as it will have impact on VMs on other hostss (due to HA disablement)

2. Disconnect ESXi from older vCenter.

3. Add the same ESXi host on new vcenter cluster.

But in your case, as you do not have control on older vcenter, first way is the only way you will have.

On EVC, as I already specified, please study well how EVC works & go ahead with the same.


----------------------------------------------------------------
Thanks & Regards
Vikas, VCP70, MCTS on AD, SCJP6.0, VCF, vSphere with Tanzu specialist.
https://vThinkBeyondVM.com/about
-----------------------------------------------------------------
Disclaimer: Any views or opinions expressed here are strictly my own. I am solely responsible for all content published here. Content published here is not read, reviewed or approved in advance by VMware and does not necessarily represent or reflect the views or opinions of VMware.

Reply
0 Kudos