On of the more common questions we hear is were using vCenter Server Heartbeat to protect vCenter Server but what about the database server?
Well good news if your using SQL Server with vCenter Server, you can also protect the SQL Server itself whether it is local to the vCenter Server (same server) or if it is on a separate (remote) server with the same vCenter Server Heartbeat license. Thats right a single vCenter Server Heartbeat license will provide Application, Operating System and Hardware level montoring, all with failover capabilities when using it to protect the vCenter server application as welll as the vCenter database SQL server, regardless of edition.
The current version of vCenter Server Heartbeat (v6.4) supports the following versions of SQL Server (x86/x64):
SQL Server 2005 SP1 and later
SQL Server 2008 including SP1 and later
SQL Server 2008 R2 SP1
More information can be found here: vCenter Server Heratbeat Release Notes
NOTE:
The vCenter Server Heartbeat solution does not support protection of Oracle, IBM DB2 or a SQL Server running Microsoft Cluster Services but can protect the vCenter Server application utilizing these separate backend database systems.
By default all SQL Server instances and databases will be protected however support will only be for the VMware vCenter Product Suite databases as it is unknown how third party applications will handle a vCenter Server Heartbeat failover of its database.