Shulou(Shulou.com)06/01 Report--

We introduced the configuration of SQL Server 2016 Failover Cluster in the previous article. Today we continue the unfinished configuration introduction in the previous article, ready to add a node, and then configure to implement AlwaysOn configuration to achieve the single point of failure and high availability of SQL Server for SQL Server 2016 Failover Cluster+ ALwaysOn. SQL Server 2016 Failover Cluster has been configured, and then we have configured ALwaysOn. We have prepared a SQL server, but we also need to join the cluster node. The following is the configuration introduction diagram of the previous section

Hostname:DC1

Role:DC

IP:192.168.5.20

Domain:ixmsoft.com

Hostname:ISCSI

IP:192.168.5.38

Role:Storage

Hostname:S1

Role:SQL Server 2016

IP:192.168.5.41

Hostname:S2

Role:SQL Server 2016

IP:192.168.5.42

Hostname:AO1

Role:SQL Server 2016

IP:192.168.5.43

SQL-CLUSTER

192.168.5.46

SQLCLUSTER

192.168.5.47

HA-LP1

ListenIP:192.168.5.48

We first install the cluster failover role on the new node

We will now add a node to the cluster node and add a third SQL to that node

Enter the name of the new node

Verification passed

After the test passes, add nodes directly

Node addition completed

Let's look at the node information again

Let's go on to install a stand-alone SQL instance

We install functional roles

You must name an instance because a default instance has been created in the cluster; if you have installed a SQL cluster instance in the cluster, install the SQL instance on the nodes in the cluster (regardless of stand-alone

This instance name can no longer be used. In other words, you have installed the cluster SQL on cluster nodes 1 and 2

If it is the default instance, the stand-alone default instance of SQL can no longer be installed on node 3. In this case, you can choose to use the node

Install a named instance of SQL in the previous 3

Define account information

Server configuration information

We can define the data directory locally.

Installation completed

After node 3 is installed, we find that the service has no port, and the default SQL port is 1433, so we modify the default port-SQL Server configuration management

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.