How can we set VMware hosts to be not fully managed by vCenter while still remaining connected to it?
How can we set our VMware hosts to be not fully managed by vCenter while still remaining connected to it? Here's the background:
We have a number of VMware ESXi hosts running v6.0 and v6.5. After we recently removed our last v5.1 host, we installed a new vCenter server appliance v6.7 to replace the existing v6.0 vCSA.
The problem comes with Altaro VM backup, which always backs up through vCenter if the host is connected to one. Despite saying that the versions we're using are supported (http://support.altaro.com/customer/en/portal/articles/808716-what-are-the-system-requirements-for-altaro-vm-backup-) in fact the combination of vCenter >= v6.5 and hosts v6.0 is not supported (http://support.altaro.com/customer/portal/articles/2949256).
Now Altaro support suggested that it's possible to work around this by setting the hosts to not be fully managed by vCenter. How do we do this?
The alternative is to downgrade the v6.5 hosts to v6.0 and use a v6.0 vCenter Server Appliance, which we'd rather not have to do as it means we can't use any hosts of v6.5 or later.
We have a number of VMware ESXi hosts running v6.0 and v6.5. After we recently removed our last v5.1 host, we installed a new vCenter server appliance v6.7 to replace the existing v6.0 vCSA.
The problem comes with Altaro VM backup, which always backs up through vCenter if the host is connected to one. Despite saying that the versions we're using are supported (http://support.altaro.com/customer/en/portal/articles/808716-what-are-the-system-requirements-for-altaro-vm-backup-) in fact the combination of vCenter >= v6.5 and hosts v6.0 is not supported (http://support.altaro.com/customer/portal/articles/2949256).
Now Altaro support suggested that it's possible to work around this by setting the hosts to not be fully managed by vCenter. How do we do this?
The alternative is to downgrade the v6.5 hosts to v6.0 and use a v6.0 vCenter Server Appliance, which we'd rather not have to do as it means we can't use any hosts of v6.5 or later.
ASKER
They are not supported by VMware, alas. They are PowerEdge R710 and ProLiant DL360 / 380 G7, which are only supported as far as v6.0 - otherwise yes, that's exactly what we would have done.
Okay, yes the support issue is a problem.
(you didn't mention the servers!).
I really do not know what Altaro are stating about "not fully managed".
either a ESXi host is connected to vCenter Server, or not connected, or removed. e.g. standalone and not connected/managed.
Unless they are discussing permissions ?
Did Altaro, not state this magic ?
(you didn't mention the servers!).
I really do not know what Altaro are stating about "not fully managed".
either a ESXi host is connected to vCenter Server, or not connected, or removed. e.g. standalone and not connected/managed.
Unless they are discussing permissions ?
Now Altaro support suggested that it's possible to work around this by setting the hosts to not be fully managed by vCenter. How do we do this?
Did Altaro, not state this magic ?
ASKER
Yes, sorry I missed out the information about the servers!
Well, that's sort of what I said to them - either it's in or it's not. I know that Veeam can connect either directly to the host or through vCenter, so I don't understand how this is different, but then I'm not a programmer. If you add a host in Altaro, and that host is attached to a vCenter, it prompts for the vCenter credentials and then always connects that way.
Altaro weren't able to give me a KB article, but said that one of their other customers had come up with a workaround by configuring the host settings so that (I wish I'd saved the chat transcript!) it was "not fully managed" (or words to that effect) by vCenter.
Of course, we could just detach the hosts from the vCenter and back them up directly - but that means we would have to manage them in the regular Web Client which is nowhere near as nice as the vCenter client, plus lose Update Manager and other functionality. I suppose we could just add them in and remove them as required, but that seems like a lot of unnecessary work.
Well, that's sort of what I said to them - either it's in or it's not. I know that Veeam can connect either directly to the host or through vCenter, so I don't understand how this is different, but then I'm not a programmer. If you add a host in Altaro, and that host is attached to a vCenter, it prompts for the vCenter credentials and then always connects that way.
Altaro weren't able to give me a KB article, but said that one of their other customers had come up with a workaround by configuring the host settings so that (I wish I'd saved the chat transcript!) it was "not fully managed" (or words to that effect) by vCenter.
Of course, we could just detach the hosts from the vCenter and back them up directly - but that means we would have to manage them in the regular Web Client which is nowhere near as nice as the vCenter client, plus lose Update Manager and other functionality. I suppose we could just add them in and remove them as required, but that seems like a lot of unnecessary work.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks, that's what I suspected! The plan (already in progress) is to downgrade the 6.5 host to 6.0 and use the vCenter 6.0.
which is fully supported by Altaro.