1. Ewan MacKellar Andrew Ehrensing

2. 2

3. ScenarioOCS 2007 R2Lync 2010Lync 2013 HA: server failure  Server clustering via hardware load balancing (HLB)  Server clustering via HLB and DNS load balancing  Same as Lync Server 2010 HA: pool Back End failure  SQL Backup & Restore  SQL clustering & storage area network (SAN)– based shared storage  Use synchronous SQL mirroring between two Back Ends w/o the need for shared storage  Support auto failover (FO)/failback (FB) (w/ witness) and manual FO/FB  Integrate with Planning Tool, Topology Builder, and Lync Server Control Panel DR: pool failure  SQL Backup & Restore  Voice resiliency for datacenter pools and SBA  Metropolitan site stretched pool for presence and conferencing resiliency  Maintain voice resiliency in Lync 2010  Enhance PSTN voice w/ trunk auto FO/FB  Support presence and conferencing resiliency via pool pairing  Active-active mode in two geographically dispersed datacenters  Backup Service for real-time persistent data replication between two paired pools  Manual Failover/Failback cmdlets  Integrate with Planning Tool, Topology Builder, and Lync Server Control Panel  Does not include RGS/CPS/CAC/CDR DR: Site failure  SQL Backup & Restore  Metropolitan site stretched pool  Leverage pool failover model (details above)  Must be Lync 2013 pools  Stretched Pool not supported 3

5. Seamlessly failover within Pool No data loss incurred Primary FEBackup1 FEBackup2 FEBackend DB

6. Lync requirements Services for MCU Factory, Conference Directory, Routing Group, LYSS Fast failover with full service Automatic scaling and load-balancing User Failover model Users are mapped to groups Each group is a stateful service with 3 replicas User requests are serviced by primary replica User Group 1 User Group 2 Group 1 Group 3 Fabric node Group 2 Fabric node Group 1 Fabric node Group 3 Fabric node Group 3 Fabric node Group 1 Fabric node Group 2 6

7. 7

8. 8 Total Number of Front End Server in the pool (defined in Topology) Number of Servers that must be running for pool to be functional 1-21 3-42 5-63 7-84 9-105 11-126

10. 10

12. The 80’s are calling… and they want to know….. what happened to traditional clustering?

13. Lync 2013 Pool Principal Instance for DB1 Mirror Instance for DB1 Witness server instance (optional) Data flow SQL transaction

14. SQL mirroring Failover Impact 14

15. 15

18. Pool 2 18 Pool 1

19. 19

21. 21

22. User state or taskDuring failbackAfter failback completion User state of user already logged in User stays signed in and connected to backup pool. At some point user will be signed out and sign back in to the original home pool, in Resiliency mode. User remains signed in and goes into regular mode. New user logging inUser can sign in to the home pool in Resiliency mode. User can sign in to the original home pool in regular mode. Ongoing conferences organized by affected user All modalities of conference are terminated. Rejoin button will appear, but no users can rejoin while the affected user is in Resiliency mode. All modalities now work. Every participant needs to click to rejoin the conference. Ongoing conferences organized by unaffected user Conference continues and affected user can stay in the conference. Affected user is restricted to what he/she can do in Resiliency mode. Conference continues, and affected user can stay in the conference and all modalities work after user exits Resiliency mode. Scheduling or modifying scheduled meetings, creating ad-hoc conferences Not possible while user is in Resiliency mode.Available for all modalities. Presence as seen by other users in the same pool Presence unknown while user is signed into backup pool during Resiliency mode. Shows the last presence state set by the user, and presence changes will now be reflected. Contacts list and Address Book Service availability Not availableAvailable All peer-to-peer sessions and modalities Available

23. 23

26. It is recommended that Front End pools paired are within the same Region. Pairings best practices: Enterprise Edition pools  Enterprise Edition pools Standard Edition pools  Standard Edition pools Physical pools  physical pools Virtual pools  Virtual pools Topology Builder/topology validation will not prohibit pairing two pools in a way that does not follow these recommendations For example, Topology Builder allows you to pair an Enterprise Edition pool with a Standard Edition pool; however, these types of pairings are not recommended Pool capacity at 50% ; to serve all users during disaster If you pair Enterprise Edition pools, you can also implement high availability on the Back End Servers, but for pairs of Standard Edition pools, only the DR measures are available 26

27. FeatureHADR Peer-to-peer (all modalities) Presence Conferencing (all modalities) UCWA Archiving CDR / QoE X Federation PIC routing Unified Contact Store FeatureHADR Topology Builder Lync Server Control Panel Persistent Chat Planning Tool PSTN Voice / E911* CAA / CAS / PVA / GVA RGS / CPS X Call Admission Control X XMPP 27

28. Backup Registrar Relationships In Lync Server 2013, backup Registrar relationships between Front End pools are always 1:1 and reciprocal If P1 is the backup for P2, then P2 must be the backup for P1, and neither can be the backup for any other Front End pool Even though backup relationships between two Front End pools must be 1:1 and symmetrical, each Front End pool can still also be the backup registrar for any number of Survivable Branch Appliances, just as in Lync Server 2010 Lync Server 2013 does not extend disaster recovery support to users homed on a Survivable Branch Appliance 28

31. “Using Lync Standard Edition is not about user count, it’s about a customer’s Recovery Time Objective (RTO)”

32. UsersStdEnt 100001220 200001620 300002224 4000026 500003026 600003630 700004032

37. The metropolitan site resiliency solution supported for Lync Server 2010 is NOT supported for Lync Server 2013 If you have already deployed a Lync Server 2010 metropolitan site resiliency topology, when you upgrade to Lync Server 2013: Move to the Lync Server 2013 disaster recovery solution based on Front End pool pairing (recommended/supported) DO NOT STRETCH YOUR LYNC 2013 POOL 37

39. http://msdn.microsoft.com/en-au/ http://www.microsoftvirtualacademy.com/ http://channel9.msdn.com/Events/TechEd/Australia/2013 http://technet.microsoft.com/en-au/

40. 1. Download both Exchange Server 2013 and Lync Server 2013 and try in your own environmentExchange Server 2013 Lync Server 2013 2. Trial Exchange and Lync Online Trial Exchange and Lync Online 3. Contact your Microsoft or Partner Account Manager to arrange a time test drive Exchange and Lync in one of our Customer Immersion Experience Centres 4. Contact your Microsoft or Partner Account Manager to get a Lync business value assessment or an Exchange and Lync technical briefing