Lync Server 2013 Deployment _ Lync Server Back-end high availability

This chapter describes how to build a mirrored database based on a previous single back-end Database

The Lync Server backend is the SQL Server database, and the back-end high availability differs from the previous high-availability configuration followed by Lync Integration.

High availability is an architecture that continues to provide services in the event of a hardware or software failure in a highly available architecture,

High availability is divided into two types, the first of which is the failover cluster (Failover Cluster), and the standby server is switched on after the primary server is down

The second is Network Load Balancing (NLB), the most common case of NLB is the Web server, where multiple servers share user access traffic

First explain the deployment conditions, we have previously described the installation of SQL Server, two standard or Enterprise SQL, one express, of course you can also use three SQL Standard Edition or Enterprise Edition to complete this deployment, express version is free, can save costs, All three servers need to be joined to the domain, it is best to shut down the firewall,SQL Server All grant Lyncadmin Administrator rights

= = Mirror Database Prerequisites

Remember that the database version needs to be consistent and the express version number is consistent

We need to meet some prerequisites before mirroring, then take SQL01 as an example, SQL02 operation and SQL01 consistent, SQL03 only need to join the domain after adding lyncadmin as Administrator

1) Make sure that three SQL Server TCP 1433 ports are available, and that you need to turn on port 5022 for the primary and mirror servers, the witness server is on port 7022, and my firewall is all shut down.

2) Ensure that all SQL Server is enabled for TCP/IP protocol access (enabled by default)

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/85/6C/wKiom1ei5__ibdKFAAF0Uw22YXo609.png "title=" Qq20160804145955.png "alt=" Wkiom1ei5__ibdkfaaf0uw22yxo609.png "/>

3) Turn on remote access in primary SQL and mirrored SQL and do the same in SQL02

650) this.width=650; "src=" Http://s4.51cto.com/wyfs02/M01/85/6C/wKiom1ei6QHSGQdLAAJ5ShCnGvw897.png "style=" float: none; "title=" Qq20160804150127.png "alt=" Wkiom1ei6qhsgqdlaaj5shcngvw897.png "/>

650) this.width=650; "src=" Http://s1.51cto.com/wyfs02/M02/85/6C/wKiom1ei6QKTAdttAALbtXqgveU683.png "style=" float: none; "title=" Qq20160804150409.png "alt=" Wkiom1ei6qktadttaalbtxqgveu683.png "/>

4) Modify the service account for primary SQL and mirrored SQL, restart the SQL service, and remember that both SQL needs to be modified

650) this.width=650; "src=" Http://s1.51cto.com/wyfs02/M00/85/6B/wKioL1ei62Hhmf3NAAHpoyULBeA915.png "title=" Qq20160804150946.png "alt=" Wkiol1ei62hhmf3naahpoyulbea915.png "/>

= = Create mirror database in topology

1) Define the topology of the mirrored database

650) this.width=650; "src=" Http://s1.51cto.com/wyfs02/M02/85/6C/wKiom1ei7TTRSQSTAAHfTfOQsD8834.png "title=" Qq20160804151901.png "alt=" Wkiom1ei7ttrsqstaahftfoqsd8834.png "/>

2) Prior to deployment put this tick off, now you need to specify the SQL01 Mirror port number

650) this.width=650; "src=" Http://s1.51cto.com/wyfs02/M00/85/6C/wKioL1ei7qrBATADAAHWfVPg_rw823.png "title=" Qq20160804152800.png "alt=" Wkiol1ei7qrbatadaahwfvpg_rw823.png "/>

3) Re-release requires a shared folder for backing up synchronous primary SQL and mirrored SQL data, giving lyncadmin Full Control

650) this.width=650; "src=" Http://s1.51cto.com/wyfs02/M00/85/6C/wKioL1ei7bewvG1LAAFml2562EA214.png "title=" Qq20160804152420.png "alt=" Wkiol1ei7bewvg1laafml2562ea214.png "/>

4) Successful topology release

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/85/6E/wKiom1ejBWbA44_AAAGC7s7ezRw473.png "title=" Qq20160804170524.png "alt=" Wkiom1ejbwba44_aaagc7s7ezrw473.png "/>

5) See if the database is created

At this point SQL01 is our primary database, and SQL02 is the mirror database

650) this.width=650; "src=" Http://s1.51cto.com/wyfs02/M00/85/6E/wKioL1ejBjOAqI8PAAEIGYxOEB8300.png "style=" float: none; "title=" Qq20160804170821.png "alt=" Wkiol1ejbjoaqi8paaeigyxoeb8300.png "/>650" this.width=650; "src=" http:/ /s4.51cto.com/wyfs02/m01/85/6e/wkiom1ejbjotnunbaafuu4e8dj8410.png "title=" qq20160804170832.png "style=" float: none; "alt=" Wkiom1ejbjotnunbaafuu4e8dj8410.png "/>

6) Right-click the database properties, you can see the server configuration information in the image, you can click failover to switch

650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M00/85/6F/wKiom1ejD86BR9OZAANjZ53YrZE988.png "title=" Qq20160804174933.png "alt=" Wkiom1ejd86br9ozaanjz53yrze988.png "/>

7) Shut down the SQL01 service directly or shut down the server to see if it can be automatically failed over

You can see that the theme server is already SQL02

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/85/6F/wKiom1ejEs6SNPhdAAG7QmGYzHI686.png "style=" float: none; "title=" Qq20160804175922.png "alt=" Wkiom1ejes6snphdaag7qmgyzhi686.png "/>

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/85/6F/wKioL1ejEs7iQ0q4AAF8Dd1hG2E347.png "style=" float: none; "title=" Qq20160804180213.png "alt=" Wkiol1ejes7iq0q4aaf8dd1hg2e347.png "/>

8) If the SQL01 service is started again at this time, SQL02 will still be the main body and need to be manually switched if no failure occurs.

Next chapter deploying Lync Front-end high availability

If you encounter any errors during deployment, the following message is resolved together ...

This article from "Sameold" blog, declined reprint!

Lync Server 2013 Deployment _ Lync Server Back-end high availability