Recently I had to setup SQL Server 2012 cluster (Active-Passive) for my client.
We had given 2 physical boxes which are placed in 2 different DCs and storage has zonned so that storage can be used by both the boxes and fail over can happen without any issues between the two DCs.
Windows cluster build completed and handed over to me for SQL Server setup. This cluster was built with 2 cluster shared disks. I have started building SQL Server but out of 2 cluster disks only 1 disk was detected by SQL Server setup. I was with no clue what might be the problem. I checked with wintel person who built the windows cluster, but response is "Issue is with your SQL Server not from my side.". Again I started digging the problem and for its solution. After some research, I got an Idea to check the 2 cluster disk drives and properties, here I found one drive built with NTFS and other drive is built with ReiserFS file systems. The drive which built with NTFS file system detected by SQL Server setup but other drive which built with ReiserFS file system is not detected by SQL Server setup.
I have asked the wintel team to change the file system to NTFS. Once this change is done, SQL Server setup was able to detect both the disks.
After this in the next steps setup went smoothly but at the last step of setup encountered below error:
This error is due to insufficient permissions at OU level in AD and description is like below.
The user credentials of the currently logged on user who is creating the Failover Cluster will be used to create the computer objects in Active Directory. The user must have Create Computer Objects permissions to the OU to create the computer objects.
For this issue I have contacted AD team to provide create object permissions at OU level in AD and AD team checked whether is there any computer object with SQL Cluster name which I have used for cluster setup, which is not found in the computer object list of AD.
After providing proper permissions I have started a fresh setup again but same error repeated. Again I was with no clue. Again contacted the respective team. Now they are able to find the SQL Cluster name in the computer objects of AD, but they are not sure about the repeated error.
I did checked the windows logs but nothing was found. So thought to check the cluster logs also.
When I checked the Cluster logs found below error:
After working on all these hurdles I was able to build the SQL Server cluster without any issues.
We had given 2 physical boxes which are placed in 2 different DCs and storage has zonned so that storage can be used by both the boxes and fail over can happen without any issues between the two DCs.
Windows cluster build completed and handed over to me for SQL Server setup. This cluster was built with 2 cluster shared disks. I have started building SQL Server but out of 2 cluster disks only 1 disk was detected by SQL Server setup. I was with no clue what might be the problem. I checked with wintel person who built the windows cluster, but response is "Issue is with your SQL Server not from my side.". Again I started digging the problem and for its solution. After some research, I got an Idea to check the 2 cluster disk drives and properties, here I found one drive built with NTFS and other drive is built with ReiserFS file systems. The drive which built with NTFS file system detected by SQL Server setup but other drive which built with ReiserFS file system is not detected by SQL Server setup.
I have asked the wintel team to change the file system to NTFS. Once this change is done, SQL Server setup was able to detect both the disks.
After this in the next steps setup went smoothly but at the last step of setup encountered below error:
This error is due to insufficient permissions at OU level in AD and description is like below.
The user credentials of the currently logged on user who is creating the Failover Cluster will be used to create the computer objects in Active Directory. The user must have Create Computer Objects permissions to the OU to create the computer objects.
For this issue I have contacted AD team to provide create object permissions at OU level in AD and AD team checked whether is there any computer object with SQL Cluster name which I have used for cluster setup, which is not found in the computer object list of AD.
After providing proper permissions I have started a fresh setup again but same error repeated. Again I was with no clue. Again contacted the respective team. Now they are able to find the SQL Cluster name in the computer objects of AD, but they are not sure about the repeated error.
I did checked the windows logs but nothing was found. So thought to check the cluster logs also.
When I checked the Cluster logs found below error:
Cluster network name resource 'SQL Network Name
(Name of the SQL Cluster)' failed to create its associated computer object in domain
'Domain name' for the following reason: Resource online.
The associated error code is: -1073741790
Please work with your domain administrator to
ensure that:
- The cluster identity 'Windows Cluster name' can create
computer objects. By default all computer objects are created in the
'Computers' container; consult the domain administrator if this location has
been changed.
- The quota for computer objects has not been
reached.
- If there is an existing computer object,
verify the Cluster Identity 'Windows Cluster name' has 'Full Control' permission to that
computer object using the Active Directory Users and Computers tool.
This issue is because "Windows Cluster name" didn't have full access on "SQL Cluster name" at AD Level.
Our domain guy has provided "Windows Cluster name" full access on "SQL Cluster name" computer object at AD Level. Then I can able to bring the SQL Server resources online and failover also from fail-over cluster manager. I am happy. Cluster setup is the one task which comes rarely to most of the DBAs and everybody want to get the exposure to it. I got the chance and that too with some learning. Before also I did setup the SQL cluster on previous versions. I think we had the enough permissions at that moment so we were able to set it up without any issues. But now I think I did not provided enough privileges which made me to learn a new thing(at least new to me).
So here I had 3 issues while Building the SQL Cluster.
1. Disks are not built with NTFS file system.
2. I was not having the create objects permissions at OU Level in AD.
3. Didn't had full
control for cluster 'Windows Cluster name’ on SQL Cluster name.
After working on all these hurdles I was able to build the SQL Server cluster without any issues.
No comments:
Post a Comment