Cluster testing

I need to setup a 2 node cluster for testing.
I have 2 identical servers running Win2k3, but I have a question about the
shared disk device.
For the shared disk can I use a NAS device, one that connects thru a cat5,
or do I need a device that uses scsi?
Remember this is for a short term test.
Thanks
SQL Clustering won't support NAS. SCSI would work, but why not try Virtual
Server 2005? That works great!
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"dutch" <dutch@.discussions.microsoft.com> wrote in message
news:2CCAEA46-6F5F-44D6-86A1-5BBAD07F8B18@.microsoft.com...
>I need to setup a 2 node cluster for testing.
> I have 2 identical servers running Win2k3, but I have a question about the
> shared disk device.
> For the shared disk can I use a NAS device, one that connects thru a cat5,
> or do I need a device that uses scsi?
> Remember this is for a short term test.
> Thanks
sqlsql

cluster sql2000 & DTC

on the passive node i tried to set range port for DTC
I tried using dcomcnfg, but when i reboot the node cannot join the cluster.
Why ?
thanks in advance.
Regards,
Dario
Review the NT event logs and cluster.log to get more details on why the node failed to join the cluster.
Best Regards,
Uttam Parui
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||DTC by deault will use any port ranges.
a registry hack can be done to limit it to certain range of ports.
"Dario Sala" wrote:

> on the passive node i tried to set range port for DTC
> I tried using dcomcnfg, but when i reboot the node cannot join the cluster.
> Why ?
> thanks in advance.
> Regards,
> Dario
>
>

Cluster SQL 7.0 in W2KAdv environment

Hi!
This is the scenario:
* Windows 2000 Advanced Server clustered with 2 nodes
After the installation of SQLServer in the first node, does not appear
the 'SQL Server Failover Cluster' or 'Failover Cluster Wizard' in the
program files menu, and the option 'MSDTC Administrative Control' is
in the menu but the file 'dac.exe' isn't installed.
I don't know which is the problem, because the MSDTC resource in the
cluster is on-line and managed by the firt node, after execute the
command comclust. I see the articles in Microsoft KB (290624, 243204,
), but I don't found a solutions. There are a special SQL 7.0 version
for clustering
Thanks!!
Are you sure you installed the Enterprise Edition?
Look at the SQL Server errorlog and verify that you installed the
Enterprise Edition. BAsed on what you are saying about the Failover Wizard
not being there I am thinking that you did not.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||I fix this problem by installing the Enterprise Edition (really stupid
), and now the Failover Wizard it's ok, but the 'MSDTC
Administrative Console' still not work. I don't know the reason why
don't install dac.exe. I'll try to install mdac2.8
Thanks for your post.
Regards,
Ren
rboyd@.onlinemicrosoft.com (Rand Boyd [MSFT]) wrote in message news:<CxzmcDlJEHA.4016@.cpmsftngxa10.phx.gbl>...
> Are you sure you installed the Enterprise Edition?
> Look at the SQL Server errorlog and verify that you installed the
> Enterprise Edition. BAsed on what you are saying about the Failover Wizard
> not being there I am thinking that you did not.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.

Cluster SQL 2000

My cu has the Win2003 Cluster 4 nodes with 1 Default and 3 Named instances
SQL 2000, each instance is on different node, we noticed that every
instances have configured with TCP port 1433.
Is it possible on Cluster?
Hello.K
Since SQL uses 1433 as the default port and each instance sounds like its
running on its own node, I would say yes?
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
"kersob" <lkm> wrote in message
news:ODcWDPdWEHA.3016@.tk2msftngp13.phx.gbl...
> My cu has the Win2003 Cluster 4 nodes with 1 Default and 3 Named instances
> SQL 2000, each instance is on different node, we noticed that every
> instances have configured with TCP port 1433.
> Is it possible on Cluster?
>
> Hello.K
>
|||Host nodes don't have anything to do with port numbers. Notice that each
SQL resource group (virtual server) has its own IP address and network name.
Therefore, you can have each instance on 1433 if you desire. HOWEVER, there
are some gotchas. If you are hoping to connect to VirtualServername rather
than VirtualServerName\InstanceName, it won't work with anything higher than
MDAC 2.6. Even if you put a named instance on 1433, the client library
'knows' it isn't the default instance. MDAC will report an error that you
are connecting to the wrong instance.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"kersob" <lkm> wrote in message
news:ODcWDPdWEHA.3016@.tk2msftngp13.phx.gbl...
> My cu has the Win2003 Cluster 4 nodes with 1 Default and 3 Named instances
> SQL 2000, each instance is on different node, we noticed that every
> instances have configured with TCP port 1433.
> Is it possible on Cluster?
>
> Hello.K
>

Cluster Setting Failure Stay On Same Node

What is the Cluster setting if the present node has 3 failures (default) to
stay on the same server node?
What is the Cluster setting if the present node has 3 failures (default) to
move to another server node?
Thanks,
Joe K.
If I understand you correctly, this type of behavior is specified in the
Advanced tab of the resource Properties dialog form. There, you can specify
whether the cluster service tries to restart a resource or simply lets the
resource to fail.
If you want the cluster service to restart the resource, then you must
specify whether the resource failure should affect the group that contains
the resource. If you want to failover the group when the resource fails,
check 'Affect the group', and specify the Threshold and Period values. These
values determine how many times the cluster service will restart the resource
before failover and the amount of time in which the threshold number of
restart attempts should take place.
Linchi
"Joe K." wrote:

> What is the Cluster setting if the present node has 3 failures (default) to
> stay on the same server node?
> What is the Cluster setting if the present node has 3 failures (default) to
> move to another server node?
> Thanks,
> Joe K.

Cluster Service remain on starting state after quorum log corrupti

Hi
I have a 2 node windows 2000 Cluster with a problem. I think the quorum log
became corrupted and now on both nodes the cluster service cannot start.
Without the cluster service running i cannot access any of the resources. On
the event viewer i have some error messages indicating that the quorum log is
corrupted, is there a way of getting the cluster service to start?
I already tried starting the service with the -noquerylogging parameter, the
service started and i could clear the old log from the quorum disk, but after
that i'm trying to restart the service and he just stays on starting state
indefinetly. Is there anything i can do to save my neck...because i noticed a
few minutes ago that bmy backups were not running properly.
Please help me out, i have to start cluster on the next 8 hours!!!!
Thanks a lot
My messenger is f_batista69@.hotmail.com
Hi
Look at
"To recover from a corrupted quorum log or quorum disk"
http://www.microsoft.com/windows2000...luad_pr_70.htm
and
http://support.microsoft.com/default...b;en-us;872970
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"francisco - Portugal" <francisco - Portugal@.discussions.microsoft.com>
wrote in message news:48441502-D241-488E-A26F-CB9E6C1F5FC3@.microsoft.com...
> Hi
> I have a 2 node windows 2000 Cluster with a problem. I think the quorum
> log
> became corrupted and now on both nodes the cluster service cannot start.
> Without the cluster service running i cannot access any of the resources.
> On
> the event viewer i have some error messages indicating that the quorum log
> is
> corrupted, is there a way of getting the cluster service to start?
> I already tried starting the service with the -noquerylogging parameter,
> the
> service started and i could clear the old log from the quorum disk, but
> after
> that i'm trying to restart the service and he just stays on starting state
> indefinetly. Is there anything i can do to save my neck...because i
> noticed a
> few minutes ago that bmy backups were not running properly.
> Please help me out, i have to start cluster on the next 8 hours!!!!
> Thanks a lot
> My messenger is f_batista69@.hotmail.com
>
|||Francisco
Have you tried this.
Power off one of the nodes.
On the remaining NODE start cluster service with -noquorumlogging
Delete Everything inside of the MSCS directory on the Quroum drive (I know
you stated you deleted the quolog.log file previously).
Stop the cluster service and then start it with the -resetquorumlog
If this works then stop the cluster service and start it normally. I have
seen quorum logs become so corrupt that resetquorumlog does not work this
usually fixes it. If this does not work I would recommend the following:
Reboot the only node that is powered up with the cluster service set to
manual.
Go to the command promp c:\Windows\Cluster\clussvc -debug >c:\debug.txt
cut and paste the output into the news groups.
Regards
CT
"francisco - Portugal" wrote:

> Hi
> I have a 2 node windows 2000 Cluster with a problem. I think the quorum log
> became corrupted and now on both nodes the cluster service cannot start.
> Without the cluster service running i cannot access any of the resources. On
> the event viewer i have some error messages indicating that the quorum log is
> corrupted, is there a way of getting the cluster service to start?
> I already tried starting the service with the -noquerylogging parameter, the
> service started and i could clear the old log from the quorum disk, but after
> that i'm trying to restart the service and he just stays on starting state
> indefinetly. Is there anything i can do to save my neck...because i noticed a
> few minutes ago that bmy backups were not running properly.
> Please help me out, i have to start cluster on the next 8 hours!!!!
> Thanks a lot
> My messenger is f_batista69@.hotmail.com
>
sqlsql

Cluster service fails

I'm not able to start the cluster service on the 2nd node of our cluster.
O/S is 2003, with SQL 2000. The 2nd node is passive, and appears to join the
cluster but then it terminates unexpectedly.
We've tried using the Administrator account to start the server, but with
the same results.
The cluster service is fine on node 1.
What can I try to do in order to get the service to start?
Thanks,
Chris
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:7FE6F3AD-B838-414C-B216-D0CC84AE28F0@.microsoft.com...
> I'm not able to start the cluster service on the 2nd node of our cluster.
> O/S is 2003, with SQL 2000. The 2nd node is passive, and appears to join
the
> cluster but then it terminates unexpectedly.
>
My guess is it's having trouble seeing the Quorum resource. Make sure it
can view all the resources.

> We've tried using the Administrator account to start the server, but with
> the same results.
> The cluster service is fine on node 1.
> What can I try to do in order to get the service to start?
> Thanks,
> Chris

Cluster Service

For a particular node, I stopped the cluster service. When I tried to start the service, I received an error stating that the cluster could not start due to logon failure.
Can I be pointed in the direction to resolve this?
That's because the password for the SQL Server service account does not
match the Windows password.
Mike
Principal Mentor
Solid Quality Learning
"More than just Training"
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com
|||This would indicate that the password for the account that the cluster
service starts under has been changed. Go to Administrative Tools -
Services and enter the correct password for the account that the cluster
service is starting under.
Rand
This posting is provided "as is" with no warranties and confers no rights.
sqlsql

Cluster server connection

Good day,
I have recently installed a 2 node cluster server with SQL 2000 SP3 in my
network. and have found out that users connect to the Virtual cluster server
inorder to receive SQL services but they get the replay for the physical
node that holds the SQL.
I was wondering if this configuration can be changed so that the SQL servers
answers back with the IP address of the virtual server and not the physical
cluster.
the problem is that im working with a Firewall and we would like to restrict
the number of IP address that we expose to the world.
Thanks in advance
Oren Zippori
This is one of the wierd but unavoidable artifacts of clustering. You will
have to expose the host computer's IP addresses through the firewall.
Personally, I like to run my database servers on an restricted segment, just
to minimize the impact of stuff like this.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Oren Zippori" <orenzp@.hotmail.com> wrote in message
news:eu17pHbwFHA.3548@.tk2msftngp13.phx.gbl...
> Good day,
> I have recently installed a 2 node cluster server with SQL 2000 SP3 in my
> network. and have found out that users connect to the Virtual cluster
> server inorder to receive SQL services but they get the replay for the
> physical node that holds the SQL.
> I was wondering if this configuration can be changed so that the SQL
> servers answers back with the IP address of the virtual server and not the
> physical cluster.
> the problem is that im working with a Firewall and we would like to
> restrict the number of IP address that we expose to the world.
> Thanks in advance
> Oren Zippori
>
|||Thanks for the information on this Geoff.
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:uNRVXAgwFHA.664@.tk2msftngp13.phx.gbl...
> This is one of the wierd but unavoidable artifacts of clustering. You
> will have to expose the host computer's IP addresses through the firewall.
> Personally, I like to run my database servers on an restricted segment,
> just to minimize the impact of stuff like this.
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "Oren Zippori" <orenzp@.hotmail.com> wrote in message
> news:eu17pHbwFHA.3548@.tk2msftngp13.phx.gbl...
>

Cluster resource could not be found.

After a reboot of one of my node I am currently receiving the following
message:
The disk associated with the cluster disk resource 'Disk T:' could not be
found. The expected signature of the disk was XXXXXXX. If the disk was
removed from the server cluster, the resource should be deleted. If the disk
was replaced, the resource must be deleted and created again in order to
bring the disk online. If the disk has not been removed or replaced, it may
be inaccessible at this time because it is reserved by another server cluster
node.
How can I create another GUID? Will the installation of the Windows SP1
create a new GUID?
Burley,
You are not lonely. I got the same problem on MSCS.
"Burley" wrote:

> After a reboot of one of my node I am currently receiving the following
> message:
> The disk associated with the cluster disk resource 'Disk T:' could not be
> found. The expected signature of the disk was XXXXXXX. If the disk was
> removed from the server cluster, the resource should be deleted. If the disk
> was replaced, the resource must be deleted and created again in order to
> bring the disk online. If the disk has not been removed or replaced, it may
> be inaccessible at this time because it is reserved by another server cluster
> node.
> How can I create another GUID? Will the installation of the Windows SP1
> create a new GUID?
|||Lemme guess, SCSI-based cluster?
Sometimes a SCSI-based cluster can have problems with one node blocking
access to the shared disk. This is most common during node startup and
especially common when two nodes are started up at the same time. Always
boot one node at a time in a SCSI cluster.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Burley" <Burley@.discussions.microsoft.com> wrote in message
news:591F9019-BCCB-49FD-A749-03267C6A4591@.microsoft.com...
> After a reboot of one of my node I am currently receiving the following
> message:
> The disk associated with the cluster disk resource 'Disk T:' could not be
> found. The expected signature of the disk was XXXXXXX. If the disk was
> removed from the server cluster, the resource should be deleted. If the
> disk
> was replaced, the resource must be deleted and created again in order to
> bring the disk online. If the disk has not been removed or replaced, it
> may
> be inaccessible at this time because it is reserved by another server
> cluster
> node.
> How can I create another GUID? Will the installation of the Windows SP1
> create a new GUID?
sqlsql

Cluster recovery from node failure

Cluster services gives the high availability needed - that is great.
But I have never seen any discussion about what happens when a node
fails - what do you do to get everything back to the active-passive
tandem.

I imagine there is not much difference in terms of recovery procedure
for either active or passive node. So I'm just going to make up a
scenario that we have encountered. The system hard drive (not the
shared disk) on primary node fails. Cluster fails over to the passive
node. Following are the problems I have at hand:
-After installing windows, I need to install driver and configure the
permission to access the SAN. There is no way I could do it since the
secondary node has exclusive access to the disks.
-Imagine I got that working, is there anyway to install SQL so SQL
would know this server used to be the primary node and attach the DB
and translog automatically
-Finally, there is no proper way to apply SQL 2000 service pack 3a.
Originally when the cluster was fully functional, the service pack was
applied to active node and that automatically upgrades passive node.
Now we have a machine without 3a and a machine with 3a already
installed. See any problem?

Consider all of the above as this one big question: What is a proper
procedure to restore a cluster when one of the node goes down? Whether
it's the active or passive node."gotdough" <praemonitus@.hotmail.com> wrote in message
news:1ad01306.0409120058.3df26726@.posting.google.c om...
> Cluster services gives the high availability needed - that is great.
> But I have never seen any discussion about what happens when a node
> fails - what do you do to get everything back to the active-passive
> tandem.
> I imagine there is not much difference in terms of recovery procedure
> for either active or passive node. So I'm just going to make up a
> scenario that we have encountered. The system hard drive (not the
> shared disk) on primary node fails. Cluster fails over to the passive
> node. Following are the problems I have at hand:
> -After installing windows, I need to install driver and configure the
> permission to access the SAN. There is no way I could do it since the
> secondary node has exclusive access to the disks.
> -Imagine I got that working, is there anyway to install SQL so SQL
> would know this server used to be the primary node and attach the DB
> and translog automatically
> -Finally, there is no proper way to apply SQL 2000 service pack 3a.
> Originally when the cluster was fully functional, the service pack was
> applied to active node and that automatically upgrades passive node.
> Now we have a machine without 3a and a machine with 3a already
> installed. See any problem?
> Consider all of the above as this one big question: What is a proper
> procedure to restore a cluster when one of the node goes down? Whether
> it's the active or passive node.

This KB article might help:

http://support.microsoft.com/defaul...0&Product=sql2k

You should probably also post this in microsoft.public.sqlserver.clustering
to see if you get a better response.

Simon

Cluster problem

An installation of sql2k5 sp2 to one node of a three node
active/active/active cluster has failed. It cannot proceed beyond the
beginning of the sql2k5 sp2 installation. It fails because it can't install
sqlsupport.msi. It seems to want to put the files in the wrong place.
We can't get the sp to install after a lot of trying and want to 1) fail the
instance the node normally hosts to a partner 2) disconnect the node from
the cluster heartbeat and public networks and 3) run a SQL de-install of the
problematic instance on the disconnected node to clear off SQL and then
reinstall it, bringing it up to SQL2K5 SP2 4) reconnect the node to the
network and 5) fail the instance on the partner node back.
I don't think this will work because during the de-install the add/remove
routine will ask to remove code from san drives it can't find because
they're no longer accessible to it, since it has been disconnected from the
network and SAN. I think a manual removal may be all that can work.
After the node has been reconnected, and SQL installation commenced I will
be asked to create a new instance, a local or clustered instance, neither of
which I want. Can I avoid this by running SQL Setup on the reconnected node
and asking to manage a virtual instance instead of installing a fresh one?
Will I need, at some point, to evict the disconnected node from the cluster?
I know on a previous occasion, I couldn't get the node, once evicted, to
rejoin. Once it's out, it's out for good, isn't it?
"Robert Hindla" <rhindla@.panix.com> wrote in message
news:C38733A0.1BA20%rhindla@.panix.com...
> An installation of sql2k5 sp2 to one node of a three node
> active/active/active cluster has failed. It cannot proceed beyond the
> beginning of the sql2k5 sp2 installation. It fails because it can't
> install
> sqlsupport.msi. It seems to want to put the files in the wrong place.
Are you installing the first instance or the second instance?
Russ Kaufmann
MVP - Windows Server - Clustering
ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp
The next ClusterHelp classes are:
Jan 18 - 31 in Denver
Mar 10- 13 in Denver
|||The virtual SQL instance I'm proposing to de-install and then re-configure
using the setup program in 'manage' mode (instead of 'setup' mode) is one of
two named instances. It isn't the default instance.
The default instance functions satisfactorily, but only after a lot of
backing and filling, such as returning the native client to RTM level and
then re-running the installation of the client tools.
On 12/17/07 1:25 PM, in article
351AA24D-A3AA-4812-9682-F36BAFB1BC14@.microsoft.com, "Russ Kaufmann [MVP]"
<russ@.clusterhelp.com> wrote:

> "Robert Hindla" <rhindla@.panix.com> wrote in message
> news:C38733A0.1BA20%rhindla@.panix.com...
> Are you installing the first instance or the second instance?
|||"Robert Hindla" <rhindla@.panix.com> wrote in message
news:C38DA216.1BACB%rhindla@.panix.com...
> The virtual SQL instance I'm proposing to de-install and then re-configure
> using the setup program in 'manage' mode (instead of 'setup' mode) is one
> of
> two named instances. It isn't the default instance.
> The default instance functions satisfactorily, but only after a lot of
> backing and filling, such as returning the native client to RTM level and
> then re-running the installation of the client tools.
So, it sounds to me like things are seriously hosed (to use a highly
technical term) with your cluster. I would consider a complete rebuild over
the holidays if it were me.
Russ Kaufmann
MVP - Windows Server - Clustering
ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp
The next ClusterHelp classes are:
Jan 18 - 31 in Denver
Mar 10- 13 in Denver

Cluster Node Tuning

Hi,
I have a 2 node failover cluster running SQL2000 EE with SP4. Each node has
8GB of RAM, and each node is the preferred owner of one of the two SQL Server
instances, each of which are AWE enabled and have min and max server memory
set to 3GB. PAE and /3GB switch are also enabled on each node. Storage is
via FC direct attached SAN. My question:
Under System Properties/Advanced/Performance Options:
1. Should I set Processor Scheduling to Programs or Background Services?
2. Should I set Memory Usage to Programs or System Cache?
Thank you!
John
1. Background Services
2. Programs
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"JT" <Jthayer@.online.nospam> wrote in message
news:F0EE0BDB-79DE-4E7D-BE5E-6D9F9DF95C5D@.microsoft.com...
> Hi,
> I have a 2 node failover cluster running SQL2000 EE with SP4. Each node
> has
> 8GB of RAM, and each node is the preferred owner of one of the two SQL
> Server
> instances, each of which are AWE enabled and have min and max server
> memory
> set to 3GB. PAE and /3GB switch are also enabled on each node. Storage
> is
> via FC direct attached SAN. My question:
> Under System Properties/Advanced/Performance Options:
> 1. Should I set Processor Scheduling to Programs or Background Services?
> 2. Should I set Memory Usage to Programs or System Cache?
> Thank you!
> --
> John
|||Thanks Mike. That's what I had.
John
"Mike Epprecht (SQL MVP)" wrote:

> 1. Background Services
> 2. Programs
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "JT" <Jthayer@.online.nospam> wrote in message
> news:F0EE0BDB-79DE-4E7D-BE5E-6D9F9DF95C5D@.microsoft.com...
>
>

Cluster Node Tuning

Hi,
I have a 2 node failover cluster running SQL2000 EE with SP4. Each node has
8GB of RAM, and each node is the preferred owner of one of the two SQL Server
instances, each of which are AWE enabled and have min and max server memory
set to 3GB. PAE and /3GB switch are also enabled on each node. Storage is
via FC direct attached SAN. My question:
Under System Properties/Advanced/Performance Options:
1. Should I set Processor Scheduling to Programs or Background Services?
2. Should I set Memory Usage to Programs or System Cache?
Thank you!
--
John1. Background Services
2. Programs
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"JT" <Jthayer@.online.nospam> wrote in message
news:F0EE0BDB-79DE-4E7D-BE5E-6D9F9DF95C5D@.microsoft.com...
> Hi,
> I have a 2 node failover cluster running SQL2000 EE with SP4. Each node
> has
> 8GB of RAM, and each node is the preferred owner of one of the two SQL
> Server
> instances, each of which are AWE enabled and have min and max server
> memory
> set to 3GB. PAE and /3GB switch are also enabled on each node. Storage
> is
> via FC direct attached SAN. My question:
> Under System Properties/Advanced/Performance Options:
> 1. Should I set Processor Scheduling to Programs or Background Services?
> 2. Should I set Memory Usage to Programs or System Cache?
> Thank you!
> --
> John|||Thanks Mike. That's what I had.
--
John
"Mike Epprecht (SQL MVP)" wrote:
> 1. Background Services
> 2. Programs
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "JT" <Jthayer@.online.nospam> wrote in message
> news:F0EE0BDB-79DE-4E7D-BE5E-6D9F9DF95C5D@.microsoft.com...
> > Hi,
> > I have a 2 node failover cluster running SQL2000 EE with SP4. Each node
> > has
> > 8GB of RAM, and each node is the preferred owner of one of the two SQL
> > Server
> > instances, each of which are AWE enabled and have min and max server
> > memory
> > set to 3GB. PAE and /3GB switch are also enabled on each node. Storage
> > is
> > via FC direct attached SAN. My question:
> > Under System Properties/Advanced/Performance Options:
> > 1. Should I set Processor Scheduling to Programs or Background Services?
> > 2. Should I set Memory Usage to Programs or System Cache?
> >
> > Thank you!
> > --
> > John
>
>

Cluster Node Tuning

Hi,
I have a 2 node failover cluster running SQL2000 EE with SP4. Each node has
8GB of RAM, and each node is the preferred owner of one of the two SQL Serve
r
instances, each of which are AWE enabled and have min and max server memory
set to 3GB. PAE and /3GB switch are also enabled on each node. Storage is
via FC direct attached SAN. My question:
Under System Properties/Advanced/Performance Options:
1. Should I set Processor Scheduling to Programs or Background Services?
2. Should I set Memory Usage to Programs or System Cache?
Thank you!
--
John1. Background Services
2. Programs
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"JT" <Jthayer@.online.nospam> wrote in message
news:F0EE0BDB-79DE-4E7D-BE5E-6D9F9DF95C5D@.microsoft.com...
> Hi,
> I have a 2 node failover cluster running SQL2000 EE with SP4. Each node
> has
> 8GB of RAM, and each node is the preferred owner of one of the two SQL
> Server
> instances, each of which are AWE enabled and have min and max server
> memory
> set to 3GB. PAE and /3GB switch are also enabled on each node. Storage
> is
> via FC direct attached SAN. My question:
> Under System Properties/Advanced/Performance Options:
> 1. Should I set Processor Scheduling to Programs or Background Services?
> 2. Should I set Memory Usage to Programs or System Cache?
> Thank you!
> --
> John|||Thanks Mike. That's what I had.
--
John
"Mike Epprecht (SQL MVP)" wrote:

> 1. Background Services
> 2. Programs
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "JT" <Jthayer@.online.nospam> wrote in message
> news:F0EE0BDB-79DE-4E7D-BE5E-6D9F9DF95C5D@.microsoft.com...
>
>

Cluster Node Communications

I just rebuilt a 2 node W2k/SQL2k cluster that resides in
a NT4 domain. The cluster itself seems to be working
fine, the website that runs off of the virtual SQL server
is running fine.
However, both nodes in the cluster are not able to
communicate with other machines in my 2 other
trusted/trusting domains. My other 2 domains are W2k
based domains. Prior to the rebuild there were no
communication problems accross domains.
If I try to browse to the nodes in Windows Explorer I get
the message "No logon servers currently available to
service your request" and if I try to logon to one of the
nodes at the console using my user name and domain, it
says the domain is unavailable.
Any assistance would be greatly appreciated.
Patrick G.
You can check a few things.
1. Make sure your domain trust(s) are still in place and functioning correctly. If you don't have the W2K support tools installed (ie in a prod environment), run dsa.msc and check that you can browse the remote domain and list groups and users in the rem
ote domain (eg attempt to add a global group from the remote domain to a local domain group - you can do this with committing the change).
2. Make sure the account you are using has a valid SQL Server login on the remote SQL Server (or your account is in the builtin admins group on the remote server - if the other domain are willing to trust you with local admins on the remote server or the
remote domain).
Are both domains in W2K native or do you have W2K and W2K3 forests in the mix?

Cluster manager hangs

We have two sql cluster nodes that works fine till lastweek. i can still move
the cluster goup manualy from the one node to the other. the problem is i
can't move the sqlgroup manualy to the other node. When i do that the sql
manager hangs and nothing happends till i reboot the node where the cluster
group is active than become the group active on the second node. The cluster
dont log anything in the event viewer or the clusterlog file that i cab use
to find the cause of this problem.
I need some help to solve this problem.
Thanks
From the context, by "cluster manager" and "sql manager", I take that you
meant "Cluster Administrator", and Cluster Administrator still reports the
state of the cluster properly, right? (e.g. you can view whether a group is
online and on which node the group is running, etc) In addition, the SQL
instance itself works fine, right?
I'd try to establish whether this is a Cluster Administrator tool problem or
the cluster/sql problem. Try tto move the SQL group using Cluster
Administrator on one of the nodes itself. Failing that, check to see whether
the cluster service works properly w.r.t. the SQL group. For instance, you
can deny the cluster service account access to the SQL instance, and this
will force the cluster service to bounce the SQL group between the nodes
(because its IsAlive check would fail) and eventually give up. If the cluster
does behave this way, I'd then focus on troubleshooting the Cluster
Adminitrator itself.
Linchi
"Saber" wrote:

> We have two sql cluster nodes that works fine till lastweek. i can still move
> the cluster goup manualy from the one node to the other. the problem is i
> can't move the sqlgroup manualy to the other node. When i do that the sql
> manager hangs and nothing happends till i reboot the node where the cluster
> group is active than become the group active on the second node. The cluster
> dont log anything in the event viewer or the clusterlog file that i cab use
> to find the cause of this problem.
> I need some help to solve this problem.
> Thanks
|||Hi Linchi,
Yes, i mean the cluster administrator. I have two clustergroups named "SQL
cluster group" running on Server1 and the "cluster group" running on
Server2. When i start the cluster administrator i can manualy move the
cluster group to server1 without problems. Failback is also working fine. But
when i try to move the SQL cluster group to Server2 the cluster administrator
hangs and the only way to get the SQL cluster group running on server2 is
taking server1 offline. the same problem occurs when i try to failback to
server 1.
The SQL cluster group contains the folowing resources:
-Disk R
-SQL IP address
-MSMQ
-SQL network name
-SQL server
-SQL Server agent
-SQL Server Fulltext
Also i did the following test:
When i take the SQL server resource offline i can move the SQL cluster group
between the 2 servers. and when i take the SQL server resource online again a
try the same the cluster administrator hangs.
Note: Server2 acts as 2003 DC and DNS server
Regards,
"Linchi Shea" wrote:

> From the context, by "cluster manager" and "sql manager", I take that you
> meant "Cluster Administrator", and Cluster Administrator still reports the
> state of the cluster properly, right? (e.g. you can view whether a group is
> online and on which node the group is running, etc) In addition, the SQL
> instance itself works fine, right?
> I'd try to establish whether this is a Cluster Administrator tool problem or
> the cluster/sql problem. Try tto move the SQL group using Cluster
> Administrator on one of the nodes itself. Failing that, check to see whether
> the cluster service works properly w.r.t. the SQL group. For instance, you
> can deny the cluster service account access to the SQL instance, and this
> will force the cluster service to bounce the SQL group between the nodes
> (because its IsAlive check would fail) and eventually give up. If the cluster
> does behave this way, I'd then focus on troubleshooting the Cluster
> Adminitrator itself.
> Linchi

Cluster Lan Interface

We have a SQL Fail-Over Cluster with on Lan Interface and One Heartbeat
Interface. The Lan Interface (NIC) on our active node went down so our
clients could not access the server. Since the services and the Heartbeatr
interface did not go down the passive node did not failover and take control
of the Cluster automatically. We had to force the passive cluster to
failover. Is there anyway we can prevent this from happening in the future ?
Hi
Have you had a look at
http://support.microsoft.com/default...;en-us;242600?
If you have Media Sense Disabled, the cluster will not fail over.
Regards
Mike
"ejcs@.noemail.nospam.com" wrote:

> We have a SQL Fail-Over Cluster with on Lan Interface and One Heartbeat
> Interface. The Lan Interface (NIC) on our active node went down so our
> clients could not access the server. Since the services and the Heartbeatr
> interface did not go down the passive node did not failover and take control
> of the Cluster automatically. We had to force the passive cluster to
> failover. Is there anyway we can prevent this from happening in the future ?
|||Hi,
I wanted to post a quick note to see if you would like additional
assistance or information regarding Mike's suggestions on this particular
issue. Have you tried the method described in KB:Q242600, does this resolve
your problem?
Please feel free to let me know if there is anything more I could do to
help on this issue and we appreciate your patience and look forward to
hearing from you!
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!
|||I thought I would post this here in case somebody else has this problem. Incidentally, the link above to the KB article doesn't work: here it is again:
http://support.microsoft.com/default...b;en-us;242600
A common expectation of a virtual SQL running on a MS cluster is that link failure on the active node NIC will result in a failover.
Examples: loose cable, kicked cable, failed switch or switch module.
However, this will not cause a failover to the passive node
"Simply removing the network cable from the client network adapter does not constitute an adapter failure."
http://support.microsoft.com/kb/176320
I'm currently exploring a different issue for a client which if I find a solution for I will post here.
Scenario: 2 cluster active/passive MS cluster running SQL 2000 Enterprise. Public NICS are mixed mode, Private NIC is internal heartbeat only.
Symptons:
- unplugging public NIC cable from passive node will cause interface to dissapear from Cluster Admin
- unplugging public NIC cable from active node will cause both public NICs to become unavailable in Cluster Admin
- unplugging BOTH public NICs will cause public NIC of active to RE-APPEAR and be normal!
Anyway, I'll post more if I find a solution...|||Erratim: sorry the link from the second poster does work... didn't realise it was truncating the display.
Also, when both cables are pulled from the public NICs the status is unreachable, not unavailable |||As a conclusion to this post, my issue related to the DisableDHCPMediaSense in the Windows Registry.
The active node had this set. Nobody set this value, so it seems to have been set by the system at some point.
Check MS KB on this issue if you have a cluster that won't failover when the network cable or switch goes down.

Cluster Lan Interface

We have a SQL Fail-Over Cluster with on Lan Interface and One Heartbeat
Interface. The Lan Interface (NIC) on our active node went down so our
clients could not access the server. Since the services and the Heartbeatr
interface did not go down the passive node did not failover and take control
of the Cluster automatically. We had to force the passive cluster to
failover. Is there anyway we can prevent this from happening in the future ?Hi
Have you had a look at
http://support.microsoft.com/defaul...b;en-us;242600?
If you have Media Sense Disabled, the cluster will not fail over.
Regards
Mike
"ejcs@.noemail.nospam.com" wrote:
[vbcol=seagreen]
> We have a SQL Fail-Over Cluster with on Lan Interface and One Heartbeat
> Interface. The Lan Interface (NIC) on our active node went down so our
> clients could not access the server. Since the services and the Heartbeatr
> interface did not go down the passive node did not failover and take contr
ol
> of the Cluster automatically. We had to force the passive cluster to
> failover. Is there anyway we can prevent this from happening in the future ?[/vbco
l]|||Hi,
I wanted to post a quick note to see if you would like additional
assistance or information regarding Mike's suggestions on this particular
issue. Have you tried the method described in KB:Q242600, does this resolve
your problem?
Please feel free to let me know if there is anything more I could do to
help on this issue and we appreciate your patience and look forward to
hearing from you!
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||I thought I would post this here in case somebody else has this problem.
Incidentally, the link above to the KB article doesn't work: here it is
again:
http://tinyurl.com/4kt2f
A common expectation of a virtual SQL running on a MS cluster is that
link failure on the active node NIC will result in a failover.
Examples: loose cable, kicked cable, failed switch or switch module.
However, this will not cause a failover to the passive node
"Simply removing the network cable from the client network adapter does
not constitute an adapter failure."
http://support.microsoft.com/kb/176320
I'm currently exploring a different issue for a client which if I find
a solution for I will post here.
Scenario: 2 cluster active/passive MS cluster running SQL 2000
Enterprise. Public NICS are mixed mode, Private NIC is internal
heartbeat only.
Symptons:
- unplugging public NIC cable from passive node will cause interface to
dissapear from Cluster Admin
- unplugging public NIC cable from active node will cause both public
NICs to become unavailable in Cluster Admin
- unplugging BOTH public NICs will cause public NIC of active to
RE-APPEAR and be normal!
Anyway, I'll post more if I find a solution...
JasonX
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message1175343.html|||Erratim: sorry the link from the second poster does work... didn't
realise it was truncating the display.
Also, when both cables are pulled from the public NICs the status is
unreachable, not unavailable
JasonX
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message1175343.html|||As a conclusion to this post, my issue related to the
DisableDHCPMediaSense in the Windows Registry.
The active node had this set. Nobody set this value, so it seems to
have been set by the system at some point.
Check MS KB on this issue if you have a cluster that won't failover
when the network cable or switch goes down.
JasonX
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message1175343.html

Cluster Lan Interface

We have a SQL Fail-Over Cluster with on Lan Interface and One Heartbeat
Interface. The Lan Interface (NIC) on our active node went down so our
clients could not access the server. Since the services and the Heartbeatr
interface did not go down the passive node did not failover and take control
of the Cluster automatically. We had to force the passive cluster to
failover. Is there anyway we can prevent this from happening in the future ?Hi
Have you had a look at
http://support.microsoft.com/default.aspx?scid=kb;en-us;242600?
If you have Media Sense Disabled, the cluster will not fail over.
Regards
Mike
"ejcs@.noemail.nospam.com" wrote:
> We have a SQL Fail-Over Cluster with on Lan Interface and One Heartbeat
> Interface. The Lan Interface (NIC) on our active node went down so our
> clients could not access the server. Since the services and the Heartbeatr
> interface did not go down the passive node did not failover and take control
> of the Cluster automatically. We had to force the passive cluster to
> failover. Is there anyway we can prevent this from happening in the future ?|||Hi,
I wanted to post a quick note to see if you would like additional
assistance or information regarding Mike's suggestions on this particular
issue. Have you tried the method described in KB:Q242600, does this resolve
your problem?
Please feel free to let me know if there is anything more I could do to
help on this issue and we appreciate your patience and look forward to
hearing from you!
Sincerely yours,
Michael Cheng
Online Partner Support Specialist
Partner Support Group
Microsoft Global Technical Support Center
---
Get Secure! - http://www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!|||I thought I would post this here in case somebody else has this problem.
Incidentally, the link above to the KB article doesn't work: here it is
again:
http://tinyurl.com/4kt2f
A common expectation of a virtual SQL running on a MS cluster is that
link failure on the active node NIC will result in a failover.
Examples: loose cable, kicked cable, failed switch or switch module.
However, this will not cause a failover to the passive node
"Simply removing the network cable from the client network adapter does
not constitute an adapter failure."
http://support.microsoft.com/kb/176320
I'm currently exploring a different issue for a client which if I find
a solution for I will post here.
Scenario: 2 cluster active/passive MS cluster running SQL 2000
Enterprise. Public NICS are mixed mode, Private NIC is internal
heartbeat only.
Symptons:
- unplugging public NIC cable from passive node will cause interface to
dissapear from Cluster Admin
- unplugging public NIC cable from active node will cause both public
NICs to become unavailable in Cluster Admin
- unplugging BOTH public NICs will cause public NIC of active to
RE-APPEAR and be normal!
Anyway, I'll post more if I find a solution...
JasonX
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message1175343.html|||Erratim: sorry the link from the second poster does work... didn't
realise it was truncating the display.
Also, when both cables are pulled from the public NICs the status is
unreachable, not unavailable :)
JasonX
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message1175343.html|||As a conclusion to this post, my issue related to the
DisableDHCPMediaSense in the Windows Registry.
The active node had this set. Nobody set this value, so it seems to
have been set by the system at some point.
Check MS KB on this issue if you have a cluster that won't failover
when the network cable or switch goes down.
JasonX
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message1175343.html