Add SQL Server 2005 nodes to a SQL2000 cluster

I am trying to add 2 2005 nodes to an existing cluster that has 2xSQL2000
nodes. The cluster is using a SAN with - T, U drives as data and log in node
1, and - V, W drives as data and log in node 2
I want to add SQL2005 nodes, using these drives. When I start the install -
using wizard - I check the box to create a new virtual server (If I leave it
unchecked the install is not cluster aware)
When I get to the step re cluster group resource, I cannot use any of the
drives as they are in use by the existing virtual server.
I tried making a new group, but when I do that I cannot assign the existing
drives to the new groups.
How does one normally acheive this without rebuilding the SAN to add in
extra partitions? Has anyone seen any effective resources about how to do
this?
Thanks
Geoff Tanner
YOu can't add SQL2005 nodes to a SQL2000 cluster and keep two nodes SQL2005
and the other two nodes SQL2000. It's not supported, and makes no business
sense.
Linchi
"Geoff Tanner" wrote:

> I am trying to add 2 2005 nodes to an existing cluster that has 2xSQL2000
> nodes. The cluster is using a SAN with - T, U drives as data and log in node
> 1, and - V, W drives as data and log in node 2
> I want to add SQL2005 nodes, using these drives. When I start the install -
> using wizard - I check the box to create a new virtual server (If I leave it
> unchecked the install is not cluster aware)
> When I get to the step re cluster group resource, I cannot use any of the
> drives as they are in use by the existing virtual server.
> I tried making a new group, but when I do that I cannot assign the existing
> drives to the new groups.
> How does one normally acheive this without rebuilding the SAN to add in
> extra partitions? Has anyone seen any effective resources about how to do
> this?
> Thanks
> Geoff Tanner

Add SAN Disk Resource to Active/Active SQL cluster

Looking to see if I am missing any steps below to adding a SAN disk
resource to an Active/Active SQL cluster:
-Create Volumes
-Present LUNs to both Nodes
-Failover Cluster Groups to Node2
-On Node1
Disable ClusDisk
Disable Cluster Services
Reboot Node1
Rescan for hardware changes
Write the disk signature
Set disk to basic
Create Partition
Assign Drive Letter
Enable ClusDisk
Enable Cluster Services
Reboot Node1
-On Node2
Failover Cluster Groups to Node1
Disable ClusDisk
Disable Cluster Services
Reboot Node2
Rescan for hardware changes
Assign Drive Letter
Enable ClusDisk
Enable Cluster Services
Reboot Node2
-Assign disk resource to Cluster Groups
-On Node1
Take SQL Server Resource offline
Add SQL Server Resource dependency to disk resource
Bring SQL Server Resource online
-On Node2
Repeat above
-Test failover
Thanks,
Ian in SD
With Windows 2003 as the host, you may be able to skip some of the reboots.
You can rescan the disk list and pick up newly added disks. I have never
had to disable or stop the cluster service to pick up new disks. I do make
sure and do all the work on a node that does not currently host any cluster
resources. Once I am done, I can rescan the disk list on the other node(s)
and failover at will. If you have the downtime, the reboots won't hurt, but
they may not be necessary.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
<theredmiata@.hotmail.com> wrote in message
news:1142967852.423752.294080@.i39g2000cwa.googlegr oups.com...
> Looking to see if I am missing any steps below to adding a SAN disk
> resource to an Active/Active SQL cluster:
>
> -Create Volumes
> -Present LUNs to both Nodes
> -Failover Cluster Groups to Node2
> -On Node1
> Disable ClusDisk
> Disable Cluster Services
> Reboot Node1
> Rescan for hardware changes
> Write the disk signature
> Set disk to basic
> Create Partition
> Assign Drive Letter
> Enable ClusDisk
> Enable Cluster Services
> Reboot Node1
> -On Node2
> Failover Cluster Groups to Node1
> Disable ClusDisk
> Disable Cluster Services
> Reboot Node2
> Rescan for hardware changes
> Assign Drive Letter
> Enable ClusDisk
> Enable Cluster Services
> Reboot Node2
> -Assign disk resource to Cluster Groups
> -On Node1
> Take SQL Server Resource offline
> Add SQL Server Resource dependency to disk resource
> Bring SQL Server Resource online
> -On Node2
> Repeat above
> -Test failover
> Thanks,
> Ian in SD
>
|||Thanks for the reply Geoff. This the first time for this process as we
are trying to split the file groups and would like to have each group
on a seperate volume.

add linked server problem

Hi, there,
I have two SQL Server 2000, which are SQLA -- with SAN connected; SQLB --
just a bald SQL Server.
I want to set up linked server from SQLA , so I can run query like "select *
from SQLB.dbname.dbo.tablename". The command I use is
sp_addlinkedserver @.server = 'SQLB'
After I ran this code, I span the "Linked servers" node of Enterprise
Manager, I saw an image of a linked server named "SQLB". Then I run the
query "select * from SQLB.dbname.dbo.tablename" from Query Analyzer of
SQLA, I got the following errors
Server: Msg 17, Level 16, State 1, Line 1
SQL Server does not exist or access denied.
I'm the system administrator of the two servers, and the account I ran the
query is sys admin account. I don't know why the command failed. I drop the
linked server and readd the linked server again. I got the same result.
Who can help a bit?
Thanks so much in advance,
JamieMake very sure that the folders involved (db location, etc) have full
read/write/execute access for the login account.
Randall Arnold
"Jamie" <gsadd@.yahoo.com> wrote in message
news:O5ALGyfIGHA.1132@.TK2MSFTNGP10.phx.gbl...
> Hi, there,
> I have two SQL Server 2000, which are SQLA -- with SAN connected; SQLB --
> just a bald SQL Server.
> I want to set up linked server from SQLA , so I can run query like "select
> * from SQLB.dbname.dbo.tablename". The command I use is
> sp_addlinkedserver @.server = 'SQLB'
> After I ran this code, I span the "Linked servers" node of Enterprise
> Manager, I saw an image of a linked server named "SQLB". Then I run the
> query "select * from SQLB.dbname.dbo.tablename" from Query Analyzer of
> SQLA, I got the following errors
> Server: Msg 17, Level 16, State 1, Line 1
> SQL Server does not exist or access denied.
> I'm the system administrator of the two servers, and the account I ran the
> query is sys admin account. I don't know why the command failed. I drop
> the linked server and readd the linked server again. I got the same
> result.
> Who can help a bit?
> Thanks so much in advance,
> Jamie
>

add linked server problem

Hi, there,
I have two SQL Server 2000, which are SQLA -- with SAN connected; SQLB --
just a bald SQL Server.
I want to set up linked server from SQLA , so I can run query like "select *
from SQLB.dbname.dbo.tablename". The command I use is
sp_addlinkedserver @.server = 'SQLB'
After I ran this code, I span the "Linked servers" node of Enterprise
Manager, I saw an image of a linked server named "SQLB". Then I run the
query "select * from SQLB.dbname.dbo.tablename" from Query Analyzer of
SQLA, I got the following errors
Server: Msg 17, Level 16, State 1, Line 1
SQL Server does not exist or access denied.
I'm the system administrator of the two servers, and the account I ran the
query is sys admin account. I don't know why the command failed. I drop the
linked server and readd the linked server again. I got the same result.
Who can help a bit?
Thanks so much in advance,
Jamie
Make very sure that the folders involved (db location, etc) have full
read/write/execute access for the login account.
Randall Arnold
"Jamie" <gsadd@.yahoo.com> wrote in message
news:O5ALGyfIGHA.1132@.TK2MSFTNGP10.phx.gbl...
> Hi, there,
> I have two SQL Server 2000, which are SQLA -- with SAN connected; SQLB --
> just a bald SQL Server.
> I want to set up linked server from SQLA , so I can run query like "select
> * from SQLB.dbname.dbo.tablename". The command I use is
> sp_addlinkedserver @.server = 'SQLB'
> After I ran this code, I span the "Linked servers" node of Enterprise
> Manager, I saw an image of a linked server named "SQLB". Then I run the
> query "select * from SQLB.dbname.dbo.tablename" from Query Analyzer of
> SQLA, I got the following errors
> Server: Msg 17, Level 16, State 1, Line 1
> SQL Server does not exist or access denied.
> I'm the system administrator of the two servers, and the account I ran the
> query is sys admin account. I don't know why the command failed. I drop
> the linked server and readd the linked server again. I got the same
> result.
> Who can help a bit?
> Thanks so much in advance,
> Jamie
>