SQL 2012 Failover Cluster Build (Step by Step) – Part 2: Adding a New Node


This is my 2nd post of the series of building SQL failover cluster. This post covers adding second node to the SQL Server 2012 failover cluster that is created in Part 1. Please refer to the 1st part for understanding the context of this demonstration. You must finish part 1 in order to apply the steps defined here in your case.

Part 1: Installing SQL Server 2012 failover cluster

Part 3: Adding a New Instance to Cluster

How-to steps

Please note that Node 1 and Node 2 are interchangeable identifiers for clusters nodes. Important point is that part 1 is to be executed on node 1 and this steps  is to be done on the other node. Make sure you login with the cluster admin account defined in your domain.


Screen capture

1- Start your SQL 2012 Server installation media on Node 2 and Click 'Installation'


2. Click 'Add node to a SQL Server failover cluster' link on the right


3. OK (fix if any Failed found, of course)


4. Next


5. Setup Support Rules

Wait for Rules check. Once done make sure no failed task. Evaluate warnings for your environment (remember the VM is not connected to Internet). Then click Next


6. Provide PK key. Then Next

sql 2012 PK part 2

7. Check the 'I accept the license terms'. Then Next


8. Next


9. Next


10 - Provide engine and agent service account passwords. Then Next


11. Next


12. Next


13. Evaluate the settings. Then Install


14. SUCCESS. Close.



In this article, we have demonstrated adding a second node into the cluster. I am sure you have also found it straight forward and easy to accomplish. Right?

Take care and see you in the next post.

Comments (4)

  1. Chitra says:

    Awesome post!  Thanks!

  2. CoolDBA says:

    If you want to add a DR servers, do you need to create another cluster on DR to identical to Prod or add the DR nodes to the existing cluster? e.g. cluster is active/active on Prod

  3. Mecit Atmaca says:

    @CoolDBA, Please note that SQL 2012 release introduced dramatic changes on terms and architecture. There are significant enhancements made with this release regarding HA and DR. What you could do is to have a multisite failover cluster (yes, nodes can be dispersed geographically) utilizes Availability Groups (that replaces mirroring and log shipping) by implementing SQL 2012 AlwaysOn feature. Please check here for further details: <a href="msdn.microsoft.com/…/ff929171.aspx"> Failover Clustering and AlwaysOn Availability Groups (SQL Server) </a>

Skip to main content