June 16, 2011 at 11:28 pm
While I am creating the Cluster of sql server 2008 R2 I am getting error:
[Error Message]
The volume that contains SQL Server data directory G:\MSSQL10_50.MSSQLSERVER\MSSQL\Data does not belong to the cluster group.
[Details]
Microsoft.SqlServer.Configuration.SqlEngine.ValidationException: The volume that contains SQL Server data directory G:\MSSQL10_50.MSSQLSERVER\MSSQL\Data does not belong to the cluster group.
Thanks
June 17, 2011 at 12:29 am
G Drive is a cluster drive or not ?
Have you added this drive in the Cluster Storage ?
Have you created first SQL Server group and then start installation or you are trying to install directly SQL Server 2008 R2 on the Cluster Mode
Regards,
Syed Jahanzaib Bin Hassan
BSCS | MCTS | MCITP | OCA | OCP | OCE | SCJP | IBMCDBA
My Blog
www.aureus-salah.com
June 17, 2011 at 12:49 am
Thanks.
0. The Whole storage is provided from the Netapp.Even OS drive C: also.
1. Is it needed to create sql server group also.I hink Cluster service itself created it.
2. G drive is a clustered drive.
3. In validation report I am getting these error:
a.
An error occurred while executing the test.
There was an error validating that there are no unsigned drivers.
OpenService 'RemoteRegistry' failed.
Access is denied
b.
In Cluster Log it is giving errors of :
A1. The Cluster service failed to bring clustered service or application 'Available Storage' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
A2. Cluster resource 'Cluster Disk 4' in clustered service or application 'Available Storage' failed.
A3. Cluster resource 'Cluster Disk 2' in clustered service or application 'Available Storage' failed.
A4. Cluster resource 'Cluster Disk 1' in clustered service or application 'Available Storage' failed.
c.
IsDomainNetworkTopOfBindings
Checks to see if the computer domain server is on the network that is bound to the top of the network order.
Warning
The domain network is not the first bound network. This will cause domain operations to run slowly and can cause timeouts that result in failures. Use the Windows network advanced configuration to change the binding order
Thanks
June 21, 2011 at 5:45 am
forsqlserver (6/17/2011)
Thanks.0. The Whole storage is provided from the Netapp.Even OS drive C: also.
is this SQL Server a virtual machine?
forsqlserver (6/17/2011)
c.IsDomainNetworkTopOfBindings
Checks to see if the computer domain server is on the network that is bound to the top of the network order.
Warning
The domain network is not the first bound network. This will cause domain operations to run slowly and can cause timeouts that result in failures. Use the Windows network advanced configuration to change the binding order
which operating system are the cluster nodes using and how many NICs do you have on each cluster node?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
June 21, 2011 at 10:28 pm
check the LUN mapping of disk drives
these are shared disk or Drive comming from SAN storage?
are you installing this SQL server Installation on physical Server or Virtual Server ?
Regards,
Syed Jahanzaib Bin Hassan
BSCS | MCTS | MCITP | OCA | OCP | OCE | SCJP | IBMCDBA
My Blog
www.aureus-salah.com
December 5, 2011 at 1:04 pm
Any solution to this issue? I'm getting the same problem.
SQL Server 2008 R2
Windows Server 2008 R2 SP1
SAN disks
I get it whether the disks are in available storage or if they are pre-added to the cluster resource group.
"The volume that contains SQL Server data directory <directory path> does not belong to the cluster group"
Thank you in advance.
John
December 13, 2011 at 6:40 am
JohnnyDBA (12/5/2011)
Any solution to this issue? I'm getting the same problem.SQL Server 2008 R2
Windows Server 2008 R2 SP1
SAN disks
I get it whether the disks are in available storage or if they are pre-added to the cluster resource group.
"The volume that contains SQL Server data directory <directory path> does not belong to the cluster group"
Thank you in advance.
John
1. Ensure that you have successfully created SQL Server resource group.
2. Make all the disks where you want to keep the data & log files a part of this group.
3. Ensure you have added the dependency on these drives.
December 13, 2011 at 3:22 pm
Can you explain #3 further?
edit - the disks that contain the data and log paths are mounted volumes. They show up with strange paths that contain what looks like disk SIDs. When I change them to the logical path name using the drive letter, that's when I get the error. Does that mean I should leave the path with the SIDs and just add them that way?
edit2 - I tried everything and I still can't get this working.
I have 6 disks:
Cluster Disk 17 is Mounted Volume O:\archive
Cluster Disk 26 is Mounted Volume O:\backup
Cluster Disk 35 is Volume O: Cluster Disk 47 is Mounted Volume O:\data
Cluster Disk 55 is Mounted Volume O:\log
Cluster Disk 9 is Mounted Volume O:\temp
I tried installing with an existing resource group and disks added with all mounted disks having dependencies on disk 35
I tried installing with an existing resource group and disks added with all disk dependencies removed
I tried installing with an existing resource group and all disks in available storage
I tried installing with new resource group (specified in the installation screen) with all disks in available storage
I tried installing to the root of the mount points
I tried installing to subdirectories in the mount points
nothing works, same error every. single. time.
Please help
December 13, 2011 at 10:04 pm
Please go through this link, may help you to find the exact procedure:
December 14, 2011 at 7:22 am
I did look through that article last night actually. I didn't see anything that I wasn't doing correctly based on the instructions.
I'd just like to point out one more thing. There is another forum post http://www.sqlservercentral.com/Forums/Topic961716-1549-1.aspx which points to another error on a different part of the setup. This is at the Cluster Disk Selection screen. I am also seeing this for the root disk that the mount points are connecting to (Disk 35). I am assuming the issues I'm experiencing here and at the section where you specify the data paths described above are related.
I'm going to give it another try this morning, then call Microsoft. If I get the answer from them I'll make sure to follow up here with what they say.
December 16, 2011 at 6:48 am
JohnnyDBA (12/14/2011)
I did look through that article last night actually. I didn't see anything that I wasn't doing correctly based on the instructions.I'd just like to point out one more thing. There is another forum post http://www.sqlservercentral.com/Forums/Topic961716-1549-1.aspx which points to another error on a different part of the setup. This is at the Cluster Disk Selection screen. I am also seeing this for the root disk that the mount points are connecting to (Disk 35). I am assuming the issues I'm experiencing here and at the section where you specify the data paths described above are related.
I'm going to give it another try this morning, then call Microsoft. If I get the answer from them I'll make sure to follow up here with what they say.
Did you contact Microsoft?
December 16, 2011 at 9:54 am
Been going back and forth with them for 2 days with little to no progress. I'm trying some other things before I proceed with them on this issue.
December 16, 2011 at 3:46 pm
Microsoft believes the root cause is an issue with the mount point configuration. The action plan is to re-create the mount points following the information in this article http://support.microsoft.com/kb/947021
We need to wait for a downtime window just in case. I will follow-up when I find out if this is the solution.
December 16, 2011 at 5:11 pm
JohnnyDBA (12/16/2011)
Microsoft believes the root cause is an issue with the mount point configuration. The action plan is to re-create the mount points following the information in this article http://support.microsoft.com/kb/947021We need to wait for a downtime window just in case. I will follow-up when I find out if this is the solution.
Thanks for sharing!
December 19, 2011 at 5:04 am
From the KB947021 article...
Make a dependency in the mounted volume disk resource that specifies the disk that is hosting the mount point folder. This makes the mounted volume dependent on the host volume, and it makes sure that the host volume comes online first.
It is very important that you do this. You can either:
1) Create the SQL Cluster group and set up the dependencies before you start the SQL install
2) Let the SQL install create the group, then manually add the dependencies BEFORE you do any failover testing
If you do not set these dependencies then there is a risk that after a failover the SQL Service will start up before all of the mount point disks are online. This will confuse the life out of SQL for a while, but ultimately SQL should start providing that all disks become online before the retry failure limit for SQL is reached.
P.S. If anyone is having similar problems with a cluster install using mount points, PLEASE mention you are using them. Mount Points add a whole new set of things that can go wrong that most people will not encounter.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 15 posts - 1 through 15 (of 21 total)
You must be logged in to reply to this topic. Login to reply