problem with moving .ldf file from one wdrive to another on clustered server?

  • i just tried to move a .ldf file from a drive to another and i got this message when i gave the sp_attach command

    Cannot use file 'F:\XXXX.LDF' for clustered server. Only formatted files on which the cluster resource of the server has a dependency can be used.

     

    HELP. need to move the ldf files off the drive that the mdf files live on

    [font="Comic Sans MS"][/font]It is what it is.

  • You may need your cluster administrator's help. Is Drive F in the same cluster group as the SQL Server resource? Is the SQL Server resource set to depend on Drive F? Both of these must be true in order to be able to put any database file on the drive. The reason is because SQL Server has to be assured it has access to the drives any of its database files reside on. If the SQL Server resource isn't dependent on a given drive, SQL Server won't let you put a database file on that drive.

    K. Brian Kelley
    @kbriankelley

  • this is weird, but this is inherited mess. i mean, the cluster was created a year ago and sqlserver was installed on it. since the person that creatd it is no longer here..... no one knows anything.. so i dont have a cluster administrator . and no one knows or has an anwer to any of my questions.

    [font="Comic Sans MS"][/font]It is what it is.

  • Like Brain suppested, you have to either move the log file to the disk which belongs to SQL Server cluster group or add the F: drive into SQL Server cluster group using cluster administrator tool.

  • Do this to verify if the dependency is there:

    • Log on locally to the server (terminal services will do).
    • Bring up Cluster Administrator (Start | Programs | Administrative Tools | Cluster Administrator)
    • If prompted for a cluster to connect to, type . (a period) and click Open.
    • Expand the Groups folder. Look in each group to find a resource labeled SQL Server.
    • Right-click on it and choose Properties.
    • Click on the dependencies tab. See if the F:\ drive is listed.

    K. Brian Kelley
    @kbriankelley

  • thanks, will do.

    as an aside question, is there away to know what the sa password is? or do i have to use t-sql to hange the password. the problem with that is there are so many applications that were created before i got here, that has the sa password hard-coded. oh and none of the programmers remmeber what the new password is either.!

    [font="Comic Sans MS"][/font]It is what it is.

  • If you have a sysadmin membered account, you can use NGSSquirrel or NGSSQLCrack from NGS Software (both commercial). Due to a weakness in the way they hash and store the passwords, it's substantially faster than you'd think, but it still might take a while.

    K. Brian Kelley
    @kbriankelley

  • Thanks Brian

    [font="Comic Sans MS"][/font]It is what it is.

  • still on the moving files issue, after i fixed the dependency issue, i then tried to move the log files for a database (as test).,

    i did the following,

    chnaged db to single user mode,

    detached the db

    copied the log file to the new location,(f:\logs)

    then i attempted to attach, this locations:

    E:\Program Files\Microsoft SQL Server\MSSQL$SQLCLUS\Data\XXX.MDF

    F:\logs\XXX.LDF

    I got an error that the database file already existed.

    so i created a new folder, (e:\data) and copied the data files to it.

     then i did

     

    E:\Data\XXX.MDF                                                                                                                                                                          

    F:\LOg\Data\XXX.LDF

    it worked but when i went into the EM to view the database, i noticed that the database was in read only mode, so i tried to change it from read only and got error messages. and i doing something wrong?

     

    [font="Comic Sans MS"][/font]It is what it is.

Viewing 9 posts - 1 through 8 (of 8 total)

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