 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
SQL Server Forum / DB Engine / SQL Server / May 2008Unable to see drive from SQL
We have two instances of SQL 2005 on an active-active cluster. No service packs. Each instance has its own drives for data, log files and backups. However, when performing manual backups from Management Studio, the drives used for the scheduled backups is not listed in the Locate Database Files popup window. Can anyone tell me what needs to be done in order for the drive used for backups to be visible in this window? Thanks, Michael MacGregor Database Architect Just thinking out loud but are you sure you have the right instance? For example, if instance 1 is using drives G: and H:, while instance 2 is using drives I: and J:, then I: and J: won't show up in the list for instance 1.  SignatureTom ---------------------------------------------------- Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS SQL Server MVP Toronto, ON Canada https://mvp.support.microsoft.com/profile/Tom.Moreau We have two instances of SQL 2005 on an active-active cluster. No service packs. Each instance has its own drives for data, log files and backups. However, when performing manual backups from Management Studio, the drives used for the scheduled backups is not listed in the Locate Database Files popup window. Can anyone tell me what needs to be done in order for the drive used for backups to be visible in this window? Thanks, Michael MacGregor Database Architect Oh believe me that was my first thought, but no. We added new drives for backups for both instances and neither one can see either of those new drives. I presume it may be something to do with the cluster configuration but the drives can be accessed fine from automated backups, or by manually using the appropriate SQL in a query window, it simply can't see the drive from the popup window when you right click on a database and select either backup or restore. Mike Ah. Have you added those drives to the respective cluster groups and then added them as a dependency for SQL Server? SignatureTom ---------------------------------------------------- Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS SQL Server MVP Toronto, ON Canada https://mvp.support.microsoft.com/profile/Tom.Moreau Oh believe me that was my first thought, but no. We added new drives for backups for both instances and neither one can see either of those new drives. I presume it may be something to do with the cluster configuration but the drives can be accessed fine from automated backups, or by manually using the appropriate SQL in a query window, it simply can't see the drive from the popup window when you right click on a database and select either backup or restore. Mike Forget about doing this via GUI. If you just run the BACKUP statement, would that work? Say, BACKUP DATABASE yourDB to disk='X:\yourDB.bak' Linchi > Oh believe me that was my first thought, but no. > [quoted text clipped - 6 lines] > > Mike Performing backups is not the problem. Seeing the drives in the dialog boxes is the issue. MTM > Performing backups is not the problem. Seeing the drives in the dialog > boxes is the issue. Sure, but do you not believe that attempting a backup from a query window will help isolate the issue? The backup from the query window will either succeed or fail. If it succeeds, then you know SQL Server can see the drive, and you can either attempt to figure out why the GUI can't see it, or just run your backups using BACKUP DATABASE. If it fails, then you can focus on getting SQL Server to see the drive in general (in other words, it is no longer just an issue with the GUI). I had already said that automated backups to those drives and manually executing the appropriate SQL command work fine. Was that too obtuse to understand? MTM I am very sorry your highness, some of us work offline and don't have the energy or ability to re-read the entire thread. I will make sure to never interject so obtusely to any of your problems again. Christ, you try to help a guy, and get treated like an a**hole. :-( *PLONK* On 5/1/08 3:48 PM, in article #OGyNR8qIHA.3804@TK2MSFTNGP02.phx.gbl, > I had already said that automated backups to those drives and manually > executing the appropriate SQL command work fine. Was that too obtuse to > understand? > > MTM The issue is that your drives are not listed as dependencies in the SQL Server under Cluster Administrator. Take the SQL Server in Cluster Administrator offline and add the drives you want to be seen as dependencies and then bring SQL Server back online. The problem is that Management Studio looks to the dependencies within the SQL Server through the Cluster Management API. |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.