1 / 13

Lync 2013 Disaster Recovery Deep Dive

Lync 2013 Disaster Recovery Deep Dive. Phil Sharp | Project Leadership Associates psharp@projectleadership.net (312) 258-5320. Agenda. Disaster Recovery options in Lync 2010 Disaster Recovery scenarios in Lync 2013 Lync 2013 DR Under the Hood Lync 2013 DR Best Practices.

ardith
Download Presentation

Lync 2013 Disaster Recovery Deep Dive

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Lync 2013 Disaster RecoveryDeep Dive Phil Sharp | Project Leadership Associates psharp@projectleadership.net (312) 258-5320

  2. Agenda • Disaster Recovery options in Lync 2010 • Disaster Recovery scenarios in Lync 2013 • Lync 2013 DR Under the Hood • Lync 2013 DR Best Practices

  3. Lync 2010 Disaster Recovery Option 1 West Data Center East Data Center Primary/Backup Registrar • Two separate pools deployed in Lync topology • Weighted DNS SRV auto-configuration records • Relationship configured in Topology Builder Backup Registrar Failover WAN WAN Lync Server 2010Edge2 Lync Server 2010 Pool 2 Lync Server 2010Edge1 Lync Server 2010Pool 1

  4. Lync 2010 Disaster Recovery Option 1 Primary/Backup Registrar Pros • Easy to configure • Relatively inexpensive • Continuous voice services during failover • Can be leveraged regardless of deploymentstrategy (Standard or Enterprise) Cons • Loss of client features during failover • Restoration of data required during extended failover

  5. Lync 2010 Disaster Recovery Option 2 Metropolitan Resiliency • Single Enterprise Edition pool stretched across multiple datacenters West Data Center East Data Center Passive SQL Active SQL Lync Server 2010Edge FE 3-4 Lync Server 2010Edge FE 1-2 Low-Latency WAN

  6. Lync 2010 Disaster Recovery Option 2 Metropolitan Resiliency Pros • No loss of functionality during failover Cons • Steep technical requirements • Datacenters had to be geographically close • Relatively expensive

  7. Lync 2013 Disaster Recovery • Metropolitan Resiliency is no longer supported • Backup/restoration of data is less than ideal The Answer? Pool Pairing • The best of both previous DR options • Configured in Topology Builder • 1:1 relationship between pools • Easy to administer • Reduced capital expenditure • Provides automatic voice resiliency • All primary client-facing features are retained during failover

  8. Lync 2013 Disaster Recovery Feature Availability

  9. How is data replicated between Lync Pools?

  10. Lync 2013 Disaster Recovery Process • First fail over the Central Management Store (CMS) • Invoke-CsManagementServerFailover –BackupSqlServerFqdn <Pool02 Primary SQL FQDN> -BackupInstanceName <Named Instance> • Then fail over user data from Pool01 to Pool02 • Invoke-CsPoolFailover –PoolFqdn <Pool01> -DisasterMode

  11. Lync 2013 Disaster Recovery Process What do I do when I’ve recovered my primary site? • Fail back the user data • Invoke-CsPoolFailback –PoolFqdn <Pool01> • CMS can be failed back, or can be left on the backup pool • Same command used for failover

  12. Best Practices for Pool Pairing in Lync 2013 • Each pool should be sized to support the entire load of the user base • Active/Passive • Active/Active • Pair like pools • Deployment topologies • Physical or virtualized • Keep paired pools within the same geographic region (i.e. NA, APAC, EU) • Geographically separate pools by enough distance for DR purposes

  13. Q & A Phil Sharp | Project Leadership Associates psharp@projectleadership.net (312) 258-5320

More Related