<\/p>\n
1. Initial Network Setup<\/strong><\/h4>\nCreating Failover Cluster in SQL Server is quite clear and straightforward. However, before you can setup an SQL Server Failover cluster, you must have two or more computers on the network. In this demo, I’m using three computer:<\/p>\n
\n- SQLSERVER1<\/strong> – first node of the cluster<\/li>\n
- SQLSERVER2<\/strong> – second node of the cluster<\/li>\n
- SQLSERVER3<\/strong> – storage node, contains iSCSI virtual disks<\/li>\n<\/ul>\n
See How to Setup a Domain Network<\/p>\n
<\/p>\n
2. Install Failover Cluster on SQLSERVER1<\/strong><\/h4>\nYou have to first install SQL Failover Cluster on one of the nodes. Follow the steps below to do that:<\/p>\n
Step 1<\/strong> – Run the SQL Server Setup and choose ‘New SQL Server Failover Cluster installation’ as shown below<\/p>\n![\"New](\"https:\/\/i0.wp.com\/www.kindsonthegenius.com\/mssql\/wp-content\/uploads\/sites\/11\/2020\/10\/Screenshot-2020-10-10-at-01.32.44.png?resize=300%2C191&ssl=1\")
<\/a>New SQL Server Failover Cluster Installation<\/figcaption><\/figure>\nStep 2<\/strong> – Follow the steps until you get to the ‘Install Failover Cluster Rules’, make sure that no test failed as shown below.<\/p>\n![\"Ensure](\"https:\/\/i0.wp.com\/www.kindsonthegenius.com\/mssql\/wp-content\/uploads\/sites\/11\/2020\/10\/Screenshot-2020-10-10-at-01.40.30.png?resize=300%2C228&ssl=1\")
<\/a>Ensure that none of the test failed<\/figcaption><\/figure>\nStep 3<\/strong> – Continue on the the next step. In the Feature selection, ensure that Database Engine is selected<\/p>\n![\"Ensure](\"https:\/\/i0.wp.com\/www.kindsonthegenius.com\/mssql\/wp-content\/uploads\/sites\/11\/2020\/10\/Screenshot-2020-10-10-at-01.44.03.png?resize=300%2C228&ssl=1\")
<\/a>Ensure Database Engine is Selected<\/figcaption><\/figure>\nStep 4 – In the Instance Configuration, select Named Instance and give it a name. For me I called it SQLCLUSTER<\/p>\n![\"Use](\"https:\/\/i0.wp.com\/www.kindsonthegenius.com\/mssql\/wp-content\/uploads\/sites\/11\/2020\/10\/Screenshot-2020-10-10-at-01.46.52.png?resize=300%2C228&ssl=1\")
<\/a>Use named instance<\/figcaption><\/figure>\nStep 5<\/strong> – You may receive the error below<\/p>\n“the given network name\u00a0 is unusable….due to the following error: The network address is invalid”<\/p>\n
To correct this error, just uninstall VirtualBox Guest Additions and restart<\/p>\n
Step 6<\/strong> – At the cluster resource group as shown below, click next<\/p>\n![\"Cluster](\"https:\/\/i0.wp.com\/www.kindsonthegenius.com\/mssql\/wp-content\/uploads\/sites\/11\/2020\/10\/Screenshot-2020-10-10-at-02.05.40.png?resize=300%2C228&ssl=1\")
<\/a>Cluster Resource Group<\/figcaption><\/figure>\nStep 7<\/strong> – In the Cluster Disk Selection, select all the available storage as shown below<\/p>\n![\"Cluster](\"https:\/\/i0.wp.com\/www.kindsonthegenius.com\/mssql\/wp-content\/uploads\/sites\/11\/2020\/10\/Screenshot-2020-10-10-at-02.08.16.png?resize=300%2C228&ssl=1\")
<\/a>Cluster Disk Selection<\/figcaption><\/figure>\nStep 8<\/strong> – In Cluster Network Selection, select Ipv4 and DHCP<\/p>\n![\"Cluster](\"https:\/\/i0.wp.com\/www.kindsonthegenius.com\/mssql\/wp-content\/uploads\/sites\/11\/2020\/10\/Screenshot-2020-10-10-at-02.10.33.png?resize=300%2C228&ssl=1\")
<\/a>Cluster Network Configuration<\/figcaption><\/figure>\nStep 9<\/strong> – Specify the user account for the Agent and Database Engine<\/p>\n![\"Server](\"https:\/\/i0.wp.com\/www.kindsonthegenius.com\/mssql\/wp-content\/uploads\/sites\/11\/2020\/10\/Screenshot-2020-10-10-at-02.16.10.png?resize=300%2C226&ssl=1\")
<\/a>Server Configuration<\/figcaption><\/figure>\nStep 10<\/strong> – Add the server administrators<\/p>\n![\"Specify](\"https:\/\/i0.wp.com\/www.kindsonthegenius.com\/mssql\/wp-content\/uploads\/sites\/11\/2020\/10\/Screenshot-2020-10-10-at-02.20.14.png?resize=300%2C226&ssl=1\")
<\/a>Specify the administrators<\/figcaption><\/figure>\nStep 11<\/strong> – Follow the step and complete the installation<\/p>\nThe final window is shown below<\/p>\n![\"SQL](\"https:\/\/i0.wp.com\/www.kindsonthegenius.com\/mssql\/wp-content\/uploads\/sites\/11\/2020\/10\/Screenshot-2020-10-10-at-02.29.06.png?resize=300%2C226&ssl=1\")
<\/a>SQL Failover Cluster Successful Installation<\/figcaption><\/figure>\n <\/p>\n
3. Add Node to the Cluster<\/strong><\/h4>\nSince we have successfully set up failover cluster from the first Node(SQLSERVER1<\/em>), we would now go to the second node (SQLSERVER2<\/em>)\u00a0 so we can add the the node to the cluster. Follows the steps below<\/p>\nStep 1<\/strong> – Launch the SQL Server Setup and choose ‘Add Node to SQL Server Failover Cluster”<\/p>\n<\/div>\n![\"Add](\"https:\/\/i0.wp.com\/www.kindsonthegenius.com\/mssql\/wp-content\/uploads\/sites\/11\/2020\/10\/Screenshot-2020-10-10-at-02.25.50.png?resize=300%2C227&ssl=1\")
<\/a>Add Node to SQL Cluster<\/figcaption><\/figure>\nStep 2<\/strong> – You can see from the figure below the it detect the cluster we created in the first node (SQLCLUSTER01)<\/p>\n![\"Cluster](\"https:\/\/i0.wp.com\/www.kindsonthegenius.com\/mssql\/wp-content\/uploads\/sites\/11\/2020\/10\/Screenshot-2020-10-10-at-02.33.51.png?resize=300%2C226&ssl=1\")
<\/a>Cluster Node Configuration<\/figcaption><\/figure>\nStep 3<\/strong> – Follow the steps to complete the installation as shown below<\/p>\n![\"\"](\"https:\/\/i0.wp.com\/www.kindsonthegenius.com\/mssql\/wp-content\/uploads\/sites\/11\/2020\/10\/Screenshot-2020-10-10-at-02.42.10.png?resize=300%2C226&ssl=1\")
<\/a><\/p>\n <\/p>\n
4. Check that the Cluster Works Fine<\/strong><\/h4>\nLet’s now check that our failover cluster is working correctly.<\/p>\n
Step 1<\/strong> – Open Failover Cluster Manger in Node1 (where we installed the cluster). Click on Roles and you will see that the SQL Failover cluster is running as shown below<\/p>\n![\"SQL](\"https:\/\/i0.wp.com\/www.kindsonthegenius.com\/mssql\/wp-content\/uploads\/sites\/11\/2020\/10\/Screenshot-2020-10-10-at-02.49.02.png?resize=300%2C215&ssl=1\")
<\/a>SQL Server Failover Cluster running<\/figcaption><\/figure>\nA little explanation<\/b><\/p>\n
Now you see the the cluster is running on SQLSERVER1. So if a failure occurs, it would be migrated to the second node. So let’s see how this works<\/p>\n
See How to Setup a Domain Network<\/p>\n
<\/p>\n
2. Install Failover Cluster on SQLSERVER1<\/strong><\/h4>\nYou have to first install SQL Failover Cluster on one of the nodes. Follow the steps below to do that:<\/p>\n
Step 1<\/strong> – Run the SQL Server Setup and choose ‘New SQL Server Failover Cluster installation’ as shown below<\/p>\n<\/a>New SQL Server Failover Cluster Installation<\/figcaption><\/figure>\nStep 2<\/strong> – Follow the steps until you get to the ‘Install Failover Cluster Rules’, make sure that no test failed as shown below.<\/p>\n<\/a>Ensure that none of the test failed<\/figcaption><\/figure>\nStep 3<\/strong> – Continue on the the next step. In the Feature selection, ensure that Database Engine is selected<\/p>\n<\/a>Ensure Database Engine is Selected<\/figcaption><\/figure>\nStep 4 – In the Instance Configuration, select Named Instance and give it a name. For me I called it SQLCLUSTER<\/p>\n<\/a>Use named instance<\/figcaption><\/figure>\nStep 5<\/strong> – You may receive the error below<\/p>\n“the given network name\u00a0 is unusable….due to the following error: The network address is invalid”<\/p>\n
To correct this error, just uninstall VirtualBox Guest Additions and restart<\/p>\n
Step 6<\/strong> – At the cluster resource group as shown below, click next<\/p>\n<\/a>Cluster Resource Group<\/figcaption><\/figure>\nStep 7<\/strong> – In the Cluster Disk Selection, select all the available storage as shown below<\/p>\n<\/a>Cluster Disk Selection<\/figcaption><\/figure>\nStep 8<\/strong> – In Cluster Network Selection, select Ipv4 and DHCP<\/p>\n<\/a>Cluster Network Configuration<\/figcaption><\/figure>\nStep 9<\/strong> – Specify the user account for the Agent and Database Engine<\/p>\n<\/a>Server Configuration<\/figcaption><\/figure>\nStep 10<\/strong> – Add the server administrators<\/p>\n<\/a>Specify the administrators<\/figcaption><\/figure>\nStep 11<\/strong> – Follow the step and complete the installation<\/p>\nThe final window is shown below<\/p>\n<\/a>SQL Failover Cluster Successful Installation<\/figcaption><\/figure>\n <\/p>\n
3. Add Node to the Cluster<\/strong><\/h4>\nSince we have successfully set up failover cluster from the first Node(SQLSERVER1<\/em>), we would now go to the second node (SQLSERVER2<\/em>)\u00a0 so we can add the the node to the cluster. Follows the steps below<\/p>\nStep 1<\/strong> – Launch the SQL Server Setup and choose ‘Add Node to SQL Server Failover Cluster”<\/p>\n<\/div>\n<\/a>Add Node to SQL Cluster<\/figcaption><\/figure>\nStep 2<\/strong> – You can see from the figure below the it detect the cluster we created in the first node (SQLCLUSTER01)<\/p>\n<\/a>Cluster Node Configuration<\/figcaption><\/figure>\nStep 3<\/strong> – Follow the steps to complete the installation as shown below<\/p>\n<\/a><\/p>\n <\/p>\n
4. Check that the Cluster Works Fine<\/strong><\/h4>\nLet’s now check that our failover cluster is working correctly.<\/p>\n
Step 1<\/strong> – Open Failover Cluster Manger in Node1 (where we installed the cluster). Click on Roles and you will see that the SQL Failover cluster is running as shown below<\/p>\n<\/a>SQL Server Failover Cluster running<\/figcaption><\/figure>\nA little explanation<\/b><\/p>\n
Now you see the the cluster is running on SQLSERVER1. So if a failure occurs, it would be migrated to the second node. So let’s see how this works<\/p>\n
<\/a>Step 2<\/strong> – Follow the steps until you get to the ‘Install Failover Cluster Rules’, make sure that no test failed as shown below.<\/p>\n Step 3<\/strong> – Continue on the the next step. In the Feature selection, ensure that Database Engine is selected<\/p>\n Step 4 – In the Instance Configuration, select Named Instance and give it a name. For me I called it SQLCLUSTER<\/p>\n Step 5<\/strong> – You may receive the error below<\/p>\n “the given network name\u00a0 is unusable….due to the following error: The network address is invalid”<\/p>\n To correct this error, just uninstall VirtualBox Guest Additions and restart<\/p>\n Step 6<\/strong> – At the cluster resource group as shown below, click next<\/p>\n Step 7<\/strong> – In the Cluster Disk Selection, select all the available storage as shown below<\/p>\n Step 8<\/strong> – In Cluster Network Selection, select Ipv4 and DHCP<\/p>\n Step 9<\/strong> – Specify the user account for the Agent and Database Engine<\/p>\n Step 10<\/strong> – Add the server administrators<\/p>\n Step 11<\/strong> – Follow the step and complete the installation<\/p>\n The final window is shown below<\/p>\n <\/p>\n Since we have successfully set up failover cluster from the first Node(SQLSERVER1<\/em>), we would now go to the second node (SQLSERVER2<\/em>)\u00a0 so we can add the the node to the cluster. Follows the steps below<\/p>\n Step 1<\/strong> – Launch the SQL Server Setup and choose ‘Add Node to SQL Server Failover Cluster”<\/p>\n Step 2<\/strong> – You can see from the figure below the it detect the cluster we created in the first node (SQLCLUSTER01)<\/p>\n Step 3<\/strong> – Follow the steps to complete the installation as shown below<\/p>\n <\/p>\n Let’s now check that our failover cluster is working correctly.<\/p>\n Step 1<\/strong> – Open Failover Cluster Manger in Node1 (where we installed the cluster). Click on Roles and you will see that the SQL Failover cluster is running as shown below<\/p>\n A little explanation<\/b><\/p>\n Now you see the the cluster is running on SQLSERVER1. So if a failure occurs, it would be migrated to the second node. So let’s see how this works<\/p>\n<\/a><\/a><\/a><\/a><\/a><\/a><\/a><\/a><\/a>3. Add Node to the Cluster<\/strong><\/h4>\n
<\/a><\/a><\/a><\/p>\n4. Check that the Cluster Works Fine<\/strong><\/h4>\n
<\/a>
![\"Migrate](\"https:\/\/i0.wp.com\/www.kindsonthegenius.com\/mssql\/wp-content\/uploads\/sites\/11\/2020\/10\/Screenshot-2020-10-10-at-02.52.09.png?resize=300%2C203&ssl=1\")
<\/a>