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

Discussion in 'microsoft.public.sqlserver.clustering' started by Scott Lord, Feb 1, 2005.

  1. Scott Lord

    Scott Lord Guest

    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
     
    Scott Lord, Feb 1, 2005
    #1
    1. Advertisements

  2. Scott Lord

    Tom Moreau Guest

    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
    ..
    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
     
    Tom Moreau, Feb 2, 2005
    #2
    1. Advertisements

  3. Scott Lord

    yvr4 Guest

    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, Feb 2, 2005
    #3
  4. Scott Lord

    yvr4 Guest

    I for get tell one more step . you have to add resource in Cluster
    administrator.

    Regards
     
    yvr4, Feb 2, 2005
    #4
  5. Scott Lord

    Scott Lord Guest

    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
     
    Scott Lord, Feb 2, 2005
    #5
  6. That error message is correct. You must take the SQL Server resource
    offline to change its dependencies.
     
    Geoff N. Hiten, Feb 2, 2005
    #6
  7. Scott Lord

    Scott Lord Guest

    Thank you Geoff.

    I will schedule the change to the dependency tree for SQL Server to occur
    during a maintenance window.

    Scott
     
    Scott Lord, Feb 2, 2005
    #7
  8. Scott Lord

    mihir Guest

    mihir, May 20, 2009
    #8
  9. Scott Lord

    frankm Guest

    Have you:
    1) added that dirve / LUN to the SQL Server resource group.
    then
    2) Have you added the drive / LUN to the dependency on the SQL Server
    resource itself.
     
    frankm, May 20, 2009
    #9
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.