Showing results for 
Search instead for 
Did you mean: 
Level 6
Partner    VIP    Accredited

Today we are going to configure a basic scenario the SQL HA/DR.  Veritas Cluster Server HA/DR provide failover of applications and databases within a data center or to remote data centers. In the below activity we try to show the database failover to remote data center.


SQL Server version = 2005

OS = windows 2003 with SP2

SFHA/DR version = 5.0

Both Clusters have individual ISCSI SANs




"Two local clusters created"

First Cluster name = Cluster-pri

Second Cluster name = Cluster-sec

"Service Groups name"

SQL Service Group name = SQL

Replication Service Group name = REP

"Cluster-pri Nodes hostnames"



"Cluster-sec Node hostname"


"Global Cluster IP"

Global Cluster IP of Primary Site(Cluster-pri) =

Global Cluster IP of Secondary Site(Cluster-sec) =

"IP for Replication between Primary Site(Cluster-pri) and Secondary Site(Cluster-Sec)"

Replication IP of Primary Site(Cluster-pri) =

Replication IP of Secondary Site(Cluster-sec) =

"Replication Drive configuration"

Primary Site DATA Diskgroup (SAN Drive shared by both Nodes of Primary Site) name = SQL-DG

Primary Site DATA Drive(SAN Drive shared by both Nodes of Primary Site) name and size = SQL-DG-vol "800MB"

Primary Site SRL Drive(SAN Drive shared by both Nodes of Primary Site) name and size = SRL "500MB"


1.) Cluster Configuration Wizard

After installing the SFHA software run the Cluster Configuration Wizard on both Clusters(To create the Cluster) but at the end select the GCO option. See the first attachment for reference

2.) Create Replication Service Group and add IP and NIC resource

Create Replication Service Group and add IP and NIC resource. See second attachment for reference

3.) Create Replication

Create replication between Primary Cluster and Second Cluster using the VEA tool. See third attachment for reference

4.) Copy the VMDG resource to REP(Replication) Service Group

Copy the VMDG resource from SQL Service Group to the REP(Replication) Service Group and later/soon we will delete the VMDG resource from the SQL Service Group. See the fourth for reference

5.) Create vvrRVG resource for REP(Replication) Service Group

Create a resource name vvrRVG under the REP(Replication) Service Group. See the fifth attachment for reference

6.) Link the resources

Link the VMDG, vvrRVG, NIC, IP resource under the REP(Replication) Service Group. See the sixth attachment for reference

7.) Remove VMDG resource and add rvgPrimary

Remove the VMDG resource from the SQL Service Group and add the rvg Primary resource in SQL Service Group. See the seventh attachment for your reference

8.) Make dependency

Make dependency of SQL and REP(Replication) Service Group. See the eight attachment for reference.

9.) Test Local Cluster(Cluster-pri) switch over

Test the Local Cluster(Cluster-pri) switch over. See the ninth attachment for reference

10.) Add Remote Cluster

Add remote cluster so you will be able to switch over the Primary Site Clusters Service Group to the Secondary Site. See the tenth attachment for your reference

11.) Service Group Conversion

Convert the SQL Service Group to Global Service Group. The conversion of Service Group make the Service Group an ability to switch over Global means the SQL Service Group can be switch over from Cluster-pri to Cluster-sec. See the eleventh attachment for reference

12.) Test Remote Switch Over

Test the Remote/Global switch over. See the twelve attachment for your reference

13.) Configure Global HeartBeat

Now configure the Global HeartBeat so that both Clusters(Cluster-pri and Cluster-sec) know the state of each other. See the Thirteenth attachment for your reference 


Now we are able to switch over our SQL database within Primary Site and also to Remote Site. 

Version history
Last update:
‎03-10-2011 11:29 PM
Updated by: