Not able to create the db and restore the db in cluster environment

  • Hi

    We have created a new sql cluster server.After configuration we have created a db on the server.

    After some days we tried to create the db and restore the db.But we are getting the below errors.

    While restoring from a drive observed below error.

    Error:cannot access the specified path or file on th eserver.verify that you have necessary security privileges and that the path or file exist

    While creating new db

    cannot use file 'path:*****.mdf' for cluster server.only formatted files on which the cluster resource of the server has a dependency can be used.Either the disk resource containing the file is not present in the cluster group or the cluster resource of the sql doesnot have a dependency on it.

    create database failed .some file names listed could not be created.check related errors.(microsoft sql server,error:5184)

    On active node c drive and quorum drives are offline.On passive node both are online.Remaining other drives are in online on active node.We have kept the user and sys db files on other drives.

    Is this causing issue.please share if there are any links related to this issue.

  • Here are the errors

    Msg 5184, Level 16, State 2, Line 1

    Cannot use file '.mdf' for clustered server. Only formatted files on which the cluster resource of the server has a dependency can be used. Either the disk resource containing the file is not present in the cluster group or the cluster resource of the Sql Server does not have a dependency on it.

    Msg 3156, Level 16, State 3, Line 1

    File '***' cannot be restored to '***.mdf'. Use WITH MOVE to identify a valid location for the file.

    Msg 5184, Level 16, State 2, Line 1

    Cannot use file '***.ldf' for clustered server. Only formatted files on which the cluster resource of the server has a dependency can be used. Either the disk resource containing the file is not present in the cluster group or the cluster resource of the Sql Server does not have a dependency on it.

    Msg 3156, Level 16, State 3, Line 1

    File '**log' cannot be restored to '***.ldf'. Use WITH MOVE to identify a valid location for the file.

    Msg 3119, Level 16, State 1, Line 1

    Problems were identified while planning for the RESTORE statement. Previous messages provide details.

    Msg 3013, Level 16, State 1,

    Line 1 RESTORE DATABASE is terminating abnormally.

    When i executed the below query its is not showing ant drives.

    select * from sys.dm_io_cluster_shared_drives.

  • Look at the drive letter(s) in your restore error messages.

    Then go into the cluster administrator and see if those drive letters are in the SQL disk group.

    If those specific drive letters are not in the SQL disk group then add them and the restore should work.

    RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

  • Minto Minto(quendans) (6/11/2014)

    On active node c drive and quorum drives are offline.On passive node both are online.Remaining other drives are in online on active node.We have kept the user and sys db files on other drives.

    If I understand your statement, you are working with a 2 node cluster (server1, server2). If the quorum drives show offline on server1, then this is no longer the active node, it is server2. If however server2 is running the SQL Server instance and the drives for the instance did not failover to server2 (meaning they are still attached to server1), then this is likely the issue. Manually fail them over and so all resources are active on server2.

    If that resolves the issue you then need to configure your SQL Server resource groups to include the associated shared drives for your database files. This will tell the cluster service to move the drives with the instance if it fails over.

    Shawn Melton
    Twitter: @wsmelton
    Blog: wsmelton.github.com
    Github: wsmelton

  • Shawn Melton (6/12/2014)


    If the quorum drives show offline on server1, then this is no longer the active node, it is server2.

    It doesnt matter where the quorum drive is online, this does not dictate the active node for a clustered application. The location of the cluster group defines the active node for that application, it is possible for the quorum to be up on node1 but the clustered sql server group be up on node2.

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply