VMware Cloud Community
mick01
Contributor
Contributor

vCenter heartbeat with SQL hosting other databases

Here is my scenario:

Site A: vCenter with a remote SQL server housing other application DBs

Site B:  vCenter with local SQL server

How do I best setup vCenter Heartbeat to support this config?  Should I utilize SQL mirrioring or is there a best practice to have a failover on a vCenter that is not an identical setup at the DR site (site B).

Any feedback is appreciated.

Thanks!

Tags (1)
Reply
0 Kudos
2 Replies
vJustinKing
Enthusiast
Enthusiast

with SQL hosting other application databases, it is not known how these applications will react with a heartbeat failover and so a best practice is too only host vCenter suite databases. With heartbeat, the target server is an identical copy of the production vCenter and so configurations will need to be the same.

In you scenairio, if you were to use heartbeat, you would have to treat the two vCenters as unique and apply heartbeat to site A and B putting both into a heartbeat active/passive pair. If you wanted to use site B as a target for site A (single vCenter management) the configurations would have to be the same.

Justin Justin King – Sr Technical Marketing Manager vCenter Server: Virtualization and Cloud Platform
Reply
0 Kudos
conramic
Contributor
Contributor

Could we please get some clarification as to what remote SQL installation methods are supported?  We just migrated from Oracle to SQL Server for Heartbeat, but we're having a rough time piecing together documentation on how the SQL portion works.  We have one shared MSSQL Server at our primary site that contains many databases - including our vCenter DB - and one database server at our DR site that was intended for Heartbeat but also contains our SRM vCenter database.  Are we expected to physically clone our DB server or is a non-identical setup supported?  If so, do we need a separate license for the cloned server?  In the event that our primary SQL Server goes down does Heartbeat simply update DNS to point to the cloned SQL Server?

Thanks for your help.

Reply
0 Kudos