April 1, 2009 at 1:25 am
Hi,
we have 3node a/a/p clustered sql server 2005 EE on windows 2003.On node1,1 instance, on node3 4 instances and node2 is passive.
On node1,we have D,E,F,G drives in Group1 for default instance
on node3,we have H,I,J,K drives in Group1 for instance1
L,M,N,O drives in Group2 for instance2
P,Q,R,S drives in Group3 for instance3
T,U,V,W drives in Group4 for instance4.
Usually when we restart the node1 all the drives D,E,F,G should move to node2(we did not see any drives on node1) and
when we restart node3 all the drives H,I,J,K,L,M,N,O,P,Q,R,S,T,U,V,W should also move to node2(We did not see any drives on node3)
But in our case, when we restart the node3, all the drives starting from D to W are visible from Node1 and aslo on node2.Could you please explain me how to analyze this cluster health?
what are the things I need to diagnose?
April 2, 2009 at 8:33 am
If your cluster configuration is correct, more specifically the dependencies for each instance and the failover order I would next look at your storage subsystem. Examining the System and Application event logs should give some indication of potential issues. Also, you might need to examine the cluster.log file as well. I mentioned the storage subsystem since we have seen issues similar to yours on an active/passive clusters and some N+1 clusters as well. In our case Veritas was not wanting to give up disk volumes to the appropriate owner. This issues can usually be remedied by updated firmware and drivers for your HBAs.
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
April 2, 2009 at 9:55 am
Thank you,
Could you please tell me where can I found(path location) this cluster.log file?
thanks
April 2, 2009 at 6:45 pm
The recommended default path in Windows 2000 and later is %SystemRoot%\Cluster. For example, C:\WinNT\Cluster\Cluster.log.
MJ
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply