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

In the previous article, I wrote some articles on the deployment configuration of SharePoint 2016, which was demonstrated in a test environment, using only one SQL Server 2016 as the back-end database storage server.

In fact, in daily enterprise production, a SQL is far from being able to meet the high security and high stability requirements of the enterprise, so at this time we can use the always on mode of SQL Server 2012 and later versions to configure high availability.

You can use this picture to have a simple understanding of what SQL Server Always On technology is.

The AlwaysOn technology supported by SQL Server2012 combines the advantages of failover clustering, database mirroring and log shipping, but they are not the same. The unit of failover cluster is the SQL instance, and the unit of database mirroring and log shipping is a single user database.

The units supported by AlwaysOn are availability groups, which can include one or more user databases. That is, once a switch occurs, all data groups in the availability group are switched as a whole.

The underlying layer of AlwaysOn still uses the mechanism of Windows failover cluster for monitoring and transfer, so the Windows Cluster needs to be established first, but the databases in the availability group do not have to be stored on shared storage, but can be stored on the local disk.

For a specific description and explanation of Always On, you can refer to General du's article http://dufei.blog.51cto.com/382644/1384210/.

All right, don't say much, let's do it!

First of all, we deploy two SQL Server 2016 servers and add two network cards to them, one is the production network segment, the other is the heartbeat network.

Note: it is not difficult to install SQL Server 2016. You can refer to my previous article http://horse87.blog.51cto.com/2633686/1870952.

Then let's install the Windows failover cluster component

Check the failover cluster component

Then start the installation.

After the installation is complete, we open the failover Cluster Administrator in the Administrative tools panel

Right-click and create a cluster

Go to the wizard page

Add the two SQL Server 2016 servers we need to join the cluster

To be on the safe side, we choose the pre-verification test.

Start testing.

The system begins to validate the hardware and software environments of the two SQL Server 2016 to determine whether the deployment of Always On mode can be completed.

Pass the verification, the green tick is like! Click finish

At this time, enter the name of Cluster, then determine the production network segment where the two SQL Server 2016 are located, and set a new IP address for the cluster in the same network segment.

Next, confirm the previous configuration information

Finally, the cluster deployment is complete.

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.