What is not a supported method for increasing the availability of a vCenter Server virtual machine?
A.
vSphere High Availability
B.
vSphere Fault Tolerance
C.
vCenter Server Heartbeat
D.
Site Recovery Manager
Explanation:
What is not a supported method for increasing the availability of a vCenter Server virtual machine?
What is not a supported method for increasing the availability of a vCenter Server virtual machine?
A.
vSphere High Availability
B.
vSphere Fault Tolerance
C.
vCenter Server Heartbeat
D.
Site Recovery Manager
Explanation:
vCenter uses 2 (v)CPU’s, FT does NOT(at this time!) support VM’s wich use multiple vCPU’s.
http://blog.shiplett.org/making-vcenter-server-highly-available/
B?
All options are working ones, but the question states “supported method”. So if you run vCenter with one vCPU only, you can protect it with FT but it is not supported method as supporter requirement is two vCPU for the vCenter server. So right answer is B.
With vSphere 5.x editions, vCenter Heartbeat is the ONLY supported method.
As for requirements, a vCenter Server should Always be Multi CPU. Therefore FT cannot be used with 5.x edition.
Yes in vSphere 6.x it supported to go upto 4 vCPU’s. vCenter Heartbeat will not be sold anymore as a seperate product.
Conclusion for this version:
C.
vcenter server heartbeat is EOL on 2/6/2014 and cannot be sell after this date, the only alternative is HA, so for me the answer is A
sorry NOT supported method…I think it’s B
after fucking with this for 20 min, still don’t understand the evil nature of this fucking thing
B is correct. http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1024051
folie okienne slask
http://www.XquielQMVW.com/XquielQMVW