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

sql server clustering : SQL Server 2000 Cluster Manual Failover


mjb9999 NO[at]SPAM hotmail.com
3/30/2006 1:28:56 PM
I have a two-node SQL Server 2000 cluster running on Windows 2003 SP1.
I have two named instances running in active/passive mode. I have the
cluster resources set up in 4 groups. The first group contains the
cluster resources (cluster name, cluster ip, and the quorum disk), the
second group contains the MSDTC resources, and the remaining two groups
contain the resources for each of the SQL Server instances.

I've noticed that if I try to manually fail over one of the SQL Server
groups, only the Network Name, IP Address, and Physical Disk resources
will fail over. The SQL Server, SQL Server Agent, and the Full Text
Search resources will not fail over unless the MSDTC resources are
running on the node to which I'm trying to fail over. Restarting the
active node will fail all resources successfully, it's only when I try
to fail a single SQL Server group that things don't work. Is this
normal behavior? Does MSDTC need to be running on a node before I fail
over a SQL Server group?
Linchi Shea
3/31/2006 5:36:02 AM
[quoted text, click to view]

This does not make sense. Resource groups are the unit of failover. The
resources in a group either all go to the other node or they all stay on this
node. You can't have some resources in a group on one node and, at the same
time, have the other resoruces in the same group on a different node.

I'd doublecheck whether what you described is indeed the case.

Linchi

[quoted text, click to view]
mjb9999 NO[at]SPAM hotmail.com
3/31/2006 12:49:16 PM
I may not have been clear enough. You're right, it isn't that some
resources in the group fail over and others don't (so the group as a
whole doesn't actually fail over), but some of them come online where
the others will not. The SQL Server Network Name, IP Address, and
Physical Disk resources will come online in the second node, but the
SQL Server, SQL Server Agent, and Full Text resources won't come online
unless the MSDTC resource group is running on the node. If MSDTC is
not running on the new node, the group will attempt to fail over. The
3 resources that don't come online stay in a status of "Online
Pending". After trying to come online 3 times, the group will fail
back to the original node. Also, the following 2 errors show up in the
Application event log.

Event Type: Error
Event Source: MSSQL$SQL1
Event Category: (3)
Event ID: 17052
Date: 3/31/2006
Time: 12:31:36 PM
User: N/A
Computer: SQLNODE1
Description:
[sqsrvres] OnlineThread: Error 5b4 bringing resource online.


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 9c 42 00 40 01 00 00 00 =9CB.@....
0008: 0b 00 00 00 53 00 51 00 ....S.Q.
0010: 4c 00 53 00 45 00 52 00 L.S.E.R.
0018: 56 00 45 00 52 00 31 00 V.E.R.1.
0020: 00 00 00 00 00 00 ......


Event Type: Error
Event Source: MSSQL$SQL1
Event Category: (3)
Event ID: 17052
Date: 3/31/2006
Time: 12:31:36 PM
User: N/A
Computer: SQLNODE1
Description:
[sqsrvres] OnlineThread: ResUtilsStartResourceService failed (status
5b4)


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 9c 42 00 40 01 00 00 00 =9CB.@....
0008: 0b 00 00 00 53 00 51 00 ....S.Q.
0010: 4c 00 53 00 45 00 52 00 L.S.E.R.
0018: 56 00 45 00 52 00 31 00 V.E.R.1.
0020: 00 00 00 00 00 00 ......
Mehul
6/1/2006 5:52:02 PM
I am facing the same error, and was interested to know if anyone has a
resolution for the same ?

[quoted text, click to view]
AddThis Social Bookmark Button