Windows Server and SQL Database Cluster


Windows server and database clusters required some prerequisites that is the reason in my previous two articles I told you how to get redundant network and shared storage for the windows server and database fail-over cluster. A windows server cluster is required for the hardware redundancy and database cluster provide us database redundancy in case of the failure of one node second node will take over and perform the operations continuously. In windows server failover cluster two or more servers communicating with each other through a series of the heartbeat on the dedicated network. The active server sends the heartbeat signals to another standby server in the specified interval that is usually called a push heartbeat. If the standby server did not receive heartbeat from the active server, it takes over and becomes the active server and performs the operations of the active server. Windows failover cluster communication signals are also sent by standby servers as well if the active server did not respond to the signals in a specific interval of time then also standby server takes over and becomes active server this is called pulled heartbeat. The same is the case when we add the role of the database service using SQL Server or MySQL server in the windows server failover cluster. This role is worked as a database cluster for database fail-over. In this article, I will show you in video and also by screenshots on how to do it with MySQL and SQL Server.

Windows Server Two Node Fail-Over Cluster

Open windows server manager and click Add roles and features

Server Manager

Select role-based or feature-based installation

Role based installtion

Select the Node on which you want to install role or feature

Select node

From the features select failover clustering and click next

Failover Clustering

Click installation to finish the wizard

Conform Installation

When role installation is complete open failover cluster manager and starts windows server failover cluster validation and the installation wizard.

Start validation through the wizard and verify the validation result

Select Servers for cluster validation

Select tests or run all tests for the cluster nodes

Test selection options

Confirm the validation wizard to start validation click next

Conform Validation Start

Click on a finish to complete validation wizard if you want to start the cluster creation wizard click the checkbox.

Finishing Cluster Validation

Click next to start the cluster configuration wizard

Provide the cluster object name and IP of the same subnet of the nodes


Confirm the cluster configuration installation wizard and check the add eligible storage checkbox and click next to start the Windows Server Failover Cluster wizard.

Cluster Configration Conformation

Open windows server failover cluster manager to check the cluster

Win Failover Cluster Manager

SQL Server Two Node Failover Cluster Instance

To install SQL server failover cluster start the SQL server instance and click on the installation


To start the installation click on the new SQL Server failover cluster installation click next after providing license information.

License Key Info

Accept the license terms and condition for SQL server failover cluster

Accept the license terms and condition

Click next after global role checking is finished

Global roles checking

Select SQL server features type for failover cluster

Select SQL Server Cluster Feature

Click the checkbox of the failover cluster features

SQL Server Cluster Feature

Checking the selected roles passed the installation check

Feature Roles Validation

Write the cluster instance name for the DNS Object

Instanse Configuration

Checking Disk space requirement for failover cluster installation

Checking Disk Requirement

Select the disk on which you want to install SQL failover cluster it must be shared storage disk among all nodes of the cluster

Checking Disk Selection

Configure cluster network information

Cluster Network IP Configuration

Cluster services user configuration of the FQDN(fully qualified domain name)

Cluster User Configuration

Configure user for database engine access provide the password for the same user as well

Database engin user configuration

Click next to check if any error and report is appaired in the installation process

Error and Reporting

Click next to check installation rules for the cluster is passed or not

Cluster Installation rules passed

Click next to proceed the wizard for installation and click on install to start installation on node1

Ready to install

When the installation is complete go to windows server failover cluster manager under the roles tab you will find the database SQL failover cluster role

Database Cluster Rule

A database failover cluster is installed and online successfully on node1 now we have to add node2 in the database failover cluster. Go to node2 and start SQL server setup from installation tab chose to add the node to SQL Server failover cluster

Add Node to SQL FCI

It will check the setup support rules for the node2

Setup support rules

Provide license details for node2 SQL server failover cluster

Product license Key

Accept license terms and conditions for the node2

Accept License terms and condition

Rules setup support check for node2 passed with some warning

Setup support rules for add node2

Cluster node2 addition in the created database cluster


Network Configuration for node2 no need to provide IP just select the IP you provide in node1 installation

Network Configuration Node2

Provide account details for node2 cluster authentication

Service Account for Node2

Check status for the node2 addition is passed

Add node2 Rules Check status

Click install to start the installation wizard to complete node2 addition

Ready to add Node2

Installation is completed for the node2 addition is completed now open windows server failover cluster manager click on the roles you will find node2 also under the SQL Server failover cluster


You may be intrested to read more useful articles.




Please enter your comment!
Please enter your name here