Groups | Blog | Home
all groups > sql server clustering > december 2006 >

sql server clustering : Move from active/passive cluster to active/active


hiddo.vanloon NO[at]SPAM gmail.com
12/18/2006 5:46:53 AM
Hi,

sorry for my lack of knowledge on this issue..

I've installed a Windows 2003 Cluster with SQL 2005. Works like a charm
when i do a failover.

Now i want to make this cluster active/active (multi instance) so no
connection is lost when a node goes down, but can't find any info on
how this need to be done. Can anyone help me out here..?!

Thanx in advance!
hiddo.vanloon NO[at]SPAM gmail.com
12/18/2006 5:57:46 AM
a Network Load balanced cluster is something then a multi instance
cluster right?!

hiddo.vanloon@gmail.com schreef:

[quoted text, click to view]
hiddo.vanloon NO[at]SPAM gmail.com
12/18/2006 6:36:05 AM
Edwin,

Thanx for your support! It's become more clear to me now...

Nog 1 vraag ... : )

Hoe verwijder ik een Windows 2003 cluster in z'n geheel. Ik draai (voor
test) een 2-node W2k3/SQL2k5 cluster en deze wil ik dus in z'n geheel
verwijderen.
Wanneer ik op de eerst node 'take offline' kies en vervolgens Evict
Node gaat dit goed, alleen bij de 2de node krijg ik RPC errors
(waarschijnlijk omdat hierop het virtuele cluster ip nog draait..)

Gr,
Hiddo


Edwin vMierlo schreef:

[quoted text, click to view]
Edwin vMierlo
12/18/2006 1:53:59 PM
Hiddo,

"to make this cluster active/active (multi instance) so no connection is
lost when a node goes down"

When a cluster-group, or instance, moves from one node to another you do
loose your connection, as it offlines the group completely when moving.

Having a multi-instance, doesn't help, multi-instance is just another word
for having multiple virtual servers, they are still seperate in regards to
databases and connections. (e.g. if you have 2 instances, you can consider
them as being 2 different servers)

I do not think that your problem can be solved by server clustering.

HTH,
_Edwin.


[quoted text, click to view]

Edwin vMierlo
12/18/2006 2:09:39 PM
NLB is indeed different then failover clustering, however not really usable
with databases such as SQL.

You need to think of your requirements, and then match it to the right
technology option for SQL

Here are some links for reference:
(some are SQL2000, but still applicable for most part)

Failover Clustering
http://msdn2.microsoft.com/en-gb/library/ms189134.aspx

SQL Server 2000 Failover Clustering
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/failclus.mspx

Scaling Out SQL Server with Data Dependent Routing
http://www.microsoft.com/technet/prodtechnol/sql/2005/scddrtng.mspx

Federated SQL Server 2000 Servers
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_cs_4fw3.asp

Federated Database Servers
http://msdn2.microsoft.com/en-us/library/ms190381.aspx

Scaling out SQL 2005
http://msdn2.microsoft.com/en-us/library/aa479364.aspx



HTH,
Rgds,
Edwin.


[quoted text, click to view]

Edwin vMierlo
12/18/2006 3:08:19 PM
Hiddo,

Good practice is to keep posts in these newsgroups in english. This so
others can read the posts and possibly help themselves solving problems.

There are however some newsgroups for some topics in your native language,
they have the microsoft.public.nl..... prefix.

In regards to your question of fully removing a W2K3/SQL2K5 cluster,

first, remove SQL instances:
http://msdn2.microsoft.com/en-us/library/ms190438.aspx

then, remove the cluster:
http://support.microsoft.com/kb/282227



Good Luck !
Rgds,
Edwin.



[quoted text, click to view]

AddThis Social Bookmark Button