Build SQL Server in 0 AlwaysOn second (Configure failover clustering)

This article focuses on configuring Windows failover clustering and the related issues (pits) that are encountered because AlwaysOn is a Windows-based failover cluster

Before you explain the steps, you need to understand the failover cluster quorum configuration

Quorum configuration for four clusters:

1, most nodes: This configuration does not use the quorum disk, and the so-called majority node is the number of normal nodes in the majority of cases, the cluster will provide services, or stop service. This configuration applies to clusters of for odd pages nodes, such as 5-node clusters, with a minimum of 3 normal nodes, and the cluster will serve

2, most nodes and disks: for the cluster of even nodes, he calculates the quorum disk in the number of legal quantities, for example, 4 nodes + 1 quorum disk node cluster, you can treat it as a cluster of 5 nodes, when the number of normal nodes must be at least 3, the cluster will provide service

3. Most nodes and file sharing: It is similar to (most nodes and disks), but the quorum disk changes to a file in a shared folder

4, no majority: only the disk, as long as the quorum disk offline, the cluster will stop providing services (not recommended, this way has been a long time ago)

I test environment (majority node) cluster nodes are odd (3), if the cluster node is an even number, then use the majority of nodes and file sharing (need to configure a shared folder, each node can access the shared folder, and the shared folder machine does not need to join the domain)

Attention:

Domain control does not require the Failover Cluster service and SQL Server to be installed, nor does it need to be joined to a failover cluster
All machine firewalls are turned off.
Two nodes need to install the same update, it is recommended not to turn on the Automatic Update feature, manually updated by the system administrator

SQL Server-AlwaysOn supports up to one primary replica and four secondary replicas, allowing up to three synchronous-commit availability replicas (including primary replicas), allowing up to two automatic failover replicas (including primary replicas)

Here is a step-by-step installation

1. In the Add Roles feature, select Add Failover Cluster

2, three nodes after the failover cluster is installed, log off on one of the nodes, then log on to the computer using the Dcadmin domain user, and then open Cluster Administrator

3. Open the Verification configuration

4. Configuration Wizard Next

5. Select Server

6. Add three servers (may say how to have a long004 server, the first chapter of the previous how do not have this server, this issue will be mentioned later) Note: You cannot select a domain control

7. In the Validate a configuration wizard, it is a good idea to run all the tests and to see all the settings for the cluster between the servers, including the network, shared disks, operating systems, and so on.

8. View the report

10. Create a cluster Wizard

11. Enter the cluster name and VIP

Note: This is just the management name of the cluster and the management IP, regardless of AlwaysOn , uncheck-Add all eligible storage to the cluster

12. Cluster creation is complete, because we are odd node so do not need to create a new shared folder, that is, the above has completed the configuration of this article, if the number of even need to add the shared folder reference address

Here is a small episode (or step on a pit) is mentioned above, computer: long004 (192.168.0.31) Why not in the list, this server in the next configuration of the outage and can not be used, then how to do?

A. Open failover Cluster Manager and click on the failed node (long004)

B. Right-click More actions-eviction (confirm that it is down and not, and if you are in this cluster, adding a new server to the cluster is not able to fail over the failover Cluster Validation report )

C. Reinstall system (LONG005:192.168.0.32) added to the domain environment

D. Browse for the new server name (long005)

E. Adding to the failed cluster

F. Three nodes have already been added to the fault cluster ( pit filling )

Build SQL Server in 0 AlwaysOn second (Configure failover clustering)