Hi Guys,
As i am reading the reference guide a few questions are poping out.
If i have a remote SQL server acting as the SQL server for my vc instance what is the best way to set this up in a WAN environment with vCenter Heartbeat?
Thanks
Dougie
Process is the same as if you were protecting vcenter over a WAN with heartbeat. If you have different IP's for primary/secondary, then you use the WAN option, and provide the IPs as required during the install. The only difference is that you select the SQL option during the wizard for primary and secondary installation.
vExpert
VMware Communities Moderator
vmwise.com / @vmwise
-KjB
Process is the same as if you were protecting vcenter over a WAN with heartbeat. If you have different IP's for primary/secondary, then you use the WAN option, and provide the IPs as required during the install. The only difference is that you select the SQL option during the wizard for primary and secondary installation.
vExpert
VMware Communities Moderator
vmwise.com / @vmwise
-KjB
cheers,
The second part of the question was in a WAN environment if you have a remote SQL server do you need to clone the SQL server as well?
Just trying to understand how the vc backend works when it is remote from VC in thi scenario.
Thanks
Dougie
Hi Dougie,
Did you ever happen to figure out the answer to your question? We're in the process of implementing Heartbeat and can't find any explicit instructions that tell us to physically clone our remote MSSQL server. We have other DBs running on it and don't really want to go down the road of cloning everything on that box.
If so, will we need a second SQL license as well for the cloned server?
Thanks for any help you can offer!
Mike
you can use heartbeat on a separate standalon SQL server, the installation is exactly the same as protecting vCenter but selecting SQL only. You will need to clone the server, you can clone locally and manually transfer image or select the install clone which will only clone the apps and identity, the data will be synchronized when replication starts. If you have other non vCenter related databases, these will also be replicated however it is not known how the applications using these non vCenter databases will handle a heartbeat failover and thus be unsupported.
In short, Heartbeat will support a failover of a standalone SQL server (standard or enterprise) with the vCenter suite databases only (including VMware plugin databases)
I ended up playing about with this.
As vJustinKing mentioned set this up as a SQL standalone setup.
Regards
Dougie
