Windows 2008 Dual-Machine cluster configuration (for SQL Server)

The Windows2008 cluster is configured here and will be used for SQL Server 2008 dual-machine failover clusters, where SQL Server's cluster is based on the Windows cluster implementation. Windows 2008 clusters are easier to implement as long as you plan for IP and disk allocation, you can always configure them by the window interface.

Server Requirements:

This test requires 3 servers, 1 domain controllers (Windows 2003, dual Nic optional), 2 cluster nodes (Windows Server 2008, dual network cards).

Required Tools:

WindowsInstaller 4.5 Redistributable

Microsoft.NET Framework 3.5 Service Pack 1

Starwindvirtual SAN? Free

Description: The Windows Installer and net Framework 3.0 default installation, Starwind for simulating networked storage (refer to Starwind emulation of ISCSI for networked storage management)

Network configuration:

	Node one (Win8-servera)	Node two (win8-serverb)
Public IP	192.168.2.201	192.168.2.202
Private IP	10.10.10.201/24	10.10.10.202/24
Dc/dns	192.168.2.9/192.168.2.1
MSDTC	192.168.2.204
Cluster Management IP	192.168.2.200

Shared Storage Letter Settings: (for testing, so set smaller)

Arbitration panel (D)	1GB
MSDTC shared disk (F)	2GB
Database share disk (E)	3GB

"Windows cluster main steps"

1. prophase :

1.1. Configuring the domain environment

1.2. Configure network shared storage

1.3. Configure each node network

2. Configure in 2 nodes :

2.1. Add a role : Application Server

2.2. Add features : failover cluster set

3. in any of the 1 nodes ( which will be the primary node ):

3.1. failover cluster Management : Verifying the configuration

3.2. failover cluster Management : Create a cluster

3.3. Disk Management : disk connection and create a simple volume

3.4. failover cluster Management : Quorum configuration

3.5. failover cluster Management : Distributed Transaction Coordinator (DTC) Configuration

Domain environment deployment does not indicate that networked storage reference Starwind emulates ISCSI for networked storage management

1.3. Configure each node network

Node 1:

Nic 1:ip:192.168.2.201, subnet mask: 255.255.255.0, Gateway: 192.168.2.1,dns:192.168.2.1

Nic 2:ip:10.10.10.201, subnet mask: 255.255.255.0

Node 2:

Nic 1:ip:192.168.2.202, subnet mask: 255.255.255.0, Gateway: 192.168.2.1,dns:192.168.2.1

Nic 2:ip:10.10.10.202, subnet mask: 255.255.255.0

Verify that you can see the same 3 offline disks in 2 nodes.

2.1. Add a role : Application Server

The Application Server role is added to all 2 nodes and is also useful for installing SQL Server in the future.

Open Server Manager , click the roles tree menu and click Add roles . As with the installation steps.

Installation is complete! ~

2.2. Add features : failover cluster set

Failover clustering enhances the high availability of services and applications and enables other clusters to recognize that node. add a failover cluster to all 2 nodes.

Open Server Manager , click on the function tree menu and click Add Feature . As with the installation steps.

Configuration Complete! ~

Now select Node 192.168.2.201 as the first node (master node), and the following operations are performed on that node.

3.1. fail-over cluster management : Verifying the configuration

Start-Programs-Administrative Tools--open failover Cluster Management , click Verify Configuration ...

Verification Complete! ~

3.2. fail-over cluster management : Create a cluster

If the above validation is correct, you can continue to create a cluster. In failover Cluster Management , click Create a cluster ...

When the cluster is added, you can see the clustered virtual machine in the domain control computer.

3.3. Disk Management : disk connection and create a simple volume

After the cluster is added, the disks are automatically added to the cluster and can be added manually if not added.

Bring 3 of network disks online and initialize to create a simple volume .

Disk Creation Complete! ~

3.4. fail-over cluster management : Quorum configuration

The arbiter does not need a separate server here, but instead uses disk as the arbiter for detecting and coordinating failover.

Connect to a cluster with failover Cluster Management , right-click Clustered servers-more operations-configure cluster quorum settings

The quorum disk configuration is complete! ~

3.5. fail-over cluster management : Distributed Transaction Coordinator (DTC) Configuration

The Distributed Transaction Coordinator (DTC) service is used to reconcile the following transactions: Two or more transactions are updated to protect resources, such as databases, message queues, file systems, and so on. These transaction-protected resources may be located on a single computer or on multiple networked computers.

Right-click Services and Applications , tap Configure service or application to open configuration

Distributed Transaction Coordinator configuration Complete! ~

For the network configuration in the node, click on the Network Tree directory in the cluster to view it. The network configuration in the node is recognized by default in the cluster and is not required here.

At this point, the Windows cluster configuration is complete! ~

For the first time configuration, there may be unreasonable settings where it is welcome to point out and learn from each other.

The text is illustrated, and then a complete download link is compiled.

OK, then log in to install SQL Server database! ~

Reference:

Install SQL Server in a Windows server Cluster Part 1
Install SQL Server in a Windows server Cluster Part 2
Install SQL Server in a Windows server Cluster Part 3
Install SQL Server in a Windows server Cluster Part 4

Create a Windows2008 cluster

Windows + SQL 2008 cluster installation configuration detailed

Windows 2008 Dual-Machine cluster configuration (for SQL Server)