Additional IP for SQL Cluster

Hi,
We have a two node failover SQL 2000 cluster setup. These servers are on a
closed netowrk where they do not have access to internet or anything other
network. I now have a need to be able to connect to the SQL server from
another network. I had added the correct gateway etc and can assign a new IP
in the cluster for outside access. Everything work fine except that SQL will
not listen on this IP. I am assigning the new IP on the same NIC as my
cluster's public IP. Does anyone know who do I go about making SQL listen
on both IPs?
Thank you.
Hi
Have you made the IP address available as a resource to SQL Server?
John
"Dragon" wrote:

> Hi,
> We have a two node failover SQL 2000 cluster setup. These servers are on a
> closed netowrk where they do not have access to internet or anything other
> network. I now have a need to be able to connect to the SQL server from
> another network. I had added the correct gateway etc and can assign a new IP
> in the cluster for outside access. Everything work fine except that SQL will
> not listen on this IP. I am assigning the new IP on the same NIC as my
> cluster's public IP. Does anyone know who do I go about making SQL listen
> on both IPs?
> Thank you.
>
>
|||Open the cluster administrator tool and add an IP Address resource to the
group that SQL has been installed in. You will need to have a different IP
bound to the NIC for this to work, but of course on that same subnet.
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Dragon" <baadil_nospam@.hotmail.com> wrote in message
news:OHT8S4NCHHA.4680@.TK2MSFTNGP04.phx.gbl...
> Hi,
> We have a two node failover SQL 2000 cluster setup. These servers are on a
> closed netowrk where they do not have access to internet or anything other
> network. I now have a need to be able to connect to the SQL server from
> another network. I had added the correct gateway etc and can assign a new
> IP in the cluster for outside access. Everything work fine except that SQL
> will not listen on this IP. I am assigning the new IP on the same NIC as
> my cluster's public IP. Does anyone know who do I go about making SQL
> listen on both IPs?
> Thank you.
>
|||I read the other two responses, and although they were posted in the SS
cluster forum, they are clearly OS answers. They will not work.
Every Operation DBA knows that you cannot manage SQL Server 2000 Cluster IP
addresses through the Cluster Administrator APIs.
You must rerun the SQL Server 2000 Setup utility, Virtual Server, Advanced
Options, Manager Cluster Resources, and add the additional IP resources from
the Network Dialog.
The only other alternative would be to hack the registry (HKLM\Cluster and
HKLM\SOFTWARE\Microsoft, either Microsoft SQL
Server\MSSQL$InstanceName\MSSQLServer or MSSQLServer\MSSQLServer cluster
keys and resources).
Sincerely,
Anthony Thomas

"Dragon" <baadil_nospam@.hotmail.com> wrote in message
news:OHT8S4NCHHA.4680@.TK2MSFTNGP04.phx.gbl...
> Hi,
> We have a two node failover SQL 2000 cluster setup. These servers are on a
> closed netowrk where they do not have access to internet or anything other
> network. I now have a need to be able to connect to the SQL server from
> another network. I had added the correct gateway etc and can assign a new
IP
> in the cluster for outside access. Everything work fine except that SQL
will
> not listen on this IP. I am assigning the new IP on the same NIC as my
> cluster's public IP. Does anyone know who do I go about making SQL listen
> on both IPs?
> Thank you.
>

Additional IP for SQL Cluster

Hi,
We have a two node failover SQL 2000 cluster setup. These servers are on a
closed netowrk where they do not have access to internet or anything other
network. I now have a need to be able to connect to the SQL server from
another network. I had added the correct gateway etc and can assign a new IP
in the cluster for outside access. Everything work fine except that SQL will
not listen on this IP. I am assigning the new IP on the same NIC as my
cluster's public IP. Does anyone know who do I go about making SQL listen
on both IPs?
Thank you.Hi
Have you made the IP address available as a resource to SQL Server?
John
"Dragon" wrote:
> Hi,
> We have a two node failover SQL 2000 cluster setup. These servers are on a
> closed netowrk where they do not have access to internet or anything other
> network. I now have a need to be able to connect to the SQL server from
> another network. I had added the correct gateway etc and can assign a new IP
> in the cluster for outside access. Everything work fine except that SQL will
> not listen on this IP. I am assigning the new IP on the same NIC as my
> cluster's public IP. Does anyone know who do I go about making SQL listen
> on both IPs?
> Thank you.
>
>|||Open the cluster administrator tool and add an IP Address resource to the
group that SQL has been installed in. You will need to have a different IP
bound to the NIC for this to work, but of course on that same subnet.
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Dragon" <baadil_nospam@.hotmail.com> wrote in message
news:OHT8S4NCHHA.4680@.TK2MSFTNGP04.phx.gbl...
> Hi,
> We have a two node failover SQL 2000 cluster setup. These servers are on a
> closed netowrk where they do not have access to internet or anything other
> network. I now have a need to be able to connect to the SQL server from
> another network. I had added the correct gateway etc and can assign a new
> IP in the cluster for outside access. Everything work fine except that SQL
> will not listen on this IP. I am assigning the new IP on the same NIC as
> my cluster's public IP. Does anyone know who do I go about making SQL
> listen on both IPs?
> Thank you.
>|||I read the other two responses, and although they were posted in the SS
cluster forum, they are clearly OS answers. They will not work.
Every Operation DBA knows that you cannot manage SQL Server 2000 Cluster IP
addresses through the Cluster Administrator APIs.
You must rerun the SQL Server 2000 Setup utility, Virtual Server, Advanced
Options, Manager Cluster Resources, and add the additional IP resources from
the Network Dialog.
The only other alternative would be to hack the registry (HKLM\Cluster and
HKLM\SOFTWARE\Microsoft, either Microsoft SQL
Server\MSSQL$InstanceName\MSSQLServer or MSSQLServer\MSSQLServer cluster
keys and resources).
Sincerely,
Anthony Thomas
"Dragon" <baadil_nospam@.hotmail.com> wrote in message
news:OHT8S4NCHHA.4680@.TK2MSFTNGP04.phx.gbl...
> Hi,
> We have a two node failover SQL 2000 cluster setup. These servers are on a
> closed netowrk where they do not have access to internet or anything other
> network. I now have a need to be able to connect to the SQL server from
> another network. I had added the correct gateway etc and can assign a new
IP
> in the cluster for outside access. Everything work fine except that SQL
will
> not listen on this IP. I am assigning the new IP on the same NIC as my
> cluster's public IP. Does anyone know who do I go about making SQL listen
> on both IPs?
> Thank you.
>

Additional IP for SQL Cluster

Hi,
We have a two node failover SQL 2000 cluster setup. These servers are on a
closed netowrk where they do not have access to internet or anything other
network. I now have a need to be able to connect to the SQL server from
another network. I had added the correct gateway etc and can assign a new IP
in the cluster for outside access. Everything work fine except that SQL will
not listen on this IP. I am assigning the new IP on the same NIC as my
cluster's public IP. Does anyone know who do I go about making SQL listen
on both IPs?
Thank you.
Hi
Have you made the IP address available as a resource to SQL Server?
John
"Dragon" wrote:

> Hi,
> We have a two node failover SQL 2000 cluster setup. These servers are on a
> closed netowrk where they do not have access to internet or anything other
> network. I now have a need to be able to connect to the SQL server from
> another network. I had added the correct gateway etc and can assign a new IP
> in the cluster for outside access. Everything work fine except that SQL will
> not listen on this IP. I am assigning the new IP on the same NIC as my
> cluster's public IP. Does anyone know who do I go about making SQL listen
> on both IPs?
> Thank you.
>
>
|||Open the cluster administrator tool and add an IP Address resource to the
group that SQL has been installed in. You will need to have a different IP
bound to the NIC for this to work, but of course on that same subnet.
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Dragon" <baadil_nospam@.hotmail.com> wrote in message
news:OHT8S4NCHHA.4680@.TK2MSFTNGP04.phx.gbl...
> Hi,
> We have a two node failover SQL 2000 cluster setup. These servers are on a
> closed netowrk where they do not have access to internet or anything other
> network. I now have a need to be able to connect to the SQL server from
> another network. I had added the correct gateway etc and can assign a new
> IP in the cluster for outside access. Everything work fine except that SQL
> will not listen on this IP. I am assigning the new IP on the same NIC as
> my cluster's public IP. Does anyone know who do I go about making SQL
> listen on both IPs?
> Thank you.
>
|||I read the other two responses, and although they were posted in the SS
cluster forum, they are clearly OS answers. They will not work.
Every Operation DBA knows that you cannot manage SQL Server 2000 Cluster IP
addresses through the Cluster Administrator APIs.
You must rerun the SQL Server 2000 Setup utility, Virtual Server, Advanced
Options, Manager Cluster Resources, and add the additional IP resources from
the Network Dialog.
The only other alternative would be to hack the registry (HKLM\Cluster and
HKLM\SOFTWARE\Microsoft, either Microsoft SQL
Server\MSSQL$InstanceName\MSSQLServer or MSSQLServer\MSSQLServer cluster
keys and resources).
Sincerely,
Anthony Thomas

"Dragon" <baadil_nospam@.hotmail.com> wrote in message
news:OHT8S4NCHHA.4680@.TK2MSFTNGP04.phx.gbl...
> Hi,
> We have a two node failover SQL 2000 cluster setup. These servers are on a
> closed netowrk where they do not have access to internet or anything other
> network. I now have a need to be able to connect to the SQL server from
> another network. I had added the correct gateway etc and can assign a new
IP
> in the cluster for outside access. Everything work fine except that SQL
will
> not listen on this IP. I am assigning the new IP on the same NIC as my
> cluster's public IP. Does anyone know who do I go about making SQL listen
> on both IPs?
> Thank you.
>
sql

Additional IP for SQL Cluster

Hi,
We have a two node failover SQL 2000 cluster setup. These servers are on a
closed netowrk where they do not have access to internet or anything other
network. I now have a need to be able to connect to the SQL server from
another network. I had added the correct gateway etc and can assign a new IP
in the cluster for outside access. Everything work fine except that SQL will
not listen on this IP. I am assigning the new IP on the same NIC as my
cluster's public IP. Does anyone know who do I go about making SQL listen
on both IPs?
Thank you.Hi
Have you made the IP address available as a resource to SQL Server?
John
"Dragon" wrote:

> Hi,
> We have a two node failover SQL 2000 cluster setup. These servers are on a
> closed netowrk where they do not have access to internet or anything other
> network. I now have a need to be able to connect to the SQL server from
> another network. I had added the correct gateway etc and can assign a new
IP
> in the cluster for outside access. Everything work fine except that SQL wi
ll
> not listen on this IP. I am assigning the new IP on the same NIC as my
> cluster's public IP. Does anyone know who do I go about making SQL listen
> on both IPs?
> Thank you.
>
>|||Open the cluster administrator tool and add an IP Address resource to the
group that SQL has been installed in. You will need to have a different IP
bound to the NIC for this to work, but of course on that same subnet.
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Dragon" <baadil_nospam@.hotmail.com> wrote in message
news:OHT8S4NCHHA.4680@.TK2MSFTNGP04.phx.gbl...
> Hi,
> We have a two node failover SQL 2000 cluster setup. These servers are on a
> closed netowrk where they do not have access to internet or anything other
> network. I now have a need to be able to connect to the SQL server from
> another network. I had added the correct gateway etc and can assign a new
> IP in the cluster for outside access. Everything work fine except that SQL
> will not listen on this IP. I am assigning the new IP on the same NIC as
> my cluster's public IP. Does anyone know who do I go about making SQL
> listen on both IPs?
> Thank you.
>|||I read the other two responses, and although they were posted in the SS
cluster forum, they are clearly OS answers. They will not work.
Every Operation DBA knows that you cannot manage SQL Server 2000 Cluster IP
addresses through the Cluster Administrator APIs.
You must rerun the SQL Server 2000 Setup utility, Virtual Server, Advanced
Options, Manager Cluster Resources, and add the additional IP resources from
the Network Dialog.
The only other alternative would be to hack the registry (HKLM\Cluster and
HKLM\SOFTWARE\Microsoft, either Microsoft SQL
Server\MSSQL$InstanceName\MSSQLServer or MSSQLServer\MSSQLServer cluster
keys and resources).
Sincerely,
Anthony Thomas
"Dragon" <baadil_nospam@.hotmail.com> wrote in message
news:OHT8S4NCHHA.4680@.TK2MSFTNGP04.phx.gbl...
> Hi,
> We have a two node failover SQL 2000 cluster setup. These servers are on a
> closed netowrk where they do not have access to internet or anything other
> network. I now have a need to be able to connect to the SQL server from
> another network. I had added the correct gateway etc and can assign a new
IP
> in the cluster for outside access. Everything work fine except that SQL
will
> not listen on this IP. I am assigning the new IP on the same NIC as my
> cluster's public IP. Does anyone know who do I go about making SQL listen
> on both IPs?
> Thank you.
>

Adding SSIS to sql 2005 cluster

The basics
Win2k Enterprise
SQL 2005 Enterprise
2 node cluster, single instance.
So I have had these servers up for a little while and would like to add SSIS
to them.
I found this document here about running setup from the command line for a
cluster
http://msdn2.microsoft.com/en-gb/library/ms144259.aspx
this document for installing SSIS from the command line (not in a cluster)
http://msdn2.microsoft.com/en-gb/library/ms144291.aspx
and this about installing SSIS (not in a cluster)
http://support.microsoft.com/kb/913967
and this about how to configure SSIS on a cluster.
http://msdn2.microsoft.com/en-gb/library/ms345193.aspx
As you can see from this last document, step three seems trivial,
"3. Install Integration Services on each node of the cluster individually."
Can anyone help me put this all together.
I think the main thing I need is the command line to install SSIS on a
cluster.
Also, if anyone knows of any good books on HA SQL, that would be nice, I
looked at a stack of SQL2005 books last night and was surprised to find that
HA and Clustering are hardly mentioned.
Chris
The Installer for SSIS is "not" cluster aware.
You will need to install SSIS on each node of the cluster.
If you install it on Node 1 while the SQL server is running on that
node, the installer will install SSIS on Node 1 only.
You will have to run the install a second time on Node 2, preferably
while the SQL is running on Node 2
Once you have SSIS installed on both nodes, you can follow the
instructions in the document on configuring SSIS on a cluster,
remembering that after you make any changes to the MsDtsSrvr.ini.xml
file you need to restart the SSIS service . That should work in your
configuration. It gets real tricky when you have an active/active setup
(I am still struggling with that myself)
Sorry I cant help with the command line, perhaps a more command line
savy person can help with that.
CDSuperG wrote:
> The basics
> Win2k Enterprise
> SQL 2005 Enterprise
> 2 node cluster, single instance.
> So I have had these servers up for a little while and would like to add SSIS
> to them.
> I found this document here about running setup from the command line for a
> cluster
> http://msdn2.microsoft.com/en-gb/library/ms144259.aspx
> this document for installing SSIS from the command line (not in a cluster)
> http://msdn2.microsoft.com/en-gb/library/ms144291.aspx
> and this about installing SSIS (not in a cluster)
> http://support.microsoft.com/kb/913967
> and this about how to configure SSIS on a cluster.
> http://msdn2.microsoft.com/en-gb/library/ms345193.aspx
> As you can see from this last document, step three seems trivial,
> "3. Install Integration Services on each node of the cluster individually."
> Can anyone help me put this all together.
> I think the main thing I need is the command line to install SSIS on a
> cluster.
> Also, if anyone knows of any good books on HA SQL, that would be nice, I
> looked at a stack of SQL2005 books last night and was surprised to find that
> HA and Clustering are hardly mentioned.
> Chris
|||You can visit www.jumpstarttv.com. There is a good video on the site. You
will have to register before you can see the site, but I did and it helped a
lot.
"Jim" wrote:

> The Installer for SSIS is "not" cluster aware.
> You will need to install SSIS on each node of the cluster.
> If you install it on Node 1 while the SQL server is running on that
> node, the installer will install SSIS on Node 1 only.
> You will have to run the install a second time on Node 2, preferably
> while the SQL is running on Node 2
> Once you have SSIS installed on both nodes, you can follow the
> instructions in the document on configuring SSIS on a cluster,
> remembering that after you make any changes to the MsDtsSrvr.ini.xml
> file you need to restart the SSIS service . That should work in your
> configuration. It gets real tricky when you have an active/active setup
> (I am still struggling with that myself)
> Sorry I cant help with the command line, perhaps a more command line
> savy person can help with that.
> CDSuperG wrote:
>

adding sql server CAL on cluster

Hi Guys,
i am using sql server 2000 on Windows 2000 cluster with
150 concurrent license . now i want to add 50 more licence.
do i have to add this for both nodes?
what is the procedure to do this ? is it using licensing
manager in control panel?
PLS advice meReplied in the other thread.
David Portas
SQL Server MVP
--

adding sql server CAL on cluster

Hi Guys,
i am using sql server 2000 on windows 2000 cluster with
150 concurrent license . now i want to add 50 more licence.
do i have to add this for both nodes?
what is the procedure to do this ? is it using licensing
manager in control panel?
PLS advice me
Replied in the other thread.
David Portas
SQL Server MVP

Adding Spindals on Cluster to SAN

How much work is it to add spindals to a drive on a
Windows 2000 Advanced Server clustered on a SAN?
Thank You,
Dave
You will need Veritas volume manager to expand the logical drive at the OS
level under Windows 2000. What happens at the SAN level depends on your SAN
vendor.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Dave" <anonymous@.discussions.microsoft.com> wrote in message
news:59bf01c42d50$5c2ec8a0$a301280a@.phx.gbl...
> How much work is it to add spindals to a drive on a
> Windows 2000 Advanced Server clustered on a SAN?
> Thank You,
> Dave
|||Dave -
Because we don't use Veritas we generally just add another drive to the
cluster, and make sure that the new drive does not share any spindals with
the old drive on the SAN. Then we just balance our data files.
Craig
ccarl@.mcafee.com
"Dave" <anonymous@.discussions.microsoft.com> wrote in message
news:59bf01c42d50$5c2ec8a0$a301280a@.phx.gbl...
> How much work is it to add spindals to a drive on a
> Windows 2000 Advanced Server clustered on a SAN?
> Thank You,
> Dave
|||If you wish to add physical disks to the same volume presented to your nodes in the cluster, assuming your SAN vendor supports it:
1. Add the new disks to the disk pool
2. Use diskpart (from the W2K resource kit - it comes with the o/s in W2K3) to "list volume" then "select volume" x and then "extend" the partition.
Note1: You must use diskpart 5.1 or newer (some of the earlier versions are dodgy)
Note2: This is an on-line operation and causes no disruption to current SQL operations.

adding second node to sql cluster

I created a one node Cluster in Windows 2003 enterprise server. I then loaded
a SQL 2000 Vitrual server. I now need to add a second node. The cluster sees
the new node. However when I attempt to load the SLQ executables on the
second node the only option I have once I choose the virtual server is to
upgrade the existing installation. That does not install the executable on
the second node. What am I doing wrong. Thanks in advance.
you must choose upgrade the existing installation on virual server and add
second node for existing virtual sql server
Aleksandar Grbic
MCDBA, Senior Database Administrator
"Joe McHae" wrote:

> I created a one node Cluster in Windows 2003 enterprise server. I then loaded
> a SQL 2000 Vitrual server. I now need to add a second node. The cluster sees
> the new node. However when I attempt to load the SLQ executables on the
> second node the only option I have once I choose the virtual server is to
> upgrade the existing installation. That does not install the executable on
> the second node. What am I doing wrong. Thanks in advance.
|||I did choose upgrade. I did not see an option to add a second node for the
existing sql server. The second server is in the cluster.
"Aleksandar Grbic" wrote:
[vbcol=seagreen]
> you must choose upgrade the existing installation on virual server and add
> second node for existing virtual sql server
> --
> Aleksandar Grbic
> MCDBA, Senior Database Administrator
>
> "Joe McHae" wrote:
|||In the setup routine, there will be an Advanced option. After selecting,
there will be a Maintain and Existing Installation option.
This will take you down an installation path were you can add new cluster
member nodes as a potential SQL Server failover partner.
In the maintenance section of the SQL Server 2000 failover clustering
document is an Add/Remove Cluster Nodes sub-section.
Adding or Removing a Cluster Node from the Virtual Server Definition
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/failclus.mspx#EPUAG
Best of luck.
Sincerely,
Anthony Thomas

"Joe McHae" <JoeMcHae@.discussions.microsoft.com> wrote in message
news:332E6DA7-9F20-455C-97BE-ABD7BE8EFAE8@.microsoft.com...[vbcol=seagreen]
> I did choose upgrade. I did not see an option to add a second node for the
> existing sql server. The second server is in the cluster.
> "Aleksandar Grbic" wrote:
add[vbcol=seagreen]
loaded[vbcol=seagreen]
cluster sees[vbcol=seagreen]
the[vbcol=seagreen]
to[vbcol=seagreen]
executable on[vbcol=seagreen]
|||Anthony;
thanks, the problem I wa having was the executables for SQL were not loading
on the second node. I followed your link then removed the node and added it
again. for some reasons the executables are there. I guess that is why they
call it magic.
Joe
"Anthony Thomas" wrote:

> In the setup routine, there will be an Advanced option. After selecting,
> there will be a Maintain and Existing Installation option.
> This will take you down an installation path were you can add new cluster
> member nodes as a potential SQL Server failover partner.
> In the maintenance section of the SQL Server 2000 failover clustering
> document is an Add/Remove Cluster Nodes sub-section.
> Adding or Removing a Cluster Node from the Virtual Server Definition
> http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/failclus.mspx#EPUAG
> Best of luck.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Joe McHae" <JoeMcHae@.discussions.microsoft.com> wrote in message
> news:332E6DA7-9F20-455C-97BE-ABD7BE8EFAE8@.microsoft.com...
> add
> loaded
> cluster sees
> the
> to
> executable on
>
>

Adding node to cluster

Hello everyone!
We currently have a one node cluster (w2k3 and sql2000ent) and have had it
this way for a while waiting on the second server to arrive, well, the time
has come and now we are about to install the second node in this
active/passive cluster.
I have been reading in booksonline on how to do this and it seems fairly
simple. Install the second server, add it to the cluster and run sql setup
on it, choosing "maintaining a virtual server for failover" and so on. Am I
right so far?
My questions are:
Should I run the sql installation from the new node or from the old one? Or
does it not matter?
When the installation is done I've understood that I have to reapply sp3a?
And that this is done from the node that is currently the owner?
Thanks in advance for your help!
Regards,
Erik
1. You run SQL Server setup from the old node, with SQL Server running on
that node.
2. You run SP3a from the node that currently owns SQL Server while SQL
Server is active on that node.
You will also need to apply any patches as well.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||1. You run SQL Server setup from the old node, with SQL Server running on
that node.
2. You run SP3a from the node that currently owns SQL Server while SQL
Server is active on that node.
You will also need to apply any patches as well.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Thanks alot for those tips!
/Erik
"Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message
news:h9sx6h6UEHA.2436@.cpmsftngxa10.phx.gbl...
> 1. You run SQL Server setup from the old node, with SQL Server running on
> that node.
> 2. You run SP3a from the node that currently owns SQL Server while SQL
> Server is active on that node.
> You will also need to apply any patches as well.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>

Adding node back after hardware failure.

After you have to take a node out of a SQL cluster, what is
the procedure to get it back in the cluster?
The second machine is back up and working on the cluster
with everything except the SQL resources, which makes sense
because you have to install SQL on the cluster after it is
set up.
But how should we go about getting this machine back in the
SQL cluster? Should we just reinstall SQL on the cluster,
or should we uninstall first? Is uninstalling simple on a
cluster?
Is there anything obvious that I'm leaving out that will
cause us headaches?
Thanks in advance,
Shawn
Look up 'Maintaining a Failover Cluster' in BOL. It has step-by-step
instructions on how to replace a failed node in a SQL cluster.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Shawn" <anonymous@.discussions.microsoft.com> wrote in message
news:18cfe01c44bdc$c8664390$a501280a@.phx.gbl...
> After you have to take a node out of a SQL cluster, what is
> the procedure to get it back in the cluster?
> The second machine is back up and working on the cluster
> with everything except the SQL resources, which makes sense
> because you have to install SQL on the cluster after it is
> set up.
> But how should we go about getting this machine back in the
> SQL cluster? Should we just reinstall SQL on the cluster,
> or should we uninstall first? Is uninstalling simple on a
> cluster?
> Is there anything obvious that I'm leaving out that will
> cause us headaches?
> Thanks in advance,
> Shawn
|||Awesome. Thanks.
>--Original Message--
>Look up 'Maintaining a Failover Cluster' in BOL. It has
step-by-step
>instructions on how to replace a failed node in a SQL cluster.
>
>--
>Geoff N. Hiten
>Microsoft SQL Server MVP
>Senior Database Administrator
>Careerbuilder.com
>I support the Professional Association for SQL Server
>www.sqlpass.org
>"Shawn" <anonymous@.discussions.microsoft.com> wrote in message
>news:18cfe01c44bdc$c8664390$a501280a@.phx.gbl...
>
>.
>

Adding new node to SQL SP4 cluster

Hi all,
I'm trying to add a new node to our SQL Server 2000 SP4 cluster. Cluster
node is Windows 2003 SP1. I can add the node to the SQL cluster, but when I
try to add SP4 to the new node, I get an error message when I enter in the
service password for the instance.
Error message : Setup cannot verify/grant logon as service right to the SQL
Server service logon account: 5000 (0x1388)
However, this error didn't come up when I was adding the node to the SQL
cluster and it prompted me for the same password. We're running an
active/active configuration and I can't do anything with the other instance
(the default one) as it says that this instance is still waiting for the
service pack!
Any ideas anyone? Thanks in advance
Dave
Dave Wall
Dave,
It looks like a permission issue. Does the Windows domain a/c that you are using the setup have local admin privileges on both the cluster nodes? Try running the setup using the virtual SQL Server service a/c or the
cluster service a/c ?
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
|||Dave,
Are you using the NEED_SP_KEY in the registry. If yes, then remove this key and re-run SP4 from the original node (i.e the node that is already on SP4 and owns the SQL resources) and see if this helps?
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
|||Thanks Uttam,
removed the reg key and it all went through without any problems
Dave
Dave Wall
"Uttam Parui[MS]" wrote:

> Dave,
> Are you using the NEED_SP_KEY in the registry. If yes, then remove this key and re-run SP4 from the original node (i.e the node that is already on SP4 and owns the SQL resources) and see if this helps?
> 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
>
>
|||Dave,
Glad to hear that the issue is resolved. I appreciate your update.
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
|||Hello, I'm having the same problem, but I don't know what you mean by this
NEED_SP_KEY I can't find any information on it. If you could shed some light
on this I would greatly appreciate it!
--Gene
"Uttam Parui[MS]" <uttamkp@.online.microsoft.com> wrote in message
news:KA3IUo6kFHA.944@.TK2MSFTNGXA01.phx.gbl...
> Dave,
> Are you using the NEED_SP_KEY in the registry. If yes, then remove this
key and re-run SP4 from the original node (i.e the node that is already on
SP4 and owns the SQL resources) and see if this helps?
> 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
>
|||Depending on certain parameters, the Need_SP_Key is added to the new node by the setup process when the node is
added to the SQL failover cluster.
Check (on all nodes) if you have the following key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\80\Need_SP_Key
If yes, then delete it. Then try to install the service pack 4 from the active node where SQL Server is currently running.
If no, then you might be having a different issue. Give more details for us to help you.
HTH,
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
|||Uttam Parui[MS] wrote:
> Dave,
> Are you using the NEED_SP_KEY in the registry. If yes, then remove this key and re-run SP4 from the original node (i.e the node that is already on SP4 and owns the SQL resources) and see if this helps?
For me this does not realy help. The node needs to be a possible owner of
the sql resources or else, the node is not updated. When you have just added
the node by the advanced sql setup option, this is not the case yet.
The second problem is, that this way sp4 updates all the nodes and takes the
SQL resources OFFLINE.
I tried installing SP3 first, which is not a goed idea. The sqlsetup runs
fine, the node becomes a possible owner but can't be used (sql wil not come
online), the NEED_SP_KEY dissapears, with means SP4 wants to reapply totaly.
Restoring the NEED_SP_KEY solves this but then the "Setup cannot
verify/grant logon as service right..." is back.
So adding a SP4 node without takeing SQL temporarily offline is not possible.
Hans
p.s.
SP4 was installed with a enterprise admin account.
|||There is a hotfix available from Microsoft support which fixed this for me.
See http://support.microsoft.com/?kbid=905286
BB.
"Hans de Bruin" wrote:

> Uttam Parui[MS] wrote:
> For me this does not realy help. The node needs to be a possible owner of
> the sql resources or else, the node is not updated. When you have just added
> the node by the advanced sql setup option, this is not the case yet.
> The second problem is, that this way sp4 updates all the nodes and takes the
> SQL resources OFFLINE.
> I tried installing SP3 first, which is not a goed idea. The sqlsetup runs
> fine, the node becomes a possible owner but can't be used (sql wil not come
> online), the NEED_SP_KEY dissapears, with means SP4 wants to reapply totaly.
> Restoring the NEED_SP_KEY solves this but then the "Setup cannot
> verify/grant logon as service right..." is back.
> So adding a SP4 node without takeing SQL temporarily offline is not possible.
> --
> Hans
> p.s.
> SP4 was installed with a enterprise admin account.
>

Adding Full-Text Search Indexing to a Cluster

Ihave an Active/Passive Cluster. Can someone point me to a Technet
article or provide the steps for adding Full-text indexing?
I can't seem to find one!
Thank you.
Jay
SQL FTS has to be installed from the start on a cluster. The SQL Server 2000
High availablilty book is pretty good for installing a cluster.
<jay.griffin@.burke.com> wrote in message
news:1107212619.013634.8160@.c13g2000cwb.googlegrou ps.com...
> Ihave an Active/Passive Cluster. Can someone point me to a Technet
> article or provide the steps for adding Full-text indexing?
> I can't seem to find one!
> Thank you.
> Jay
>
|||Jay,
Could you post the full output of -- SELECT @.@.version -- as this is helpful
in understanding your current clustered environment.
For the time being, I'm going to assume that you have a clustered SQL Server
2000 A/P environment. Correct? If so, then you should be using SQL Server
2000 Enterprise Edition and Full-text Indexing (and Full-text Search, often
referred to as SQL FTS) is installed by default.
You can use the SQL Enterprise Manager and select Server and database, you
want to FT-enable and click on Tools -> Full-text Indexing to launch the FT
Indexing Wizard. This wizard (SQLFTWiz.exe) will walk you though all the
necessary steps for adding Full-text Indexing to a selected table. Note, the
table, must have a single column, non-nullable, unique index to qualify for
a table to be FT Indexed. Also, the only restriction for FTI in a clustered
environment, is that the FT Catalog, must be created on the shared disk
drive in your clustered environment.
You may also want to do this via pure T-SQL code, and if so, checkout "Full
Text Indexing using T-SQL from a Profiler Trace" at
http://spaces.msn.com/members/jtkane/Blog/cns!1pWDBCiDX1uvH5ATJmNCVLPQ!304.entry
and this blog entry will walk you though all the necessary T-SQL code.
Hope that helps!
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
<jay.griffin@.burke.com> wrote in message
news:1107212619.013634.8160@.c13g2000cwb.googlegrou ps.com...
> Ihave an Active/Passive Cluster. Can someone point me to a Technet
> article or provide the steps for adding Full-text indexing?
> I can't seem to find one!
> Thank you.
> Jay
>
|||Thanks for your help. It is SQL 2000 Enterprise (A/P) on Windows 2000
Adv Server. Sorry to omit that important information.
Here is my problem -- Full Text indexing is not installed. When I try
to do what you indicated, Full Text Indexing is grayed out.
I was installing some other software which was going to create a
database. It gave the a warning that Full text indexing was not
installed and the software would not function properly.
If I go into the SQL Setup, I can't add/remove components. The only
option I have is to Uninstall. I am wondering how I can add full-text
indexing.
Thanks for your help,
Jay
John Kane wrote:
> Jay,
> Could you post the full output of -- SELECT @.@.version -- as this is
helpful
> in understanding your current clustered environment.
> For the time being, I'm going to assume that you have a clustered SQL
Server
> 2000 A/P environment. Correct? If so, then you should be using SQL
Server
> 2000 Enterprise Edition and Full-text Indexing (and Full-text Search,
often
> referred to as SQL FTS) is installed by default.
> You can use the SQL Enterprise Manager and select Server and
database, you
> want to FT-enable and click on Tools -> Full-text Indexing to launch
the FT
> Indexing Wizard. This wizard (SQLFTWiz.exe) will walk you though all
the
> necessary steps for adding Full-text Indexing to a selected table.
Note, the
> table, must have a single column, non-nullable, unique index to
qualify for
> a table to be FT Indexed. Also, the only restriction for FTI in a
clustered
> environment, is that the FT Catalog, must be created on the shared
disk
> drive in your clustered environment.
> You may also want to do this via pure T-SQL code, and if so, checkout
"Full
> Text Indexing using T-SQL from a Profiler Trace" at
>
http://spaces.msn.com/members/jtkane/Blog/cns!1pWDBCiDX1uvH5ATJmNCVLPQ!304.entry
> and this blog entry will walk you though all the necessary T-SQL
code.[vbcol=seagreen]
> Hope that helps!
> John
> --
> SQL Full Text Search Blog
> http://spaces.msn.com/members/jtkane/
>
> <jay.griffin@.burke.com> wrote in message
> news:1107212619.013634.8160@.c13g2000cwb.googlegrou ps.com...
|||You're welcome, Jay,
Despite what you see as "Full Text Indexing is grayed out", it is most
likely that Full Text Search (FTS) is installed because of what you see when
you attempt to add the "Full-Text Search" components via SQL Setup and
"custom installation" where the "Full-Text Search" component option is
already checkmarked. Correct?
If the above is not correct, you may have the MSSQLServer service running
under a local machine account, if so, then checkout KB article Q270671
(Q270671) "PRB: Full Text Search Menus Are Not Enabled for Local Windows NT
Accounts" at:
http://support.microsoft.com/default...;en-us;q270671
If the above is correct, then you can force the removal of the checkmark via
the removal or renaming of the following tracking registry key and the
following procedure to Re-install" the "Full-text Search" components via
deleting (or renaming) the below "tracking key" and re-install (If you're
not using a named instance, remove "<Instance_Name>\".)
NOTE: be sure to be logged on to the server as either Administrator or as a
member of the server's Admin Group!
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\<Instance_Name>\Tracking\
{E07FDDA7-5A21-11d2-9DAD-00C04F79D434}
Once you're done removed (renamed) the above tracking key, then delete the
MSSearch directory from either:
drive_letter:\Program Files\Common Files\Microsoft Shared\
or
drive_letter::\Program Files\Common Files\System\
Then using your SQL Server 2000 installation CD re-install via "Custom
Installation" the Full-Text Search component (it should be un-checked). When
this completes find and save these files: SearchSetup.log (usually under
\windows or \winnt folders) and sqlsp.log. If any problems, please post
these files.
Re-install the service pack that you may have applied to SQL Server 2000, so
that the newly re-installed MSSearch components are upgraded to SP3a levels
and then re-boot &/or restart the MSSearch and MSSQLServer services.
You may also want to consult or perform the procedures document in the
following Kb article: 827449 "How to manually reinstall the Microsoft Search
service for an instance of SQL 2000" at:
http://support.microsoft.com/default...b;EN-US;827449
Finally, and considering that this is a clustered environment, you may also
want to review the following KB articles:
812666 "How to recover a failed full-text search resource on a clustered
instance of SQL Server 2000" at:
http://support.microsoft.com/default.aspx?kbid=812666
"The full-text search results that are returned in a clustered SQL Server
2000 environment may be different when the active node changes" at:
http://support.microsoft.com/default...b;en-us;889708
Hope that helps!
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
<jay.griffin@.burke.com> wrote in message
news:1107270434.064396.309410@.c13g2000cwb.googlegr oups.com...
> Thanks for your help. It is SQL 2000 Enterprise (A/P) on Windows 2000
> Adv Server. Sorry to omit that important information.
> Here is my problem -- Full Text indexing is not installed. When I try
> to do what you indicated, Full Text Indexing is grayed out.
> I was installing some other software which was going to create a
> database. It gave the a warning that Full text indexing was not
> installed and the software would not function properly.
> If I go into the SQL Setup, I can't add/remove components. The only
> option I have is to Uninstall. I am wondering how I can add full-text
> indexing.
> Thanks for your help,
> Jay
>
> John Kane wrote:
> helpful
> Server
> Server
> often
> database, you
> the FT
> the
> Note, the
> qualify for
> clustered
> disk
> "Full
>
http://spaces.msn.com/members/jtkane/Blog/cns!1pWDBCiDX1uvH5ATJmNCVLPQ!304.entry
> code.
>
|||Thanks John.
Clarification from my previous post: "If I go into the SQL Setup, I
can't add/remove components. =ADThe only option I have is to Uninstall.
" -- ALL other options are grayed out. It is not a matter of them
already being checked. I have no option to check them. It isn't
installed and it won't let me add it.
I am assuming because this is a cluster, components have to be added
differently. Because I have no option to add/remove components under
the custom install. My only option is to Uninstall. (yes - I am
logged in as administrator).
MSSQLServer is running as a domain account and that account is in the
domain admins group.
|||You're welcome, Jay,
Ok, so we take 10 yards and punt (to use a football analogy)... Before I ask
you to un-cluster your servers and re-install SQL Server (a big effort, I
know), I want you to confirm something for me.
Is this SQL Server installed on a Domain Controller or a backup DC? As I've
seen problems with FTS working correctly when installed on a DC or BDC and
with MSSQLServer service startup account being the Domain Administrators
account. If it's not on a DC or BDC, but you are using an account that is a
member of the DOMAIN Administrator group, could you create a separate
DOMAIN\Account and add that account to the local server's Administrators
Group and then using the SQL Enterprise Manager's server property security
tab, change the MSSQLServer service startup account to the newly created
DOMAIN\Account. This change should prompt you to stop & re-start SQL Server
and click yes to this prompt. Then close and re-launch the Enterprise
Manager and see if the Full Text Indexing is still grayed out. If it is not
grayed out, then failover to your Passive node and do the same thing there.
As I've said I've seen this before in non-clustered environments where SQL
Server 2000 was installed on a DC or BDC and the MSSQLServer service
startup account being the Domain Administrators account. The solution in
this case was as I described above or resetting the MSSQLServer service
startup account use LocalSystem or as a last resort move the SQL Server off
the DC or BDC.
Let me know if this successful for you, otherwise, the fallback solution is
to un-cluster your servers and re-install SQL Server :-(
Thanks,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
<jay.griffin@.burke.com> wrote in message
news:1107277007.739900.246620@.z14g2000cwz.googlegr oups.com...
Thanks John.
Clarification from my previous post: "If I go into the SQL Setup, I
can't add/remove components. XThe only option I have is to Uninstall.
" -- ALL other options are grayed out. It is not a matter of them
already being checked. I have no option to check them. It isn't
installed and it won't let me add it.
I am assuming because this is a cluster, components have to be added
differently. Because I have no option to add/remove components under
the custom install. My only option is to Uninstall. (yes - I am
logged in as administrator).
MSSQLServer is running as a domain account and that account is in the
domain admins group.
|||Based on what you are telling me -- I am going to have to uncluster and
re-install. The servers are not a DC. The special user I setup for
the SQL servers is in the local admins group already.
Do you know of any KB articles that would walk me through this without
losing any information?
|||Jay,
Yep, 10 yards & punt... Re-installing a Clustered SQL server is never easy,
but these references may help:
a.. SQL Server 2000 Clustering Whitepaper,
http://www.microsoft.com/SQL/techinf...vercluster.asp
a.. 815431 PRB: Installation of a Named Instance of SQL Server 2000 Virtual
Server http://support.microsoft.com/?id=815431
a.. 325485 WebCast: Microsoft SQL Server 2000 Virtual Server Basic Setup
http://support.microsoft.com/?id=325485
a.. 274446 INF: Upgrade to SQL Server 2000 Failover Solution Recommended for
All... http://support.microsoft.com/?id=274446
a.. 254321 INF: Clustered SQL Server Do's, Don'ts, and Basic Warnings
http://support.microsoft.com/?id=254321
a.. 243218 INF: Installation Order for SQL Server 2000 Enterprise Edition
http://support.microsoft.com/?id=243218
a.. 260758 INF: Frequently Asked Questions - SQL Server 2000 - Failover
Clustering http://support.microsoft.com/?id=260758
Hope this helps!
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
<jay.griffin@.burke.com> wrote in message
news:1107354007.277719.324960@.g14g2000cwa.googlegr oups.com...
> Based on what you are telling me -- I am going to have to uncluster and
> re-install. The servers are not a DC. The special user I setup for
> the SQL servers is in the local admins group already.
> Do you know of any KB articles that would walk me through this without
> losing any information?
>
|||John,
Thank you for all your help on this issue.
Jay

Adding FoxPro to SQL Cluster?

Hi all,
I am the SQL DBA for an organization. We have an active/passive 2-node SQL 2000 cluster running on Windows 2003 Server. So far, it has been very stable (knock wood).
Somebody here wants to add FoxPro as a clustered application onto our (failover) clustered database server. My gut tells me no, partially because I'm not sure if you can cluster FoxPro, and what the implications of running a FoxPro cluster are. Also, I
have not been able to find any information on the Web about implementing, administrating or coding for a FoxPro cluster, while the same information on SQL Server clustering is abundent.
My questions are:
1. Has anyone out there implemented a clustered FoxPro server?
2. If so, have you implemented this on the same cluster as your production SQL Server cluster?
3. Does anyone have any recommendations for or against this type of setup?
4. Can anyone point me in the direction of information that would make the case one way or the other about this proposed implementation?
Thanks in advance!
Cheers,
-m
My first question would be:
Why do they want to do this?
Why would they want to use a FoxPro application in an environment that is
designed for high availablitly?
Theoritically any application can be clustered but logically it does not
make sense to cluster an application that by design is a desktop
application. It seems to be a waste of resources.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Someone within your organisation seems to be getting confused between server products and desktop products. Foxpro is a desktop product. Another way of looking at it is by replacing the word "FoxPro" with "Access", "Word", "Excel" etc and ask yourself t
he same questions again. Desktop applications are not cluster-aware. Some server products are. eg SQL Server 2000, Exchange 2000/2003. Attempting to make a desktop application cluster-aware seems to be a major step in the wrong direction. Your initia
l instincts were correct. Now you just need to point out the differences between cluster-aware applications and non-cluster-aware applications to your management.
If management want high availability with their database platform switch from FoxPro to SQL Server 2000 EE (on a MCS cluster). There is no such thing as a cheap highly available solution in the database space (well I've not seen one yet).

Adding drive dependencies to WIN2k/SQL2k cluster resource

I need to add two additional SAN attached volumes to be dependencies
for my SQL Server Cluster resource. Do I have to restart the cluster
service for this to take affect? Is there another way for the cluster
resource to re initialize it's dependencies without restarting?
If you want to create databases on these drives, you need to add them to the
SQL Server resource dependency list. To do that, you don't need to restart
the cluster service. But you do need to take the SQL Server resource offline,
add the drives as the dependencies, and then bring the SQL Server resource
online.
Linchi
"zoneranger@.gmail.com" wrote:

> I need to add two additional SAN attached volumes to be dependencies
> for my SQL Server Cluster resource. Do I have to restart the cluster
> service for this to take affect? Is there another way for the cluster
> resource to re initialize it's dependencies without restarting?
>

Adding Disks

I would like to add another volume to my two node sql 2005 cluster. From
what i have been reading i need to shut one of the cluster nodes, add
the drive to the cluster then bring the backup node back on line. Am i
missing anything?
Thanks for the help
Noah Hamilton
Sr Systems Administrator
Carpathia Hosting, Inc
21711 Filigree Court, Suite A
Ashburn, VA 20147
voice: (703) 297-4451
Fax: (703) 997 5577
www.carpathiahost.com
Once you have physically connected the disk (or carved a new LUN and
presented it to the host computers), you must create a clustered resource.
Use the cluster admin tool to create a disk resource and map it to the
physical disk. I usually create a temporary resource group to park it in
while I am setting things up. Test failover to make sure all host nodes can
"see" and use the clustered disk.
You then can move the disk into the SQL resource group. Finally, you must
make the SQL Service dependent on the new disk before SQL will use it for
data or logs. This will require stopping the SQL service while the
dependencies are changed.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Noah" <noah@.carpathiahost.com> wrote in message
news:%23$wrjlp2HHA.4584@.TK2MSFTNGP03.phx.gbl...
>I would like to add another volume to my two node sql 2005 cluster. From
>what i have been reading i need to shut one of the cluster nodes, add the
>drive to the cluster then bring the backup node back on line. Am i missing
>anything?
> Thanks for the help
> Noah Hamilton
> Sr Systems Administrator
> Carpathia Hosting, Inc
> 21711 Filigree Court, Suite A
> Ashburn, VA 20147
> voice: (703) 297-4451
> Fax: (703) 997 5577
> www.carpathiahost.com
>
|||Thanks for the help. I have the new drives up and running now.
Appreciate all the help.
Geoff N. Hiten wrote:
> Once you have physically connected the disk (or carved a new LUN and
> presented it to the host computers), you must create a clustered
> resource. Use the cluster admin tool to create a disk resource and map
> it to the physical disk. I usually create a temporary resource group to
> park it in while I am setting things up. Test failover to make sure all
> host nodes can "see" and use the clustered disk.
> You then can move the disk into the SQL resource group. Finally, you
> must make the SQL Service dependent on the new disk before SQL will use
> it for data or logs. This will require stopping the SQL service while
> the dependencies are changed.
>

adding disk

I have to add SAN space to an existing cluster. what are the steps?
thanks
Create LUN on SAN
Present LUN to Host computers via SAN Masking software
On one host:
Rescan disks in Disk Administrator on host. (may require host reboot)
Partition disk (may require offsetting the start of the partition to align
LUN boundaries)
Create disk resource on temporary cluster group.
Rescan disks on remaining host nodes (again, ay require reboot of specific
nodes.
Test disk access on all nodes, shifting disk resource as necessary.
On the host for the SQL Instance you wish to add the disk to:
Using Cluster Administrator, Stop the SQL Service, leave the remaining
resources online
Make the SQL service dependent on the new disk resource (see existing disk
resource dependencies)
Start SQL Service using Cluster Administrator
Add folders and data.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"vision" <vision@.discussions.microsoft.com> wrote in message
news:192B4B9C-D1BB-4A46-9322-771B4C2F3987@.microsoft.com...
>I have to add SAN space to an existing cluster. what are the steps?
> thanks
|||thanks'
I am not sure what a temporary disk resource is.
"Geoff N. Hiten" wrote:

> Create LUN on SAN
> Present LUN to Host computers via SAN Masking software
> On one host:
> Rescan disks in Disk Administrator on host. (may require host reboot)
> Partition disk (may require offsetting the start of the partition to align
> LUN boundaries)
> Create disk resource on temporary cluster group.
> Rescan disks on remaining host nodes (again, ay require reboot of specific
> nodes.
> Test disk access on all nodes, shifting disk resource as necessary.
> On the host for the SQL Instance you wish to add the disk to:
> Using Cluster Administrator, Stop the SQL Service, leave the remaining
> resources online
> Make the SQL service dependent on the new disk resource (see existing disk
> resource dependencies)
> Start SQL Service using Cluster Administrator
> Add folders and data.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "vision" <vision@.discussions.microsoft.com> wrote in message
> news:192B4B9C-D1BB-4A46-9322-771B4C2F3987@.microsoft.com...
>
>
|||Temporary resource group, not temporary disk resource.
This is just a group you made up to hold the resource while you are testing
it. Once you have confirmed it moves between hosts as you expect, you moe
the disk resource into the SQL group before setting the dependencies.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"vision" <vision@.discussions.microsoft.com> wrote in message
news:9CDCB135-2CBF-417E-B158-FC3BA891D421@.microsoft.com...[vbcol=seagreen]
> thanks'
> I am not sure what a temporary disk resource is.
> "Geoff N. Hiten" wrote:
|||If you need to replace the disk, or want to swap it out, use the Cluster
Recovery Utility to change the resource dependencies. Then you copy the
contents of the old volume to the new and swap the drive letters.
The SQL Server resources will have to be offline during this process, but
you won't have to hack the registry to refer to a new drive letter.
The download contains a reference document.
http://www.microsoft.com/downloads/details.aspx?familyid=2BE7EBF0-A408-4232-9353-64AAFD65306D&displaylang=en
Sincerely,
Anthony Thomas

"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:eNEP0ieAHHA.4472@.TK2MSFTNGP03.phx.gbl...
> Temporary resource group, not temporary disk resource.
> This is just a group you made up to hold the resource while you are
testing
> it. Once you have confirmed it moves between hosts as you expect, you moe
> the disk resource into the SQL group before setting the dependencies.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "vision" <vision@.discussions.microsoft.com> wrote in message
> news:9CDCB135-2CBF-417E-B158-FC3BA891D421@.microsoft.com...
>

adding CAL for sql server on cluster

Hi Guys,
i am using sql server 2000 on windows 2000 cluster with
150 concurrent license . now i want to add 50 more licence.
do i have to add this for both nodes?
what is the procedure to do this ? is it using licensing
manager in control panel?
PLS advice me
> 150 concurrent license . now i want to add 50 more licence.
SQL CALs are not "concurrent" licences. You need a CAL per device or user
regardless of how many connections are made concurrently. Under the
Server/CAL licensing model you only need one licence per device or user even
if they connect to multiple servers, whether clustered or otherwise.
Refer to:
http://www.microsoft.com/sql/howtobuy/default.asp
David Portas
SQL Server MVP
|||Hi,
so even if i have 10 connections from one work stations it
will consider as only one CAL.?
but it in sql 7.0 it was concurrent license
[vbcol=seagreen]
>--Original Message--
licence.
>SQL CALs are not "concurrent" licences. You need a CAL
per device or user
>regardless of how many connections are made concurrently.
Under the
>Server/CAL licensing model you only need one licence per
device or user even
>if they connect to multiple servers, whether clustered or
otherwise.
>Refer to:
>http://www.microsoft.com/sql/howtobuy/default.asp
>--
>David Portas
>SQL Server MVP
>--
>
>.
>
|||> so even if i have 10 connections from one work stations it
> will consider as only one CAL.?
Yes. Conversely if you have 100 workstations you need 100 device CALs even
if no more than 50 are ever connected concurrently.

> but it in sql 7.0 it was concurrent license
From the Licensing FAQ:
Q. Do you still offer per-server (concurrency) CALs?
A. No. SQL Server 2000 is only available by means of a Server plus device
CAL, Server plus user CAL, or a Processor license.
David Portas
SQL Server MVP

adding CAL for sql server on cluster

Hi Guys,
i am using sql server 2000 on Windows 2000 cluster with
150 concurrent license . now i want to add 50 more licence.
do i have to add this for both nodes?
what is the procedure to do this ? is it using licensing
manager in control panel?
PLS advice me> 150 concurrent license . now i want to add 50 more licence.
SQL CALs are not "concurrent" licences. You need a CAL per device or user
regardless of how many connections are made concurrently. Under the
Server/CAL licensing model you only need one licence per device or user even
if they connect to multiple servers, whether clustered or otherwise.
Refer to:
http://www.microsoft.com/sql/howtobuy/default.asp
David Portas
SQL Server MVP
--|||Hi,
so even if i have 10 connections from one work stations it
will consider as only one CAL.?
but it in sql 7.0 it was concurrent license

>--Original Message--
licence.[vbcol=seagreen]
>SQL CALs are not "concurrent" licences. You need a CAL
per device or user
>regardless of how many connections are made concurrently.
Under the
>Server/CAL licensing model you only need one licence per
device or user even
>if they connect to multiple servers, whether clustered or
otherwise.
>Refer to:
>http://www.microsoft.com/sql/howtobuy/default.asp
>--
>David Portas
>SQL Server MVP
>--
>
>.
>|||> so even if i have 10 connections from one work stations it
> will consider as only one CAL.?
Yes. Conversely if you have 100 workstations you need 100 device CALs even
if no more than 50 are ever connected concurrently.

> but it in sql 7.0 it was concurrent license
From the Licensing FAQ:
Q. Do you still offer per-server (concurrency) CALs?
A. No. SQL Server 2000 is only available by means of a Server plus device
CAL, Server plus user CAL, or a Processor license.
David Portas
SQL Server MVP
--

Adding a third NODE to an existing SQl server 2000 CLUSTER

Currently we have an ACTIVE/ACTIVE SQL Server 2000 cluster in our production
environment. The current configuration is such that each node has a dedicated
server hardware. Lets call one of the ACTIVE nodes as NODE1 and the other
ACTIVE node as NODE2. We are in the planning stages of a SQL Server 2005,
side by side upgrade. Also we are planning to introduce a new server hardware
into the equation to help the upgrade process so that the performance is not
affected. The way we want to use the new SQl server hardware is to have both
a SQl Server 2000 instance and a SQl Server 2005 instance in this new
hardware, lets call this NODE3. The databases for all the SQl servers will be
presented via a SAN.
(1)NODE2 will have another instance of SQl 2005 installed into it.
(2)The SQL 2005 instance of the NODE2 needs to be clustered with the SQL
2005 instance in the NODE3 as an ACTIVE-ACTIVE cluster.
(3)The SQL 2000 instance of the NODE2 then needs to be clustered with the
SQL 2000 instance in the NODE 1.
If the above was technically possible then the SQl 2005 databases will be
load balanced between NODE2 and NODE3 and the SQL 2000 databases will be load
balanced between NODE 1 and NODE 2. Eventually when we move all of the SQl
2000 databases to SQl 2005 then the SQl 2000 Server instances will be
upgraded to SQl 2005 as well.
So eventually we would end up with 2 ACTIVE/ACTIVE cluster of SQl 2005
Servers in 3 dedicated server hardware.
Am I dreaming here ? Or is this technically feasible. Any thoughts are
welcome. Any other alternatives are also welcome.
Many Thanks in advance.
RK
Active/Active does not share data across nodes. Technically, Active/Active
does not exist. The term described a unique configuration that existed for
SQL 7.0 when nodes were not equal peers in cluster. There is no load
balancing or shared databases across nodes in MSCS clustering.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"RK" <RK@.discussions.microsoft.com> wrote in message
news:C6A544B9-0573-4CE4-829F-D42727C52134@.microsoft.com...
> Currently we have an ACTIVE/ACTIVE SQL Server 2000 cluster in our
> production
> environment. The current configuration is such that each node has a
> dedicated
> server hardware. Lets call one of the ACTIVE nodes as NODE1 and the other
> ACTIVE node as NODE2. We are in the planning stages of a SQL Server 2005,
> side by side upgrade. Also we are planning to introduce a new server
> hardware
> into the equation to help the upgrade process so that the performance is
> not
> affected. The way we want to use the new SQl server hardware is to have
> both
> a SQl Server 2000 instance and a SQl Server 2005 instance in this new
> hardware, lets call this NODE3. The databases for all the SQl servers will
> be
> presented via a SAN.
> (1)NODE2 will have another instance of SQl 2005 installed into it.
> (2)The SQL 2005 instance of the NODE2 needs to be clustered with the SQL
> 2005 instance in the NODE3 as an ACTIVE-ACTIVE cluster.
> (3)The SQL 2000 instance of the NODE2 then needs to be clustered with the
> SQL 2000 instance in the NODE 1.
> If the above was technically possible then the SQl 2005 databases will be
> load balanced between NODE2 and NODE3 and the SQL 2000 databases will be
> load
> balanced between NODE 1 and NODE 2. Eventually when we move all of the SQl
> 2000 databases to SQl 2005 then the SQl 2000 Server instances will be
> upgraded to SQl 2005 as well.
> So eventually we would end up with 2 ACTIVE/ACTIVE cluster of SQl 2005
> Servers in 3 dedicated server hardware.
> Am I dreaming here ? Or is this technically feasible. Any thoughts are
> welcome. Any other alternatives are also welcome.
> Many Thanks in advance.
> RK
>
>
|||Hi,
Thanks for that. When I said shared SAN I didnt mean shared databases
between the cluster nodes. Again when I said load balancing what I intended
there was rather than have an Active/passive configuration and have all
databases managed by one instance of SQl Server 2000, in Active/Active it
will be managed by 2 SQL servers. But still you havent answered my main
question whether the new configuration as mentioned below is possible
technically ?
Many thanks in advance.
"Geoff N. Hiten" wrote:

> Active/Active does not share data across nodes. Technically, Active/Active
> does not exist. The term described a unique configuration that existed for
> SQL 7.0 when nodes were not equal peers in cluster. There is no load
> balancing or shared databases across nodes in MSCS clustering.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "RK" <RK@.discussions.microsoft.com> wrote in message
> news:C6A544B9-0573-4CE4-829F-D42727C52134@.microsoft.com...
>
|||You can have a three node cluster with multiple SQL instances of differing
versions. You can also set preferred node order for each instance
independently. Finally, you can set each instance to run on only a subset
of the nodes, but I would recommend allowing all instances on all nodes,
just to cover secondary failure possibilities.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"RK" <RK@.discussions.microsoft.com> wrote in message
news:C2CBECB3-A855-48E9-AAF2-FF2700DFEAD1@.microsoft.com...[vbcol=seagreen]
> Hi,
> Thanks for that. When I said shared SAN I didnt mean shared databases
> between the cluster nodes. Again when I said load balancing what I
> intended
> there was rather than have an Active/passive configuration and have all
> databases managed by one instance of SQl Server 2000, in Active/Active it
> will be managed by 2 SQL servers. But still you havent answered my main
> question whether the new configuration as mentioned below is possible
> technically ?
> Many thanks in advance.
>
> "Geoff N. Hiten" wrote:
|||You can have a three node cluster with multiple SQL instances of differing
versions. You can also set preferred node order for each instance
independently. Finally, you can set each instance to run on only a subset
of the nodes, but I would recommend allowing all instances on all nodes,
just to cover secondary failure possibilities.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"RK" <RK@.discussions.microsoft.com> wrote in message
news:C2CBECB3-A855-48E9-AAF2-FF2700DFEAD1@.microsoft.com...[vbcol=seagreen]
> Hi,
> Thanks for that. When I said shared SAN I didnt mean shared databases
> between the cluster nodes. Again when I said load balancing what I
> intended
> there was rather than have an Active/passive configuration and have all
> databases managed by one instance of SQl Server 2000, in Active/Active it
> will be managed by 2 SQL servers. But still you havent answered my main
> question whether the new configuration as mentioned below is possible
> technically ?
> Many thanks in advance.
>
> "Geoff N. Hiten" wrote:
|||Hi Geoff,
What I intended to acheive with this was TWO 2 node clusters from the 4 SQl
server instances spread around 3 servers. One cluster being a SQL 2000 based
and the other one based on SQL 2005. Possible still ?
Cheers
Rajeev
"Geoff N. Hiten" wrote:

> You can have a three node cluster with multiple SQL instances of differing
> versions. You can also set preferred node order for each instance
> independently. Finally, you can set each instance to run on only a subset
> of the nodes, but I would recommend allowing all instances on all nodes,
> just to cover secondary failure possibilities.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "RK" <RK@.discussions.microsoft.com> wrote in message
> news:C2CBECB3-A855-48E9-AAF2-FF2700DFEAD1@.microsoft.com...
>
|||No. Each machine can participate in one and only one cluster. You can have
a single cluster with two SQL instances and three host nodes.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"RK" <RK@.discussions.microsoft.com> wrote in message
news:C91E92BB-0C97-44CE-AC35-D426D9C92F5F@.microsoft.com...[vbcol=seagreen]
> Hi Geoff,
> What I intended to acheive with this was TWO 2 node clusters from the 4
> SQl
> server instances spread around 3 servers. One cluster being a SQL 2000
> based
> and the other one based on SQL 2005. Possible still ?
> Cheers
> Rajeev
> "Geoff N. Hiten" wrote: