In this post, I go over the steps to build a Lync 2013 environment that is site resilient. This means that the Lync service is running in two different geographic locations such that if a disaster happens at one location, the Lync service can be failed over to the other location and continue running.·
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.
- In Step 1: We built the SQL back-end database for the Lync Enterprise Pool
- In Step 2: We built one of the Lync Front End Enterprise Edition servers
- 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.
- 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.
For the step by step build procedure, see the attached document: Adding A Second Pool