Can't get new LUN/Logical Drive visible from within SQL Server on cluster.

We have had a working SQL Server 2000 SP3 (default instance) on two node MS
Windows 2000 Advanced Server with MS Cluster servcie working for over a year
now.
The shared Q: and E: drives are actually two seperate LUNS from a SAN
connected via Host Bus Adapters..
Recently, needed another logical drive. Added another LUN from the SAN.
Configured it as basic disk, drive letter F: It show up in Disk Manager
exactly like the pre-existing E: drive in terms of attribute values.
It is a working a normal drive on the primary node.
Using the cluster administrator, it was added as a physical disk resource
and added to the iManage SQL Cluster Group, the same as the E: drive.
It shows up as online and owned by the primary node where the SQL Server is
active.
However, it does not show up with the Enterprise Manage for the SQL Server.
Only E: is showing. Have even rebooted the nodes for the cluster.
The logical drive F: is available for all other uses, but it cannot be seen
by the SQL Server.
Scott Lord
Willkie Farr & Gallagher LLP
New York, New York
slord@.willkie.com
you have to add new drive as a SQL Server Dependency in cluster administrator. once you added into sqlserver dependency then enterprise mangager see the drive.
Regards
Ram
Systems SQL DBA|||I for get tell one more step . you have to add resource in Cluster administrator.
Regards
Ram

Quote:

Originally posted by yvr4
you have to add new drive as a SQL Server Dependency in cluster administrator. once you added into sqlserver dependency then enterprise mangager see the drive.
Regards
Ram
Systems SQL DBA

|||Have you made it a dependency of the SQL Server group?
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com
..
"Scott Lord" <nomail@.nomail.com> wrote in message
news:ehHkGQKCFHA.2404@.TK2MSFTNGP15.phx.gbl...
We have had a working SQL Server 2000 SP3 (default instance) on two node MS
Windows 2000 Advanced Server with MS Cluster servcie working for over a year
now.
The shared Q: and E: drives are actually two seperate LUNS from a SAN
connected via Host Bus Adapters..
Recently, needed another logical drive. Added another LUN from the SAN.
Configured it as basic disk, drive letter F: It show up in Disk Manager
exactly like the pre-existing E: drive in terms of attribute values.
It is a working a normal drive on the primary node.
Using the cluster administrator, it was added as a physical disk resource
and added to the iManage SQL Cluster Group, the same as the E: drive.
It shows up as online and owned by the primary node where the SQL Server is
active.
However, it does not show up with the Enterprise Manage for the SQL Server.
Only E: is showing. Have even rebooted the nodes for the cluster.
The logical drive F: is available for all other uses, but it cannot be seen
by the SQL Server.
Scott Lord
Willkie Farr & Gallagher LLP
New York, New York
slord@.willkie.com
|||Thanks to Tom Moreau and yvr4 for their answers. I am pretty sure they both
identified the problem, I haven't been able to successfully test their
solution.
I had not added it as a dependency for the SQL Server. I only had it added
it to the SQL Cluster Group. I just tried adding it as a dependency to the
SQL Server.
FYI: The disk resource F: is online to the primary node and the SQL Server
is and online to the primary node.
In the cluster administrator, simply pulling up the properties to the SQL
Server and going to the Dependencies tab showed the F: drive on the left as
an available resource to be added as a dependency. I highlighted the F:
drive and tried to add it. I got a slightly ambiguous error message which I
will also type the text from the error message box.
Message box title: Cluster Administrator
Yellow triangle with exclamation point icon.
An error occurred attempting to add 'Disk F:' as a dependency of 'SQL
Server':
The operation could not be completed because the cluster resource is online.
Error ID: 5019 (0000139b).
This is a production environment: I am concerned about two things. Which
resource, the F: drive or the SQL Server is the error message meaning when
it say 'because the cluster resource is online' I know that I would like
for it to mean the disk drive, but I am modifying the SQL Server dependency
tree, so it is possible it means the SQL Server. I can't take that offline
except during a maintenance window. Also, if I simply take the disk drive
F: resource offline in the cluster administrator window in order to add it
to the SQL Server dependency tree, will it cause a fail-over of the SQL
Server since the newly defined dependency, F: disk drive resource, is not
online. That is what the dependency tree is for, isn't it.
I hope the answer is simply, take the disk drive F: resource offline in
cluster administrator, add it as a dependency to the SQL Server, and it will
either come online itself or I can manually bring it online, without the SQL
Server failing over.
Alternatively, I can accept needing to take the SQL Server offline in the
cluster administrator, having the disk drive F: resource online, adding it
as a dependency to the SQL Server and bringing the SQL Server online.
Sorry about these additional questions, but I thought the error message was
a little ambiguous, and I am concerned about adding an offline resource as a
dependency if it will cause a fail-over in our production environment. We
do not have a test cluster to try this on.
Scott Lord
Willkie Farr & Gallagher LLP
New York, New York
slord@.willkie.com
"yvr4" <yvr4.1jt3a0@.mail.mcse.ms> wrote in message
news:yvr4.1jt3a0@.mail.mcse.ms...
> you have to add new drive as a SQL Server Dependency in cluster
> administrator. once you added into sqlserver dependency then enterprise
> mangager see the drive.
> Regards
> Ram
> Systems SQL DBA
>
> --
> yvr4
> Posted via http://www.mcse.ms
> View this thread: http://www.mcse.ms/message1393040.html
>
|||That error message is correct. You must take the SQL Server resource
offline to change its dependencies.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Scott Lord" <nomail@.nomail.com> wrote in message
news:e97ziSUCFHA.2384@.TK2MSFTNGP14.phx.gbl...
> Thanks to Tom Moreau and yvr4 for their answers. I am pretty sure they
both
> identified the problem, I haven't been able to successfully test their
> solution.
> I had not added it as a dependency for the SQL Server. I only had it
added
> it to the SQL Cluster Group. I just tried adding it as a dependency to
the
> SQL Server.
> FYI: The disk resource F: is online to the primary node and the SQL
Server
> is and online to the primary node.
> In the cluster administrator, simply pulling up the properties to the SQL
> Server and going to the Dependencies tab showed the F: drive on the left
as
> an available resource to be added as a dependency. I highlighted the F:
> drive and tried to add it. I got a slightly ambiguous error message which
I
> will also type the text from the error message box.
> --
> Message box title: Cluster Administrator
> Yellow triangle with exclamation point icon.
> An error occurred attempting to add 'Disk F:' as a dependency of 'SQL
> Server':
> The operation could not be completed because the cluster resource is
online.
> Error ID: 5019 (0000139b).
> --
> This is a production environment: I am concerned about two things. Which
> resource, the F: drive or the SQL Server is the error message meaning when
> it say 'because the cluster resource is online' I know that I would like
> for it to mean the disk drive, but I am modifying the SQL Server
dependency
> tree, so it is possible it means the SQL Server. I can't take that
offline
> except during a maintenance window. Also, if I simply take the disk drive
> F: resource offline in the cluster administrator window in order to add it
> to the SQL Server dependency tree, will it cause a fail-over of the SQL
> Server since the newly defined dependency, F: disk drive resource, is not
> online. That is what the dependency tree is for, isn't it.
> I hope the answer is simply, take the disk drive F: resource offline in
> cluster administrator, add it as a dependency to the SQL Server, and it
will
> either come online itself or I can manually bring it online, without the
SQL
> Server failing over.
> Alternatively, I can accept needing to take the SQL Server offline in the
> cluster administrator, having the disk drive F: resource online, adding it
> as a dependency to the SQL Server and bringing the SQL Server online.
> Sorry about these additional questions, but I thought the error message
was
> a little ambiguous, and I am concerned about adding an offline resource as
a
> dependency if it will cause a fail-over in our production environment. We
> do not have a test cluster to try this on.
> Scott Lord
> Willkie Farr & Gallagher LLP
> New York, New York
> slord@.willkie.com
> "yvr4" <yvr4.1jt3a0@.mail.mcse.ms> wrote in message
> news:yvr4.1jt3a0@.mail.mcse.ms...
>
|||Thank you Geoff.
I will schedule the change to the dependency tree for SQL Server to occur
during a maintenance window.
Scott
"Geoff N. Hiten" <SRDBA@.Careerbuilder.com> wrote in message
news:%23mHvubUCFHA.4004@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> That error message is correct. You must take the SQL Server resource
> offline to change its dependencies.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Scott Lord" <nomail@.nomail.com> wrote in message
> news:e97ziSUCFHA.2384@.TK2MSFTNGP14.phx.gbl...
> both
> added
> the
> Server
SQL[vbcol=seagreen]
> as
which[vbcol=seagreen]
> I
> online.
Which[vbcol=seagreen]
when[vbcol=seagreen]
like[vbcol=seagreen]
> dependency
> offline
drive[vbcol=seagreen]
it[vbcol=seagreen]
not[vbcol=seagreen]
> will
> SQL
the[vbcol=seagreen]
it[vbcol=seagreen]
> was
as[vbcol=seagreen]
> a
We[vbcol=seagreen]
enterprise
>