SQL Server 2016 no-domain cluster configuration AlwaysON availability group graph tutorial, 2016 alwayson

SQL Server 2016 no-domain cluster configuration AlwaysON availability group graph tutorial, 2016 alwayson

Both windows server 2016 and SQL server 2016 can be used to allow users not to join the AD, saving a lot of management operations, and there is no need to worry about the impact of domain control problems on servers.

This test version: window server 2016 datacenter + SQL server 2016 ctp

IP address planning:

Host Name	IP	Description
Ad	192.168.2.2	Domain Server (kk.com) windows xp
Server131	192.168.2.131	Node
Server132	192.168.2.132	Node
Winclt2016	192.168.2.139	Cluster
Testag_listener	192.168.2.135	Availability group listener

Requirement: each node creates a local computer user. The account and password must be consistent and belongs to the Administrator group "Administrators ".

You can also use the default administrator Account administrator. If you are not using the default administrator Account administrator, configure registry to add LocalAccountTokenFilterPolicy to 1.

As follows:

new-itemproperty -path HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System -Name LocalAccountTokenFilterPolicy -Value 1 

This test uses the default administrator Account: administrator.

Because you do not need to add the computer to the domain, but the DNS still needs to be configured, you must first install the Domain Server, which is skipped here ......

Configure Nic information for each node:

The server does not add AD, but the domain suffix needs to be configured as follows:

After the configuration is complete, restart the node computer, and each node can ping each other by the server's full name.

In Domain Server Management, manually add each node host to the domain as follows:

After adding the Domain Server, You can ping each server by the full name of the node!

After configuring the node name and ip address, add the Failover cluster tool to each node and Add. net framwork 3.5.

Select one of the nodes (which will act as the master node) to create a cluster.

Video tutorial: https://msdnshared.blob.core.windows.net/media/2016/08/WorkgroupCluster.mp4? _ = 1

Note when selecting a server! For example, you should directly enter the names of each node and then confirm the addition. If you find the server from "Browse", you may not be able to find the server; or even if you find the server, an error occurs when you confirm the server to be added.

Set the cluster name and IP address here:

Next, create a disk and configure arbitration. The operations are similar to those of previous versions.

After that, install the MS SQL server 2016 on each node, and select the local administrator account for the service account. (Same as previous versions)

Configure the alwayson availability group and perform similar operations.

However, since the node has not been added to the AD, domain authentication is not available for a long time and only certificate authentication is required. Therefore, you need to create a certificate and an endpoint. Each node performs certificate authentication and trust before configuring the availability group.

This test uses two nodes as an example. Certificates created for each node database are backed up and restored on other nodes.

-- Shared folder path: C: \ ClusterStorage \ Volume1 \ -- Node 1: Create a master key/Certificate/endpoint and back up the certificate. USE master; go create master key encryption by password = 'kk _ testag2016 '; go create certificate Cert_server131 with subject = 'cert _ server131', START_DATE = '2017-01-01 ', EXPIRY_DATE = '2017-12-30 '; go backup certificate Cert_server131 to file = 'C: \ ClusterStorage \ Volume1 \ Cert_server131.cer '; go create endpoint [testag_endpoint] AUTHORIZATION [server131 \ administrator] STATE = started as tcp (LISTENE R_PORT = 5022, LISTENER_IP = ALL) FOR data_indexing ing (ROLE = ALL, AUTHENTICATION = CERTIFICATE Cert_server131, ENCRYPTION = required algorithm aes) GO -- Node 2: Create a master key/CERTIFICATE and back up the CERTIFICATE. USE master; go create master key encryption by password = 'kk _ testag2016 '; go create certificate Cert_server132 with subject = 'cert _ server132', START_DATE = '2017-01-01 ', EXPIRY_DATE = '2017-12-30 '; go backup certificate Cert_server132 to file = 'C: \ ClusterStorage \ Volume1 \ Cert_server132.cer '; go create endpoint [testag_endpoint] AUTHORIZATION [server132 \ administrator] STATE = started as tcp (LISTENER_PORT = 5022, LISTENER_IP = ALL) FOR data_indexing ing (ROLE = ALL, AUTHENTICATION = CERTIFICATE Cert_server132, ENCRYPTION = required algorithm aes) GO -- Node 1: CREATE another node certificate use master; go create certificate Cert_server132 from file = 'C: \ ClusterStorage \ Volume1 \ Cert_server132.cer '; GO -- Node 2: CREATE other node certificates USE master; go create certificate Cert_server131 from file = 'C: \ ClusterStorage \ Volume1 \ Cert_server131.cer '; GO

After completing the configuration, you can configure the availability group. You can set three availability groups for Synchronous submission.

Endpoint configuration: enter the name of the created endpoint. after entering the name, "port number" + "endpoint name" + "encrypt data" becomes unchangeable. Other configurations are the same.

Download detailed steps: alwaysonno-domain high-availability group 2016.rar

The above is a graphic tutorial on configuring AlwaysON availability group in SQL Server 2016 without a domain cluster. I hope it will help you. If you have any questions, please leave a message, the editor will reply to you in a timely manner. Thank you very much for your support for the help House website!