Which two options can be used for vCenter Server 6.x database availability? (Choose two.)

A.
NSX load balancer
B.
Microsoft SQL Server 2012/2014 AlwaysOn Availability Groups (AG)
C.
vCenter Server Watchdog
D.
vCenter Server Heartbeat
E.
Microsoft Windows Server Failover Clustering
Explanation:
https://kb.vmware.com/selfservice/microsites/search.do?
language=en_US&cmd=displayKC&externalId=1024051
may be B, E. Because they are looking for database availability.
B. Microsoft SQL Server 2012/2014 AlwaysOn Availability Groups (AG)
E. Microsoft Windows Server Failover Clustering
6
1
C and E is correct.
– As of vSphere 6.0, VMware introduced support for using Windows Server Failover Clustering or Microsoft Server Failover Clustering to protect a Windows-based vCenter Server.
– In vSphere 6.0, the vCenter Server Watchdog feature was introduced. vCenter Server Watchdog monitors and protects vCenter Server’s VPXD providing better availability by periodically checking the vCenter Server processes (PID Watchdog) or the vCenter Server API (API Watchdog).
– … third-party solutions are available to protect VMware vCenter Server 5.x and 6.0 … these solutions are not certified by VMware for use with vCenter Server to provide high availability … Microsoft SQL Server 2012/2014 AlwaysOn Availability Groups (AG), Microsoft SQL Server 2012/2014 AlwaysOn Failover Cluster Instance (FCI) & Microsoft SQL Server Database Mirroring
https://kb.vmware.com/s/article/1024051
1
8
C and E.
SQL is not suppoorted DB for vCenter (only Postgres and Oracle).
Oracle can be clustered using MSCS.
vCenter Server Heartbeat is not supported for vCenter 6.x
https://kb.vmware.com/s/article/1024051
2
6
Ok, rather B and E:
https://docs.vmware.com/en/VMware-vSphere/6.0/com.vmware.vsphere.install.doc/GUID-55F7FFDB-01B8-4C18-AA89-DC28BD9B1E9F.html
vCenter Server for Windows supports Oracle and Microsoft SQL database, while the vCenter Server Appliance supports only an Oracle database as an external database.
Watchdog is not for DB availability.
4
1
Agree with B and E
2
0
It seems the B is not correct:
https://blogs.vmware.com/vsphere/files/2015/05/INF4945_Potheri-vCenter_Server_Availability.pdf pag. 17
0
0
So what is it…?
0
0
I choose C and E
P.S. I think some answer may be wrong.
0
0
According to https://kb.vmware.com/selfservice/microsites/search.do?
language=en_US&cmd=displayKC&externalId=1024051
The answer should be B and E:
– Microsoft SQL Server 2012/2014 AlwaysOn Availability Groups (AG) -> certified support
– Microsoft Windows Server Failover Clustering -> with support but not certified
0
0
https://kb.vmware.com/s/article/1024051
100% positive B and E.
” …Microsoft SQL Server 2012/2014 AlwaysOn Availability Groups (AG) for high availability and disaster recovery solution (Non-shared disk configuration)
Microsoft SQL Server 2012/2014 AlwaysOn Failover Cluster Instance (FCI) for high availability, and Availability Groups (AG) for disaster recovery solution (Shared Disk Configuration)…”
0
0
D and E
MS SQL is not used in vcenter 6.x if you look at the list of requirements in https://kb.vmware.com/s/article/1024051 it clearly has these in the list:
vCenter Server Heartbeat
Microsoft Windows Server Failover Cluster
2
1
DE
https://kb.vmware.com/s/article/1024051
read the notes section
0
0
sorry i meant CE
As of vSphere 6.0, VMware introduced support for using Windows Server Failover Clustering or Microsoft Server Failover Clustering to protect a Windows-based vCenter Server. A transparent failover occurs if the Host Operating System (Host OS) running the Primary vCenter Server virtual machine fails, in which case the Secondary vCenter Server virtual machine is immediately activated to replace the failed virtual machine. WSFC/MSCS protection can only be used to protect the vCenter Server.
n vSphere 6.0, the vCenter Server Watchdog feature was introduced. vCenter Server Watchdog monitors and protects vCenter Server’s VPXD providing better availability by periodically checking the vCenter Server processes (PID Watchdog) or the vCenter Server API (API Watchdog). If the Watchdog service detects that APIs are not running or responding, the Watchdog attempts to restart the service two times; on the third attempt, depending on your configuration, the Watchdog can reboot the vCenter Server’s Host OS. For more information about the Watchdog, see Establishing Watchdog Support in the vCenter Server and Host Management Guide. Watchdog is enabled out of the box for vCenter Server 6.0. In vCenter Server 6.5, vCenter Server Watchdog is replaced by VMware Service Lifecycle Manager (vMon). For more information, see Protecting vCenter Server with VMware Service Lifecycle Manager in the vSphere Availability Guide.
0
0