SQL Server Home
Clusters and Mounted Drives are having Issues
as By Design
3/6/2008 12:06:21 PM
User(s) can reproduce this bug
**** I'm reopening this BUG. I just spent about a week trying to build a two node cluster on Windows 2008 using the following Drive layouts. During the install I select the "R" drive as my disk I then change the locations of the system database to R:\Production. I then alter the location for user database and log to R:\Production\Databases and R:\Production\Logs (This is done during the setup screen).
I use mounted drives to build my multi-node clusters. I have a root drive, in this case “R”, that is sized to be 1GB. Then have a mounted drive call “Production” that is mounted under “R”. I then have two more mounted drives, Databases and Logs that mount under Production.
R: -> Root Drive
R:\Production -> Production folder is a Mounted drive under R:\
R:\Production\Databases -> Database folder is a mounted drive under R:\Production
R:\Production\Logs -> Logs folder is a mounted drive under R:\Production
R:\Production\Backups -> Backups folder is a mounted drive under R:\Production
Size of drives:
Production 50 GB
Database (various sizes)
Logs (various size)
Backups (various sizes)
The Cluster install is telling me that my Disk R is not valid because there are dependencies in place. I’m using mounted drives and have setup dependencies between the “Root” drive in this case “R” and the mounted folders “MP Production” and “MP Logs” MP Production is where I place my MDF files and MP Logs is where the LDF files go.
This check needs to be removed or made optional
SQL Server 2008 SP1
Windows Server 2008 R2
Operating System Language
Steps to Reproduce
See descripton. Build a two node Windows 2008 Failover Cluster.
1. Configure a Root Drive (R:)
2. Add three mount points under R: (See desc)
3. Install SQL Server 2008 SP1 (Doing a SLIPSTREAM Install)
4. During the setup where it lets you change the location for user databases and Log. Change the location for user databases to R:\Production\Databases and the location for Logs to R:\Production\Logs.
Installer doesn't allow me to use mounted drive if there are dependencies setup between the root drive and the mounted folder
Install fails with Access Denied on the mounted drive. The installer doesn't assign any permission to the mounted drives.
Install should work!
to post a comment.
Please enter a comment.
on 2/2/2010 at 7:17 PM
Your particular issue is about geo-cluster configuration, where 3rd party solution has specific dependency types that we disallow.
To make this work, please check the dependency types and ensure they are of type "storage class resource" for your CLX resources.
With this I am closing this issue. Please let me know if you still have the problem after checking and revising the resource types across these dependencies.
Nilton Pinheiro - MVP
on 10/13/2009 at 1:48 PM
I'm installing a new SQL 2008 cluster using mount volume and got the below error:
2009-10-13 15:27:53 Slp: Rule evaluation message: The cluster on this computer does not have a shared disk available. To continue, at least one shared disk must be available.
I was talking with a friend and he told me that the problem is related to mount volume resources and that I need remove mount volume resources (all in the same resource group) and add it just after install SQL2008.
On the other hand, I was looking the file Detail.txt on the setup log and note this:
2009-10-13 15:27:50 Slp: The cluster disk 'SQLP8_G_BIN' has a resource dependency 'BBASQLPROD8_A_CLX' and cannot be used as a shared disk.
2009-10-13 15:27:50 Slp: Mount point status for disk 'SQLP8_G_BIN' could not be determined. Reason: 'The disk resource 'SQLP8_G_BIN' has a dependency on resource 'BBASQLPROD8_A_CLX'. To use a disk in a new SQL Server failover cluster instance, the disk must not have any dependencies.'
2009-10-13 15:27:50 Slp: The cluster disk 'SQLP8_J_DADOS' has a resource dependency 'BBASQLPROD8_A_CLX' and cannot be used as a shared disk.
I'm configuring a geocluster using Cluster Extension and noticed that the disk and volume have dependencies from CLX. So I not sure if my friend is rigth or my problem is just related to dependencies?
About you note:
"In SQL Server 2008 failover clustering, we changed the way the resource group and the disk dependencies are created. We automatically create all the dependencies between each disk and SQL Server resource. You shouldn't create any disk dependency before setup"
The article KB 280297 (http://support.microsoft.com/kb/280297/en-us) say the following on topic "How to set up volume mount points on a Clustered Server":
4. Create the new Disk resource, and then set dependencies. To do so, follow these steps:
a. Open Cluster Administrator.
b. Right-click the group that owns the Shared Disk resource for the disk on which you just created the volume mount point. Click New, and then click Resource.
c. For the Resource type, click Physical Disk. Verify that it is in the same group as the the root disk. Click Next.
d. Make sure all nodes are possible owners, and then click Next.
e. Double-click the root disk, to make this volume mount point disk dependent on the root disk. Click Next.
f. In the Disk Parameters window, you should see your disk listed. It will be listed by the disk number, and partition number; this is different from standard MSCS disks, which are listed by drive letter. Click Finish.
g. Right-click the new Disk resource, and then click Bring Online
So, update the article can be a good ideia.
Question: What is the right configuration when using volume mount point on a cluster? Should I add resources to mount points just after install SQL 2008 or this a myth? Is there any clear and "not buged" documentation?
Thanks a lot
on 9/12/2008 at 5:31 PM
For RTM release, we relaxed this requirement last minute. If there are dependencies already set across cluster disks, we allow them, provided:
1. All the disks are within the same group
2. There are no other external dependencies to the selected disks (such as for DTS)
on 9/8/2008 at 9:44 AM
Installer shouldn't be so picky. This issue also affects geographically dispered clusters which REQUIRE the disks to depend on other resources to ensure failover works properly.
on 3/12/2008 at 11:54 AM
This is by design in SQL Server 2008 failover clustering setup. You found a bug in Books Online that we will correct by removing the following statement:
- Ensure that the mounted disks or volumes are mounted under the correct lettered base drive, and make sure that the mounted drive is set to be dependent on the parent drive.
In SQL Server 2008 failover clustering, we changed the way the resource group and the disk dependencies are created. We automatically create all the dependencies between each disk and SQL Server resource. You shouldn't create any disk dependency before setup. You also should not create dependencies across disks. Windows clustering does not guarantee that those dependencies across disks are enforced; even though the user sets them, they can be easily broken as disks are moved across groups.
Please reactive this issue if this does not address your concern.
on 3/6/2008 at 12:24 PM
I found this in the SQL Server 2008 help. Ensure that the mounted disks or volumes are mounted under the correct lettered base drive, and make sure that the mounted drive is set to be dependent on the parent drive.
to post a workaround.
Please enter a workaround.
I use mounted drives to build my clusters.doc (restricted)
© 2013 Microsoft