Groups | Blog | Home
all groups > sql server clustering > august 2007 >

sql server clustering : Connecting SQL Clustering from 2 different sites



Edwin vMierlo [MVP]
8/16/2007 12:00:00 AM
in-line

[quoted text, click to view]

your cluster IP in plant 2 is on the same subnet as your cluster IP in plant
1, are you sure you are tunneling/vlanning this subnet accross ? also you
made a typo above, please send us the correct settings. Furthermore, check
if your private network in plant 2, you might be mistakingly routing packets
there (do not use a Default GW on your private NIC's, you should only have 1
NIC with a default GW), as well as check subnetting of your private NIC's.

[quoted text, click to view]

SQL2005 supports logshipping, various forms of replication, as well as
database mirroring.... would that do what your want ?
If not give us more info on your requirements, or the package/software you
are planning of using

HTH,
Edwin.

Tom Moreau
8/16/2007 12:00:00 AM
They are on two different subnets. Plant 1 is on the 192.168.128 subnet and
Plant 2 is on the 192.168.2 subnet.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


"Edwin vMierlo [MVP]" <EdwinvMierlo@discussions.microsoft.com> wrote in
message news:unCXSN$3HHA.948@TK2MSFTNGP06.phx.gbl...
in-line

[quoted text, click to view]

your cluster IP in plant 2 is on the same subnet as your cluster IP in plant
1, are you sure you are tunneling/vlanning this subnet accross ? also you
made a typo above, please send us the correct settings. Furthermore, check
if your private network in plant 2, you might be mistakingly routing packets
there (do not use a Default GW on your private NIC's, you should only have 1
NIC with a default GW), as well as check subnetting of your private NIC's.

[quoted text, click to view]

SQL2005 supports logshipping, various forms of replication, as well as
database mirroring.... would that do what your want ?
If not give us more info on your requirements, or the package/software you
are planning of using

HTH,
Edwin.

Edwin vMierlo [MVP]
8/16/2007 12:00:00 AM
In that case, I suspect that packets are mis-routed due to 2 NIC's having
Default GW's configured.



[quoted text, click to view]

subscrib3 NO[at]SPAM gmail.com
8/16/2007 2:57:01 AM
Hi all.. hope someone can help me on this.. I'm a beginner and have
limited knowledge on clustering.

I managed to setup 2 set active/passive cluster with SQL clustering on
2 different site which is connected through lease line.

Plant 1:
Cluster IP : 192.168.128.150
SQL Cluster IP: 192.168.128.200 (VIRTUSQLS1)
Node1: 192.168.128.10
Node2: 192.168.128.11

Plant 2:
Cluster IP: 192.168.128.2.150
SQL Cluster IP: 192.168.2.200 (VIRTUALSQLS2)
Node1: 192.168.2.10
Node2: 192.168.2.11

A few questions here:

1. Why all nodes in Plant 2 can ping all the nodes/cluster/sqlcluster
in Plant 1 but Plant 2 can ping all nodes in Plant 1 except the
cluster/sqlcluster? There are 3 NIC in each node where there are
Gateways set in 2 of the NIC except for the heartbeat connection. Is
there anything to do with routing?

2. We have a software where we need to transfer data from SQL in Plant
2 to Plant 1 or vice versa. How do we define the Host? By the IP ( I
don't know how I can make the server in Plant 1 to recognise the name
VIRTUALSQLS2)?

Your help is very much appreaciated. Thanks


sw.yin

8/16/2007 5:19:12 AM
Sorry, it was a typo. The correct one should be:

Plant 1:
Cluster IP : 192.168.128.150
SQL Cluster IP: 192.168.128.200 (VIRTUSQLS1)
Node1: 192.168.128.10
Node2: 192.168.128.11


Plant 2:
Cluster IP: 192.168.2.150
SQL Cluster IP: 192.168.2.200 (VIRTUALSQLS2)
Node1: 192.168.2.10
Node2: 192.168.2.11

No, there is no Default Gateway set on the Private network only the
public network. I will double-check again on the subnetting.


2. I have our own customised software where it will do some processing
and transfer some data over from Plant 1 to Plant 2. In the software,
we definately need to define the Host or the SQL Server in Plant 2 in
order for me to access it. Do I connect it by IP or what must I do in
Plant 1 for it to recognize the name VIRTUALSQLS2?

Thanks all for the answer. I will do further checking and update
later.

--
sw.yin


On Aug 16, 6:50 pm, "Edwin vMierlo [MVP]"
[quoted text, click to view]


8/16/2007 5:25:52 AM
BTW, each node have 3 NICs. 1 NIC for the heartbeat connect with the
IP of 10.x.x.x. No Default GW defined here. The other 2 NIC is public
NIC with Default Gateway defined for both of it.

--
sw.yin

On Aug 16, 8:16 pm, "Edwin vMierlo [MVP]"
[quoted text, click to view]

Tom Moreau
8/16/2007 10:14:08 AM
Even though you have two public NICs on each server, we see only one IP per
node and per virtual SQL Server. How is the second NIC configured?

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau


[quoted text, click to view]
Sorry, it was a typo. The correct one should be:

Plant 1:
Cluster IP : 192.168.128.150
SQL Cluster IP: 192.168.128.200 (VIRTUSQLS1)
Node1: 192.168.128.10
Node2: 192.168.128.11


Plant 2:
Cluster IP: 192.168.2.150
SQL Cluster IP: 192.168.2.200 (VIRTUALSQLS2)
Node1: 192.168.2.10
Node2: 192.168.2.11

No, there is no Default Gateway set on the Private network only the
public network. I will double-check again on the subnetting.


2. I have our own customised software where it will do some processing
and transfer some data over from Plant 1 to Plant 2. In the software,
we definately need to define the Host or the SQL Server in Plant 2 in
order for me to access it. Do I connect it by IP or what must I do in
Plant 1 for it to recognize the name VIRTUALSQLS2?

Thanks all for the answer. I will do further checking and update
later.

--
sw.yin


On Aug 16, 6:50 pm, "Edwin vMierlo [MVP]"
[quoted text, click to view]

AddThis Social Bookmark Button