We will discuss the following:
Plan and Design a Lync Topology
Plan Lync Site Topology
Supported Lync Server 2013 Topologies
Lync Server 2013 supports
- Deployment of sites on premises in an organization
- Integration of on-premises deployments with Lync Online deployments, which is known as a hybrid deployment.
- In a hybrid deployment, some users are homed on-premises and some users are homed online.
A Lync Server 2013 on-premises deployment consists of the following:
Your deployment must include at least one central site (also known as a data center).
Each central site must contain at least one Enterprise Edition Front End pool or one Standard Edition server.
These consist of the following:
- Enterprise Edition Front End pool, which consists of one or more Front End Servers
- Separate Back End Server.
- A Front End pool can contain a maximum of twelve Front End Servers.
- For SIP traffic, we recommend DNS load balancing, but hardware load balancing is also supported.
- If you use DNS load balancing for SIP traffic, you still need a hardware load balancer for HTTP traffic.
- We recommend SQL Server mirroring for high availability of databases.
- The back-end database requires a separate instance
- You can collocate the archiving database, monitoring database, persistent chat database, and persistent chat compliance database with it.
- Lync Server 2013 also supports shared cluster for the file shares.
- Standard Edition server includes a collocated SQL Server Express database.
- Your deployment can also have one or more branch sites associated with a central site.
If you collocate Lync Server databases
We highly recommend assessing all factors that might affect availability and performance.
To verify failover capabilities, we recommend testing all failover scenarios.
Q: Can we have more than one central site?
The Lync Server 2013 Planning Tool
Two key areas of the new Lync 2013 planning tool are:
Planning Tool Itself
Planning Tool Reporting