VMware Cloud Community
zenking
Hot Shot
Hot Shot

Move from Windows vCenter to appliance

I've been putting off making this change. I know there are no migration tools to change from Windows vCenter to the appliance, but I need to find out what settings I need to document for the change. My plan:

- Run Update Mgr on all hosts

- Remove the hosts from the current vcenter

- Down the vcenter server

- Log into one of the hosts via the web client

- Deploy the vcenter appliance using the ova file

- Create the datacenter and clusters with the same names I had before (just to keep it simple; I know )

- Connect the hosts to the appropriate clusters

- Configure HA and DRS

I have the HA and DRS settings documented. Networking is configured on the host, so no need to document that, right? Am I missing anything, or does anyone see a problem with my plan?

Thanks.

VMWare Environment: vSphere 7.0, EQ PS6210 SANs, Dell R730 Hosts, dedicated Dell switches w/ separate vlans for vmotion and iscsi.
Tags (3)
Reply
0 Kudos
9 Replies
MauroBonder
VMware Employee
VMware Employee

Hi,

Check out - https://labs.vmware.com/flings/vcs-to-vcva-converter

*Please, don't forget the awarding points for "helpful" and/or "correct" answers. *Por favor, não esqueça de atribuir os pontos se a resposta foi útil ou resolveu o problema.* Thank you/Obrigado
zenking
Hot Shot
Hot Shot

Sorry, I should have mentioned that I checked out the fling before, but it isn't supported with the SQL Express db we're running.

But based on the fact that we don't have many hosts or user roles, I don't think it will be a huge deal to build from scratch. I just wanted to make sure my plan isn't missing any steps or that there isn't anything else that stands out as a bad idea.

Thanks.

VMWare Environment: vSphere 7.0, EQ PS6210 SANs, Dell R730 Hosts, dedicated Dell switches w/ separate vlans for vmotion and iscsi.
Reply
0 Kudos
MauroBonder
VMware Employee
VMware Employee

Yes, apparently your plan it's OK.

Do you use vSS (Standard Switch) or vDS (Distributed)?

*Please, don't forget the awarding points for "helpful" and/or "correct" answers. *Por favor, não esqueça de atribuir os pontos se a resposta foi útil ou resolveu o problema.* Thank you/Obrigado
Reply
0 Kudos
Johan77
Enthusiast
Enthusiast

Hi,

About to do the same thing.

Using vDS

Will be some problem then i guess?

Cheers

Johan

Reply
0 Kudos
zenking
Hot Shot
Hot Shot

Made the move last week and all went well. We're using standard switches (Mauro, sorry, didn't see your response). We left the old Windows vcenter up throughout the process. My biggest issue was that there wasn't enough room in /tmp on my hosts to install HA when I moved them over. On most hosts, I was able to remove files from /tmp and restart the management agents to make the host recognize the free space. One host wouldn't recognize the free space until I restarted it. If you remove files from tmp and verify free space first, that will ease the process.

- Make sure you have all of your license info for hosts and vcenter. This can be copied from the old vcenter licensing in the client.

- Install and configure vc appliance with new name and IP using 60 day evaluation license

( One thing to watch out for, although it was probably just me being stupid - After the installation, there is a web based configuration gui on port 5480 that uses root to log in. This is separate from the vcenter web client interface that runs on port 9443. The 9443 one uses the administrator account, so pay better attention to which gui you need to be in for various set tasks than I did.)

- Created new datacenters and clusters on appliance

- Logged into old vcenter and disconnected hosts, then removed them one at a time

- Added hosts to the clusters in the new vcenter. You'll get messages that the license is still in use on the old vcenter. They won't prevent you from adding the hosts, so ignore for now.

- Configured DRS and HA on new vcenter

After everything looked good on the new vcenter, I manually removed all of the license info from the old vcenter and then removed all vcenter components. However, we still use that Windows server for a few utility tasks and it still has the sql express db, so I reinstalled Update Manager and pointed to the new vcenter. I used the existing instance of the db but let it wipe out history. After that, I added the update mgr extension in the client and created new baselines for my hosts. All good.

Johan, Are you using AD?

VMWare Environment: vSphere 7.0, EQ PS6210 SANs, Dell R730 Hosts, dedicated Dell switches w/ separate vlans for vmotion and iscsi.
Reply
0 Kudos
Johan77
Enthusiast
Enthusiast

Hi,

Seems to have been a smooth ride Smiley Happy

No AD integration.

Due to the fact we are using vDS my question right now is if i should do a backup/restore of the vDS or if i simply should create a new vDS and then migrate my VMs.

Should be nice if this would be possible without downtime...

Cheers

Johan

Reply
0 Kudos
zenking
Hot Shot
Hot Shot

Did you see this KB? It has links with info on how to deal with changing vds to standard switches for the move, then restoring the vds. I haven't done that, but my impression is that it's easier to do now than it used to be.

VMware KB: Moving a managed ESXi/ESX host from one vCenter Server to another vCenter Server

VMWare Environment: vSphere 7.0, EQ PS6210 SANs, Dell R730 Hosts, dedicated Dell switches w/ separate vlans for vmotion and iscsi.
Reply
0 Kudos
Johan77
Enthusiast
Enthusiast

Thanks zenking, gonna check it out.

Cheers

Johan

Reply
0 Kudos
watchmen
Contributor
Contributor

Hello Zenking,

Did you used upgrade manager to upgrade to ESXi 6.0?

Did you had EVC enabled on the old cluster and disabled it at the new one?

Thanks,

Claudio

Reply
0 Kudos