doreski
Contributor
Contributor

2x vCenter Server Appliances

Hi All,

I am sorry if this comes across as a bit of a newbie question, however, I haven't been able to really find the answer to what I am trying to achieve, assuming its possible of course.

So, I'm not all that experienced with ESXI/vSphere/vCenter Server Appliance, however I am building up my knowledge thanks to work helping me setup a lab environment prior to possible deployment.

So, what I currently have is 2 hosts. (More possibly coming, but lets just start with the 2) Both hosts are physically in the same location. Both hosts are running ESXI 6.7. Both with numerous VM's running. 1 host is running vCenter Server appliance 6.7 and the other host.. well.. here in lay is my question. Ideally, what would be the 'ideal way' (a question that is obviously subjective I would assume) to have a vCenter Server appliance that looks after both hosts? What I would like to achieve is having a vCenter look after both hosts so that I may easily perform vmotion, put either host into maintenance mode and perform updates etc.

Would I be correct in assuming I could have 1 host running vCenter Server Appliance and then join the other host to the same SSO domain?

Thoughts and suggestions? Be gentle.. I bruise easy! Smiley Happy

Thanking you all in advance....

Reply
0 Kudos
IT_pilot
Expert
Expert

If you have a license, you can add both your hosts to vCenter, and migrate the vCenter Server Appliance between these hosts (if you have a shared vault).

SSO domain refers to multiple installations of vCenter and in your case it is not worth thinking about.

http://it-pilot.ru
imacfj
Enthusiast
Enthusiast

This is generally the setup that is used, and you can have up to 1000 hosts per vCenter server (although this is not best practice). vCenter is used for managing multiple hosts and is for exactly what you're trying to do

Usually you would only use more than 1 vCenter server appliances when trying to separate your virtual datacenters, or when your hosts are physically not in the same location

Reply
0 Kudos
doreski
Contributor
Contributor

Thanks everyone.

I did try migrating the vCenter Server to the 2nd host, and it did fail. I cant recall exactly why it failed. But.. with the new VCSA 6.7 setup i will give it a go.

I am away from my lab for the next week or so, but I will comment back once I have had a chance to attempt it.

Reply
0 Kudos
IT_pilot
Expert
Expert

Either you do not have a common storage or different generations of processors. The second is solved by the EVC setting.

http://it-pilot.ru
Reply
0 Kudos
doreski
Contributor
Contributor

Hi IT_Pilot,

Thats correct.. they are 2 different datastores.

Reply
0 Kudos
daphnissov
Immortal
Immortal

It sounds like the answer to your question is fairly straightforward. To quote:

So, what I currently have is 2 hosts. (More possibly coming, but lets just start with the 2) Both hosts are physically in the same location. Both hosts are running ESXI 6.7. Both with numerous VM's running. 1 host is running vCenter Server appliance 6.7 and the other host.. well.. here in lay is my question. Ideally, what would be the 'ideal way' (a question that is obviously subjective I would assume) to have a vCenter Server appliance that looks after both hosts? What I would like to achieve is having a vCenter look after both hosts so that I may easily perform vmotion, put either host into maintenance mode and perform updates etc.

If you have two ESXi hosts (nevermind what VMs each is running), you can join and manage both hosts to the same vCenter server. It doesn't make a difference that one host runs the vCSA VM and the other host has nothing (or something). You can either create a cluster and add both to a cluster, or add both separately as standalone hosts.

Reply
0 Kudos
doreski
Contributor
Contributor

Hi Daphnissov,

I see what you are saying.. i should add a little more context.
I have managed to add the 2nd host so that it is 'managed' by VCSA. Both hosts have 'independent datastores. They are not common.

I cant seem to migrate the VCSA across to the 2nd host, hence I cannot put host 1 into maintenance mode for updates etc..

This would be a requirement for me.

Reply
0 Kudos
daphnissov
Immortal
Immortal

In order to do that, you'll need to have vMotion configured and enabled. You'll have to also initiate a manual migration in which you choose the last radio button to move the storage and compute (doesn't matter which is first). vCenter will then orchestrate a storage vMotion to the second host's datastore, followed by a regular vMotion (of the compute profile) to that host. In the end, the vCSA should be running on the second node. If you still aren't able to do this, please share some screenshots of your attempt and any errors so we may diagnose from there.

IT_pilot
Expert
Expert

Indeed, you can migrate VM without a shared repository, but there are nuances.

You write "I can easily perform vmotion, put either host into maintenance mode and perform updates." In this case, you will need to move ALL VMs from one repository to another. But this can take a long time. In addition, with the simultaneous migration of vMotion and Storage Motion, there is a limit to two simultaneous migrations.

vMotion is enabled by setting a checkmark in the Management Interface

wpid-vmotion_vsphere6.png

http://it-pilot.ru
doreski
Contributor
Contributor

Thanks for all the suggestions guys.

As I am away from the lab for the next week, I will do it when I get back.

I will definitely post back and add screenshots should there be any issues.

Thanks again everyone!

Reply
0 Kudos