Cluster Issue

Hello,
I have a Wndows 2003 Sql 2005 Cluster consisting of two servers, on Failover
from node2 to node1 the application user is unable to login until the sql
server is restarted, on failover all the resourses come online but the user
is unable to access the database and if I look in SQl Server management
studio I am unable to see the properties of the DB, if I initiate a failure
of SQL server in the cluster I am still unable to access the DB but if I
restart SQL server in management studio the database comes online.
Also when I do a failover to node2, it shows all resourses are online but
the application cannot access the DB like it is not there, but I can access
the Quorum and the shared DB drive.
Thanks in advance,
Bob Smith
Definitely a problem. Check the Application log on either node (Event
logging on a cluster is cluster-wide to each node) to see if SQL is
complaining about starting up.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Bob Smith" <BobSmith@.discussions.microsoft.com> wrote in message
news:F586AE13-D88E-4893-A6A3-0465392C13F2@.microsoft.com...
> Hello,
> I have a Wndows 2003 Sql 2005 Cluster consisting of two servers, on
> Failover
> from node2 to node1 the application user is unable to login until the sql
> server is restarted, on failover all the resourses come online but the
> user
> is unable to access the database and if I look in SQl Server management
> studio I am unable to see the properties of the DB, if I initiate a
> failure
> of SQL server in the cluster I am still unable to access the DB but if I
> restart SQL server in management studio the database comes online.
> Also when I do a failover to node2, it shows all resourses are online but
> the application cannot access the DB like it is not there, but I can
> access
> the Quorum and the shared DB drive.
> Thanks in advance,
> Bob Smith
|||Hi Geoff,
Thanks for the reply, the only thing I can see is logwriter errors, which I
googled and found more questions than answers, let me ask this: Can the
Quroum and the physical disk be in different groups or should the be in the
same, mine is set the the Quorum is in the Cluster group and the Physical
disk is in group 0. By the way I see these errors on both nodes. What is best
practice for the cluster group, what resourses should exist in it: Cluster
IP, Cluster Name, MSDTC -?, Quorum -?
Thanks again,
Bob Smith
"Geoff N. Hiten" wrote:

> Definitely a problem. Check the Application log on either node (Event
> logging on a cluster is cluster-wide to each node) to see if SQL is
> complaining about starting up.
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
>
> "Bob Smith" <BobSmith@.discussions.microsoft.com> wrote in message
> news:F586AE13-D88E-4893-A6A3-0465392C13F2@.microsoft.com...
>
|||Quorum must be in the cluster group. It is the reason the group exists.
The Quorum disk prevents split-brain problems. The Cluster group should
also have an IP Address and a Network Name Resource.
You can put the MSDTC resource in there too, but it can cause problems on
some very high volume systems.
All SQL resources should be in a different group. Note that disks are
physical resources. Logical OS partitions of the same disk cannot be split
into multiple groups.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Bob Smith" <BobSmith@.discussions.microsoft.com> wrote in message
news:1BD77D34-DC9D-4CB6-8325-9D32F50C9B58@.microsoft.com...[vbcol=seagreen]
> Hi Geoff,
> Thanks for the reply, the only thing I can see is logwriter errors, which
> I
> googled and found more questions than answers, let me ask this: Can the
> Quroum and the physical disk be in different groups or should the be in
> the
> same, mine is set the the Quorum is in the Cluster group and the Physical
> disk is in group 0. By the way I see these errors on both nodes. What is
> best
> practice for the cluster group, what resourses should exist in it: Cluster
> IP, Cluster Name, MSDTC -?, Quorum -?
> Thanks again,
> Bob Smith
> "Geoff N. Hiten" wrote:
|||Geoff,
Thanks, that is how it is setup Cluster group (Cluster IP, Cluster Name,
Disk Q and MSDTC) all other resourses are in another group, I am still
confused as too why SQL says it is online but the user/app cannot connect,
by restarting SQL server in studion management it comes online.
Thanks again,
Bob Smith
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:%23VBACR5VIHA.4140@.TK2MSFTNGP04.phx.gbl...
> Quorum must be in the cluster group. It is the reason the group exists.
> The Quorum disk prevents split-brain problems. The Cluster group should
> also have an IP Address and a Network Name Resource.
> You can put the MSDTC resource in there too, but it can cause problems on
> some very high volume systems.
> All SQL resources should be in a different group. Note that disks are
> physical resources. Logical OS partitions of the same disk cannot be
> split into multiple groups.
> --
> Geoff N. Hiten
> Senior SQL Infrastructure Consultant
> Microsoft SQL Server MVP
>
>
> "Bob Smith" <BobSmith@.discussions.microsoft.com> wrote in message
> news:1BD77D34-DC9D-4CB6-8325-9D32F50C9B58@.microsoft.com...
>
|||Maybe an IP address conflict or a dependency error. Again, the application
log should say something.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Bob Smith" <bob@.neconsulting.net> wrote in message
news:4E7A31CB-2900-4ED3-A7A9-1B0800B2128C@.microsoft.com...
> Geoff,
> Thanks, that is how it is setup Cluster group (Cluster IP, Cluster Name,
> Disk Q and MSDTC) all other resourses are in another group, I am still
> confused as too why SQL says it is online but the user/app cannot connect,
> by restarting SQL server in studion management it comes online.
> Thanks again,
> Bob Smith
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:%23VBACR5VIHA.4140@.TK2MSFTNGP04.phx.gbl...
>