Backing up and restoring Lync Server 2013
Topic Last Modified: 2013-02-21
In this section, you’ll find the best practices for backing up your Lync Server 2013 data, and for restoring it if you have a failure. These best practices apply to the following situations:
An entire Lync Server pool of any type (Front End Server, Edge Server, Mediation Server, Persistent Chat Server, or Director), or an individual server in one of these pools.
The Central Management Server
A Standard Edition server
An Enterprise Edition Back End Server
A File Store
An Archiving database, Monitoring database, or Persistent Chat database
This section does not include information about restoring an entire site or for developing a standby site. For details about developing a disaster recovery solution with paired Front End pools, see Planning for high availability and disaster recovery in Lync Server 2013. This is the recommended method for planning for disaster recovery.
If you have deployed paired Front End pools, if one of these pools fails and becomes unrecoverable, you can restore this pool with a new fully qualified domain name (FQDN) from its paired pool. For details on the steps to perform this recovery, see Failing over a pool in Lync Server 2013. Additionally, if you later want to recreate a failed and unrecoverable pool that was part of a Front End pair, you can use the steps in Performing an ABC Front End pool failover in Lync Server 2013.
The methodology described in this document involves special considerations during the planning phase. For details, see Establishing a backup and restoration plan for Lync Server 2013.
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.