SQL Server 2012 clustered instance
We have reached the last article of this series. To close this series out,let’s discuss how to add a node into an existing SQL Server clustered instance. The following steps are performed either to add one more node to some already installed clustered instance, or to continue the installation of a brand new clustered instance.
Configure Server
We will repeat most of the steps done on Node (1)
1.Now open Server Manager , select Local Server , right click on Ethernet(), and rename it to Domain.
2.Double click on domain, then select Properties to set a static IP address. Uncheck these three options:
4. We can change the computer name and join it to "SQL2" domain.
2.Double click on domain, then select Properties to set a static IP address. Uncheck these three options:
- Linked-Layer Topology Discovery Mapper I/O Driver
- Linked-Layer Topology Discovery Responder
- Internet Protocol Version 6 (TCP/IPv6)
4. We can change the computer name and join it to "SQL2" domain.
Heartbeat connection
After restarting the SQL1 virtual machine, we need to add a new heartbeat connection.
1. Right Click on the virtual machine name & select Setting
2. From Virtual Machine Setting click Add, to add a new network adapter and click Next.
3. Select "Custom: Specific virtual network", and from the list and click finish.
4. Sign in to SQL1 by using domain Administrator login.
5. Open "Server Manager", click on "Local Server", select Ethernet1, and rename it to "HeartBeat".
6. Double click on HeartBeat, then select Properties to set a static IP address. Uncheck these three options:
5.Enter SQLDemo in Cluster Name , unchecked the heartbeat connection, and enter 192.168.10.200 and click on Next.
1. Run setup. In the SQL Server Installation Center click on Advanced, then click on Advanced cluster preparation.2. From Virtual Machine Setting click Add, to add a new network adapter and click Next.
3. Select "Custom: Specific virtual network", and from the list and click finish.
4. Sign in to SQL1 by using domain Administrator login.
5. Open "Server Manager", click on "Local Server", select Ethernet1, and rename it to "HeartBeat".
6. Double click on HeartBeat, then select Properties to set a static IP address. Uncheck these three options:
- Linked-Layer Topology Discovery Mapper I/O Driver
- Linked-Layer Topology Discovery Responder
- Internet Protocol Version 6 (TCP/IPv6)
7. Double click on Internet protocol version 4, select Use the following IP address, set IP address with 192.168.20.2 , and leave Default Gateway and DNS Servers empty. Then click on Advanced.
8. Click on DNS tab, uncheck Register this connection’s addresses in DNS option.
9. Finally, from WINS tab, select the Disable NetBIOS over TCP/IP option and click OK.
8. Click on DNS tab, uncheck Register this connection’s addresses in DNS option.
9. Finally, from WINS tab, select the Disable NetBIOS over TCP/IP option and click OK.
Installing .NET Framework 3.5
1. Open the Server Manager from the task bar.
2. From Server Manager Dashboard select Add roles and features. This will launch the Roles and Features Wizard allowing for modifications to be performed on the Windows Server 2012 instance.
3. Select Role-based or features-based installation from the Installation Type screen and click Next.
4. The current server is selected by default. Click Next to proceed to the Server Roles tab.
5. From add and Roles features wizard just click next.
6. Mark in the box next to .Net Framework 3.5 Features and click next.
7. Click on the link specify an alternate source path.
8. Determine the .Net Framework 3.5 from windows sources " D:\sources\sxs" & click OK.
Configure iSCSI Initiator
1.Go to Start Menu and click on Administrative Tools.
2.Double click on iSCSI Initiator and click on Yes.
3.Fill the Target: with 192.168.10.100, then click on Quick Connect and click on Done and OK.
4. Open Disk Management, then right click on Disk 1 and click Online.
5.We can see the virtual shared storage’s partition that we created former, now available in SQL2 virtual machine. If you check SQL1 disk management, it became offline on it now.
1.Go to Start Menu and click on Administrative Tools.
2.Double click on iSCSI Initiator and click on Yes.
3.Fill the Target: with 192.168.10.100, then click on Quick Connect and click on Done and OK.
4. Open Disk Management, then right click on Disk 1 and click Online.
5.We can see the virtual shared storage’s partition that we created former, now available in SQL2 virtual machine. If you check SQL1 disk management, it became offline on it now.
2.Double click on iSCSI Initiator and click on Yes.
3.Fill the Target: with 192.168.10.100, then click on Quick Connect and click on Done and OK.
4. Open Disk Management, then right click on Disk 1 and click Online.
5.We can see the virtual shared storage’s partition that we created former, now available in SQL2 virtual machine. If you check SQL1 disk management, it became offline on it now.
Add Windows Cluster feature
1. Open Server Manager and click on Add roles and features, and follow the regular steps
2. When you reach Features check the box of Failover Clustering, click on Add Features and on Next.
3. By now you should be an expert in Add Roles and Features Wizard",follow the regular steps till the setup completed successfully.
1. Open Server Manager and click on Add roles and features, and follow the regular steps
2. When you reach Features check the box of Failover Clustering, click on Add Features and on Next.
3. By now you should be an expert in Add Roles and Features Wizard",follow the regular steps till the setup completed successfully.
3. By now you should be an expert in Add Roles and Features Wizard",follow the regular steps till the setup completed successfully.
Configure Windows Failover Cluster
1. From Start Menu open Administrative Tools and open the Failover Cluster Manager.
2. In Action pane, click on Create Cluster and click on Next.
3.Enter both server names which are "SQL1" and "SQL2" and click on Add to add them to Selected servers. Then click on Next.
4.It is recommended to run configuration validation tests.5.Enter SQLDemo in Cluster Name , unchecked the heartbeat connection, and enter 192.168.10.200 and click on Next.
SQL Server Cluster Preparation
3. For the SQL Server Agent service enter the account name LOGIC\Sql_Agent which we created it after setup domain controller.
For the SQL Server Database Engine service enter the account name LOGIC\SQL_Account. Enter their passwords and click on Next.
Setup SQL Server Failover Cluster
1. Before SQL Server installation, we have to create another virtual disk. Login to your domain virtual machine DC, open Server Manager, click on File and Storage Services, click on iSCSI, right click in the middle of the window and start the New iSCSI Disk Wizard.
3. Give 10 GB and select Fixed size which is faster than other options.
4. Select New iSCSI target and click Next
5. Fill Name with Virtual2 and click Next.
Configure iSCSI Initiator on (SQL1)
2. Open iSCSI Initiator, click on Refresh, select Virtual2 which is inactive and click on Connect and on OK.
3. Open Disk Management, then right click on Disk 2 and click Online.
4. Again, right click on Disk 1 and click on Initialize Disk . Then create a 10 GB drive and name it Virtual2 .
5. From Administrative Tools, open Failover Cluster Manager. Then right click on Disks and click Add Disk. Now, add new virtual disk to cluster.
Configure iSCSI Initiator on (SQL2)
1. Login to SQL2 virtual machine (Node2) and Go to Start Menu and click on Administrative Tools.
2. Open iSCSI Initiator, click on Refresh, select Virtual2 which is inactive and click on Connect and on OK.
SQL Server Cluster Preparation (SQL1)
1. Run setup. In the SQL Server Installation Center click on Advanced, then click on Advanced cluster preparation.
3. For the SQL Server Agent service enter the account name LOGIC\Sql_Agent which we created it after setup domain controller.
2.Select Cluster Disk 2 and click on Next.
3. Enter IP address 192.168.10.201 to SQL Cluster.
4. Select Windows authentication mode , click on Add Current User and Next.
Post a Comment