Plan for high availability and disaster recovery in Skype for Business Server
Skype for Business Server offers high availability with server pooling, disaster recovery with pool pairing, and several modes of Back End Server high availability, including AlwaysOn Availability groups, database mirroring, and SQL failover clustering.
High availability refers to making sure that Skype for Business Server services are available even if one or more servers goes down. Disaster recovery refers to keeping services going in the event of a natural or human-caused disaster, and preserving as much data from before the disaster as possible.
As in previous versions of Lync Server, the main high availability feature for most server roles in Skype for Business Server is server redundancy via pooling. If a server running a certain server role fails, the other servers in the pool running the same role take the load of that server. This applies to Front End Servers, Edge Servers, Mediation Servers, and Directors.
Skype for Business Server also provides disaster recovery options for Front End pools. You can set up two pools in different geographical areas to serve as backups for each other. Then if you have an entire pool or site go down, the backup pool can continue to provide service to users at both sites.
Skype for Business Server also supports four modes of high availability for your Back End Servers: SQL mirroring, AlwaysOn Availability Groups, AlwaysOn Failover Cluster Instances (FCI), and SQL failover clustering.
SQL Mirroring is available in Skype for Business Server 2015 but is no longer supported in Skype for Business Server 2019. The AlwaysOn Availability Groups, AlwaysOn Failover Cluster Instances (FCI), and SQL failover clustering methods are preferred with Skype for Business Server 2019.
AlwaysOn Availability Groups are not supported with Persistent Chat Servers.
This section explains these features, and also covers what steps you can take for high availability and disaster recovery for some of your other server roles.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.