1 Dean Suzuki Blog Title: Lync 2013 Site Resiliency (Step 4 - Building A Second Lync Pool and Enabling Site Resiliency) Created: 2/7/2013, Updated (2/12/2013) Description: We have been building a Lync 2013 environment in an Enterprise configuration. This is the fourth step in the process. Here is a recap of what has been done in the prior posts. o In Step 1: We built the SQL back-end database for the Lync Enterprise Pool o In Step 2: We built one of the Lync Front End Enterprise Edition servers o In Step 3: We built a second Lync Front End Enterprise Edition server so that we will have a highly availability solution. High availability means that the Lync service can suffer a server going down and another server will pick up the load and maintain the service in a single location. o In this step (Step 4): We are going to create a second Lync Pool in a different location so that the Lync service has a site resiliency. Site resiliency enables the Lync service to continue operating in the scenario that a disaster hits one geographic location (e.g. Irvine California). The Lync service can be transitioned to the other location and run from that location. There is a new service in Lync 2013 called the Lync Backup Service that replicates the user and conference information between Lync pools. See this article (http://technet.microsoft.com/en-us/library/jj205293.aspx) for more information. Lync Front End (Step 2) SQL Database (Step 1) Lync Front End (Step 3) Lync Front End (Step 4) SQL Database (Step 4) Lync Front End (Step 4) Lync Backup Service (Step 4) Please note that in Lync 2013 the best practice is to have three Lync Front-End Enterprise Edition servers in a pool. To add a third server to the pool, just repeat this post to build a third
35
Embed
SQL Database (Step 1) SQL Database (Step 4) · PDF file05.02.2013 · On a front end server in the second Lync pool, execute the following: o Invoke-CsBackupServiceSync –PoolFqdn
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
1
Dean Suzuki Blog
Title: Lync 2013 Site Resiliency (Step 4 - Building A Second Lync Pool and Enabling Site Resiliency)
Created: 2/7/2013, Updated (2/12/2013)
Description:
We have been building a Lync 2013 environment in an Enterprise configuration. This is the
fourth step in the process. Here is a recap of what has been done in the prior posts.
o In Step 1: We built the SQL back-end database for the Lync Enterprise Pool
o In Step 2: We built one of the Lync Front End Enterprise Edition servers
o In Step 3: We built a second Lync Front End Enterprise Edition server so that we will
have a highly availability solution. High availability means that the Lync service can
suffer a server going down and another server will pick up the load and maintain the
service in a single location.
o In this step (Step 4): We are going to create a second Lync Pool in a different location
so that the Lync service has a site resiliency. Site resiliency enables the Lync service to
continue operating in the scenario that a disaster hits one geographic location (e.g.
Irvine California). The Lync service can be transitioned to the other location and run
from that location. There is a new service in Lync 2013 called the Lync Backup Service
that replicates the user and conference information between Lync pools. See this
article (http://technet.microsoft.com/en-us/library/jj205293.aspx) for more
information.
Lync Front End (Step 2)
SQL Database (Step 1)
Lync Front End (Step 3)
Lync Front End (Step 4)
SQL Database (Step 4)
Lync Front End (Step 4)
Lync Backup Service(Step 4)
Please note that in Lync 2013 the best practice is to have three Lync Front-End Enterprise
Edition servers in a pool. To add a third server to the pool, just repeat this post to build a third
2
server. See http://technet.microsoft.com/en-us/library/gg412996.aspx for more information.
We are building the architecture described on: http://technet.microsoft.com/en-
http://technet.microsoft.com/en-us/library/jj721939.aspx ; Managing Lync Server 2013 Disaster
Recovery, High Availability, and Backup Service
http://technet.microsoft.com/en-us/library/gg398347.aspx ; Planning for Central Site Voice Resiliency
Disclaimer:
Contents of this blog and article represent the opinions of Dean Suzuki, and do not reflect the views of my employer. (C) 2012 Dean Suzuki, All Rights Reserved
Procedure:
Table of Contents 1 Build a Lync SQL Back-end: ................................................................................................................... 4
2 Build Lync Front End Servers: ................................................................................................................ 4
2.1 Building the First Lync Front End Server in the Second Pool ........................................................ 4
2.1.1 Create Lync 2013 FE VM: ...................................................................................................... 4
2.1.2 Prepare Lync Server - Load Operating System Pre-requisites .............................................. 4
Lync 2013 uses the same install process in that it use the CMS to learn the configuration of the server.
20
2.1.9 Setup Lync Components
21
22
2.1.10 Request certificates
2.1.10.1 Request Default Certificate
23
24
25
26
2.1.11 Start Lync Services
27
Then check that the Lync services are started.
2.1.12 Perform Microsoft Updates on the Server. Then, perform Updates on the server
2.2 Building the Second Front End Server in the Pool Build the second Front End Server in the Pool. The process to build the second server in the second
pool is very similar to creating the second server in the first pool. So rather than pasting all those steps
in, we were refer you to the following post that outlines the process to add a second server to the pool.
o http://deansuzuki.net/2013/02/05/technology-adding-a-second-lync-front-end-server-
to-a-pool/
3 Enabling Replication between Pools To assure voice resiliency in the event of a central site failure, the primary Registrar pool must have a
single designated backup Registrar pool located at another site. The backup can be configured by using
Topology Builder resiliency settings. Assuming a resilient WAN link between the two sites, users whose
primary Registrar pool is no longer available are automatically directed to the backup Registrar pool
(taken from http://technet.microsoft.com/en-us/library/gg398347.aspx)
3.1 Configure Pool Resiliency in Topology Builder To configure the pool resiliency, launch Topology Builder
Navigate to the Enterprise Edition Front End pool in Irvine (Lync Server > IrvineMTC > Lync Server 2013 >
Enterprise Edition Front End pools > Poolname (pool13a.irvlab.mtcdemos.net)