Windows 2012 configuration failover (for SQL Server, AlwaysOn)

SQL Server AlwaysOn technology relies on the Windows WSFC feature, the Failover Clustering feature. Both Liunx corosync+pacemaker and Oracle Grid Infrastructure need to complete the control of cluster resources and resource isolation. WSFC transfers and isolates the resources associated with SQL Server, such as nodes, IP, disk resources, and so on. This article describes the installation of Windows WSFC and prepares you for an AlwaysOn installation.

I. Preparing to install a failover cluster

Ensure that the nodes in the cluster are joined to the domain (in this case, 2 nodes)
Ensure that domain accounts are added to the native Administrators group
You can refer to: Install Windows 2012 domain control (for SQL Server AlwaysOn)

Second, install the failover cluster (all nodes need to install this feature) 1) Click Taskbar Server Manager to open the server Management dashboard

Click on the "Manage" menu and select "Add Roles and Features"
Click Next, select Role-based or feature-based installation, click Next
Select the local server, click Next until the Feature module, select. NET 3.5, and the subsequent installation of SQL Server will use the
Drag the scroll bar and select Failover Cluster

2) The following is the addition of a failover cluster

3) Click Install

4) After installation, click the Close button three, configure WSFC1) all cluster nodes after the failover feature is installed, on any node, log in as a domain administrator for cluster configuration

2) Click Create Cluster

3) Start the Create Cluster wizard

4) Add all servers that need to be added to the cluster to the list

5) Validate before creating the cluster

6) Verifying the configuration

7) Select Run All tests

8) Click Next to start validation

9) Verify the results, such as

10) Configure the cluster access point, for example, specify the cluster name and VIP address

11) Create a list of clusters, click Next to create

12) Create a summary after completion

13) View the clusters you have created

14) Configuring cluster quorum

Create a folder on the domain control and share it (this folder is not recommended for domain control in a production environment) to ensure that the 2 node has access to the shared folder of the node (currently 2 nodes, mainly the general practice of meeting the cluster cardinality node deployment)
Here we create a folder when we enable the file share witness

15) Start the Configure Cluster Quorum wizard

16) Select the quorum witness

17) Select Profile Share Witness

18) Configure shared file witness path

19) Create a shared folder and its permissions

20) Confirm

21) Configuration Complete

22) View Arbitration

23) Finish

Windows 2012 configuration failover (for SQL Server, AlwaysOn)