Prerequisite for SQL Server Cluster Installation
SQL Server 2012 – Run Failover Clustering Validation tool.
Two instances of SQL Server or 1 and if 2 then both should have different cluster group.
.NET Framework 3.5 with Service Pack 1 & Windows Installer 4.5.
The nodes for the cluster and their ip addresses and access to both nodes.
OS version & Edition – (Windows Server 2008 R2)
SQL Server version & edition – (Enterprise or Standard)
Verify Storage SAN/iSCSI
Configure the quorum disk
Create a Local Disk for Page File
Verify that anti-virus software is not installed on your MSCS cluster
Verify that you have disabled NetBIOS for all private network cards before beginning SQL Server Setup
Remote Administration must be enabled
The SQL Server installation product key.
The SQL Server components to be installed.
The SQL Server virtual server name.
Default or named instance?
The shared disks to select.
The SQL Server virtual IP address.
The subnet mask.
The dedicated domain group for the SQL Server services and dedicated domain account to be added in admin group for running SQL server Engine and SQL Server Agent services.
The dedicated domain accounts for each of the services if needed, to be installed (SSAS, SSIS, and/or SSRS).
The SQL Server Collation to select mostly default.
Windows or Mixed authentication mode
The list of users to be the SQL Server administrator for the instance.
The default locations for the data and log files for the user databases and tempdb and also the location for the backup directory.
Create Domain Group with SQL Admin permissions and use that group for cluster security and management.
MSDTC is to be installed prior to install sql server clustering with dedicated MSDTC drive and IP address.
Cluster nodes should not be a part of domain controller.
Ethernet LAN – 10.0.0.0/21
Primary iSCSI LAN – 10.10.10.0/24
Secondary iSCSI LAN – 10.10.20.0/24
Heartbeat LAN – 18.104.22.168/24
Node 1 LAN – 10.0.1.201
Node 1 iSCSI1 – 10.10.10.201
Node 1 iSCSI2 – 10.10.20.201
Node 1 Heartbeat – 22.214.171.124
SQL Node 2 LAN – 10.0.1.202
SQL Node 2 iSCSI1 – 10.10.10.202
SQL Node 2 iSCSI2 – 10.10.20.202
SQL Node 2 Heartbeat – 126.96.36.199
Authentication Mode – Mixed
Database mode – SQL 2012 Compatible
Management Cluster Name: SQLCLSTADMIN
SQL Management Cluster IP – 10.0.1.203
Virtual Cluster Name –
Virtual Cluster IP –
SQLCLST Cluster Name – SQLCLSTDB
SQLCLST Cluster IP –
SQL Server Accounts Info
Use sql Domain group
SQL Database Engine domain group ID – Domain\sqladmin
SQL server Agent domain group ID – Domain\sqlagent
Drive Usage :-
Data – L-Drive
Log file: P Drive
Data – N-Drive
Windows Server 2012 Validate Cluster Configuration
Word of caution: do not skip any error message that this wizard generates in the final report. Doing so would simply mean that our configuration going forward will be unsupported. We only need to run this wizard on either of the nodes.
To run the Validate Cluster Configuration Wizard:
1. Open the Failover Cluster Management console
2. Under the Management section, click the Validate a Configuration link. This will run the Validate a Configuration Wizard
3. In the Select Servers or a Cluster dialog box, enter the host names of the nodes that you want to add as members of your cluster and click Next.
i.e:- SQLCLST01, SQLCLST02
4. In the Testing Options dialog box, click Next to run all the necessary tests to validate whether or not the nodes are OK for clustering. If this is the first time to run the wizard, we must run all the tests for validation. For succeeding runs, especially when adding hardware like disk subsystems ot network cards on your cluster nodes, we can selectively choose which tests to run as long as we have initially validated our hardware by running all tests.
5. In the Confirmation dialog box, click next. This will run all the necessary validation tests.
In the Summary dialog box, verify that all the report returns successful.
Fail over Cluster Resource dependencies in sql server
When you install Microsoft SQL Server on a cluster as a SQL Server fail over cluster instance, a specific set of SQL Server resources that have dependencies on other resources in the cluster group are created.
Step 1: Right click on sql server more actions Show Dependency Report