Skip to main content

[RESOLVED] Mulitple vCenters

Thread needs solution

Hi,

I have two vSphere Essentials licenses and therefore have two vCenter servers. However it's only possible to add one vCenter server apparently. I can add the separate hosts but then it will complain about it being managed by a vCenter already and that I should add the vCenter instead.

Is there a way to fix this so I can have two vCenters in my vmProtect 8?

Find the solution here.

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi PatricF,

Currently vmProtect infrastructure supports only 1 vCenter to be handled so in your case the options are:

1) Register inividual hosts in vmProtect and ignore that warning. The warning just means that vmProtect won't be able to handle situations where VMs are migrated via vMotion between hosts managed by vCenter, however this is not a problem in your environment from what I can see.
2) Add both of your ESXi hosts into the same vCenter and register this vCenter.
3) Deploy 2 vmProtect appliances so that each manages its own 1 vCenter.

Usually vCenter makes sense when you have more than 1 ESX(i) hosts to be managed and it is intended to handle multiple hosts. Can you please clarify if there is some special reason for why you have 2 vCenters where (if I correctly understood) each vCenter manages only 1 host? I believe that 1 vCenter will be more than enough in your case.

Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager

Each vCenter manage 3 hosts as we are running vSphere Essentials license and can't really afford to buy a Standard and vCenter license as it would be way to expensive. So we bought two Essentials licenses so we could manage our six hosts.
For the same price of one Standard license per CPU we get two Essentials license with support for total of 12 CPU's, the only downside is that we have two vCenters.

That's the reason we have two vCenters. I guess we can add the 3 other hosts to vmProtect if the error is only about vmotion, as we can't use vmotion anyway.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi PatricF,

Thank you for the clarifications. I believe that it would make sense to go with option 3, i.e. deploy 2 vmProtect appliances to different hosts - one under 1st vCenter and another under 2nd vCenter. This would let you get the best performance since each vmProtect appliance will be able to attach the virtual disks to itself for direct access (assuming that there is some shared storage used on each of the vCenters), while with 1 appliance the disks from remote vCenter will be read over network which is slower. That's just a recommendation anyways (having 1 appliance managing all 6 hosts will also work, but will be slower). Hope it makes sense!

Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager