Virtualizing Lync Server 2013 – Planning & Architecture

2. Virtualizing Lync Server 2013 – Planning & Architecture Campbell Gunn and Seth McClue Program Manager and Service Engineer Microsoft Corporation SERV305

3. Session Agenda Why Virtualize? Hardware and Software Approach Host hardware and software best practices Guest server requirements recommendations and guest placement Deployment Recommended practices for deploying Lync Server 2014 in virtualized environment Performance and Scale Guidelines using Key Health Indicators (KHIs) for performance and scale on Lync Server 2013 roles Testing Approach Insight into the testing approach on a pilot lab environment used by Microsoft

4. Why Virtualize? • Organizations want to: • Reduce infrastructure costs • Create more value and faster low-cost services • Reduce Total Cost of Ownership • Leverage existing resources and Server Consolidation • Decrease hardware maintenance costs • Reduce and standardize on common platform • Better capacity planning • Operational Efficiency • Improve business continuity • Increase operational flexibility • Improve the server to administration ratio

5. Why Virtualize?Lync Server 2013 • Virtualize Workloads • Designed to consume the full physical server capabilities • Resource Abstraction • Share infrastructure across many applications • CPU • Memory • Network and Disk • Utilize consistency via virtualization templates

6. Why Virtualize?Considerations • Call Quality • Key component of Lync Server performance • Depends on ready CPU resources for media transcoding • High-performing network support for media streams • Be aware the Virtualization adds a layer of abstraction (software on software) • Spike in database activity can have an impact • Stress test! • Configuration • Lync Server 2013 breaks when virtual machine portability is used • Lync Server 2013 has a rich set of application failover techniques

7. Why Virtualize?Considerations • Processor • Disable hyper-threading on all hosts • Do not use process oversubscription • Maintain a 1:1 virtual CPU to physical CPU ratio • Ensure that host servers support • Nested Page Tables and Extended Page Tables (NPT/EPT) • Memory • Do not configure dynamic memory, not supported • Do not over-commit on host servers • Hypervisor • VM portability or failover techniques such as Live Migration are not supported

8. Why Virtualize?Considerations • Network • Use Virtual Machine Queue (VMQ) • Use to optimize synthetic NIC performance • Use physical NIC segregation for host versus guest communications • VM Chimney (TCP offload) should be disabled • To minimize NIC performance impacts by offloading TCP processing • Single Root I/O Virtualization (SR-IOV) is recommended • The specific configuration depends on the host chipset and network driver/adaptor • Storage • Use fixed or pass through disks rather than dynamic disk

9. Architectural Changes

10. Lync Server 2013Architectural Changes • Back End Database Role(BE DB) • BE Database is no longer the real-time data store in Lync pool • To eliminate the single point of failure • Improve performance and scalability • Provides overall persistent blob storage of data from Front End Servers • Different in comparison to Lync Server 2010

11. Lync Server 2013Architectural Changes • Front End Server Role(FEs) • Handles transactions for users • Presence, contacts, and conferencing information • Higher requirement on resources and compute than Lync Server 2010 • A/V Conferencing Server • Part of the Front End Server role • No longer separate Monitoring nor Archiving Server role • Running as services on the Front End Server role • H264 codec for video requirement for video conferencing • Now runs on the Front End Server role • Requires additional computational resources

12. Lync Server 2013 Lab Scenario

13. Stress and PerformanceLync Server Stress and Performance Tool (LSS) • Validation Toolset • Perform stress testing of a targeted deployment infrastructure • Can target a specific usage pattern • Simulate individual workloads, such as IM and presence • Understand capacity management • Adding workloads as required (Scale-Up) • Use to provision users and simulate user loads • Ensure proper design and deployment • Support Infrastructure such as Active Directory, Certificate Services, Office Web Apps Server, Load Balancer and Reverse Proxy • Performed after technical design, before piloting • Deploy into lab (controlled environment) • Requires clients for stress testing

14. Key Health IndicatorsGood Pass • 10 Critical Key Health Indicators • Provide the basis for a “Good Pass” • Ease of checking all the indicators in each run • If testing reveals no issues in the 10 KHIs • Further analysis of the full KHI set is recommended • Network Planning, Monitoring, and Troubleshooting with Lync Server documentation http://www.microsoft.com/en-us/download/details.aspx?id=39084

15. 10 Key Health Indicators

16. Lync Server 2013 Scenario • Hardware Specs and VM Placement • Eight HPDL560 Generation 8 chassis • With four Intel E5-4650 processors and 128GB Memory • Hardware Components (BOM)

17. Lync Server 2013 Scenario • Logical Host Configuration • Each Virtual Server was configured • 12 cores and 32 GB of memory allocated • Recommendations from Physical Servers • Used Lync Server Planning documentationat http://technet.microsoft.com/en-us/library/gg398835.aspx

18. Lync Server 2013 Scenario • Host Storage Configuration

19. Lync Server 2013 Scenario Lync Server Topology

20. Lync Server 2013 Scenario • Virtual Machine Placement • Guest virtual machines were spread across hosts in order to test performance • Collocation of specific server roles was not tested. Instead, we used a logical separation of roles • Did not place FEs together on same host • Can keep virtual servers in the same pool improves resilience

21. Lync Server 2013 Scenario • Observations • Multiple tests were conducted • Optimal solution found • 10,000 user pool with three Front End Servers • Solution produced a high resource utilization • Was within critical KHI Limits • Testing is required • Due to different hardware and user model

22. Lync Server 2013 Scenario • LSS Ramp Up • Throughout testing process required a ramp up period of about 30mins • During Ramp-Up time, the following occurred: • LSS Configuration files are loaded • Users are logged in • Lync Server completes some background tasks

23. Lync Server 2013 Scenario • LSS Ramp Up

24. Lync Server 2013 Scenario • SQL Express • Four processors remained in high utilization over time • Associated with the RTCLOCAL SQL Server Express Edition instance • SQL Server Express Edition can use only four logical processors • http://technet.microsoft.com/en-us/library/ms143760.aspx • >90% utilization indicates Enterprise with 3 FEs is already at full capacity • From a SQL Server Express viewpoint and can be accommodated by addition Front End Servers • Lync Server 2013 is optimized to utilize the four cores assigned for SQL Express Compute • Key KHI is Queue Latency and Sproc Latency • Queue Latency is amount of time (in milliseconds) takes a request to leave FE’s queue toward the BE database • Sproc Latency is amount of time that it takes SQL Server database to process the request • Used to measure the effect SQL Server has on CPU utilization

25. Lync Server 2013 Scenario • SQL Express

26. Hypervisor

27. Hypervisor • Validated Hypervisors • Windows Server 2012 Hyper-V • Windows Hyper-V Server 2012 • Other Hypervisors • Windows Server 2012 R2 Hyper-V • Windows Hyper-V Server 2012 R2

28. Hypervisor • Not Recommended • Windows 2008 R2 hypervisors are supported, but this is not recommended due to guests being limited to 4 cores making this unsuitable for all Lync Server roles. • Windows Server 2008 R2 Hyper-V • Windows Hyper-V Server 2008 R2 • KB981836 “Network connection is lost on a Windows Server 2003-based Hyper-V VM” at http://go.microsoft.com/fwlink/?LinkId=201212) • Unsupported Hypervisors • Windows Server 2008

29. Hypervisor • Overhead • Typically an overhead of 6-10% • Above and beyond what the virtual guest requires • Involves both CPU and Memory • Net increase of physical servers due to virtualization layer • Virtual Machine Image Templates • Cannot run sysprep to create machine image templates after Lync Server 2013 is installed • Recommend using custom OS templates with applicable prerequisites • FEs could use templates for Internet Information Services (IIS) and Windows Media Format Runtime

30. Hypervisor • Live Migration and Quick Migration • Not supported • Technical challenges redirecting real time media traffic without an interruption • Can move a virtual machine running Lync Server between hosts • Must be shut down prior to doing the activity • An outage will be observed by a portion of the client base • Any active conferences will be ended • Memory • Dynamic Memory not supported on any roles • Memory must not be over provisioned, will starve other guest VMs

31. Hypervisor • Virtual Disks • Use fixed-sized disks • Fixed-size VHDX delivers near native-to-physical performance • Slightly higher performance than dynamically expanding VHDX files • Differencing disks and dynamically expanding disks not supported • Underlying Storage can become overcommitted • Allocated fixed-sized virtual disks to a static amount of disk space • Do not store system files on the same drives dedicated to storing VMs • Creates disk contention issues • Do not use checkpoints for the virtual machines • Checkpointing creates a new secondary drive which causes reduce performance

32. Hypervisor • Virtual IDE and SCSI • Virtual IDE controller use to boot up virtual machine • All other drives can be attached to virtual SCSI controller • Virtual SCSI can have 64 connected disks per controller and 4 controllers per virtual machine (256 Virtual SCSI disks) • Virtual SCSI supports hot-add/removal of disks, Virtual IDE disk do not • Ensure optimal performance and greatest flexibility • Virtualized Lync Server 2013 can use fibre channel storage solutions

33. Hypervisor • Guest Storage • Depends on a number of factors • Storage is locally attached, or use of SAN • Two Methods provided in Windows Server 2012 Hyper-V • In-guest iSCSI and Virtual Fibre Channel • Common best practices for Guest Storage • Operating system boot drive must be mapped to virtual IDE drive • SQL Server workloads/binaries use a virtual IDE drive or the operating system drive • Guest servers need to move between hosts then iSCSI targets are directly exposed to the guest server

34. Host Requirements

35. Host Requirements • Resource Over-Allocation • Do not over-allocate the CPU • Mixing Physical and Virtual Servers • Mixing of physical and virtual servers in the same pool is not supported • Virtual Front End server pool and physical Back End Servers is supported • Physical to Virtual CPU Ratio • Physical to virtual CPUs ratio should not be oversubscribed • Oversubscription of CPU cores of host running Lync Server media workloads not supported and not recommended on other workloads • Antivirus • Only deploy antivirus software on VM host root partition (OS)

36. Host Requirements • Host Redundancy • Environment should be full redundant • Ensure that similar roles are spread across multiple physical platforms • Front End Server and Back End Servers are most important • Host Networking • Considerations • Each host must have a dedicated network adaptor • Share usage not supported • Correct sizing should be used to handle the workload on the host server • KB968703, “Microsoft Support Policy for NIC Teaming with Hyper-V” at http://go.microsoft.com/fwlink/?LinkId=211073 • Enable VLAN tagging on the host NIC • Implement (multiple) VLANs on the guests to optimize network traffic from FEs to clients and FEs to Bes

37. Guest Requirements

38. Guest Requirements • Guest Core Requirements • Hyper-V has not limitations to the number of CPU Cores on Windows Server 2012 • Other third-part hypervisors may be limited to 8 cores • Lync Server 2013 running on physical hardware does not have any limit to CPU cores • Guest Operating System • Windows Server 2012 • Windows Server 2012 R2 preferred • Windows Server 2008 R2 • Windows Server 2008 SP2 is not supported

39. Guest Requirements • Legacy versus Synthetic Virtual NIC • Using Legacy adapter results in lower data transfer • Emulates Intel 21140-based PCI Fast Ethernet Adapter (usually 1GBps or faster) • Synthetic Adaptors preferred • Dedicated VMBus to Virtual and Physical NIC Communication • Single Root IO Virtualization (SR-IOV) • Available in Windows Server 2012 • Provides extensions to PCI Express devices like network adapters to separate access which creates a virtual switch • Legacy network adapter is not supported

40. Guest Requirements • IPv4 and IPv6 • Not recommended to mix IPv4 with IPv6 • Disable Virtual DVD/CD Drives in Guest • Prevents allocation resources being allotted for their function

41. Session Summary Why Virtualize? Hardware and Software Approach Host hardware and software best practices Guest server requirements recommendations and guest placement Deployment Recommended practices for deploying Lync Server 2014 in virtualized environment Performance and Scale Guidelines using Key Health Indicators (KHIs) for performance and scale on Lync Server 2013 roles Testing Approach Insight into the testing approach on a pilot lab environment used by Microsoft

42. Questions?

44. Microsoft Pavilion Demos, Speakers, Demos, Lync Room System, Experts, Demos, a Bar....and more Demos

45. ATTENDEE PARTY Wednesday, February 19th6:30pm-9:30pmHakkasan, MGM Grand Brought to you by When it comes to Vegas nightclubs, it doesn’t get any hotter than Hakkasan. And when it comes to opportunities to connect and reasons to party, no one does it better than Lync Conference! Our attendee party has a full lineup: an open bar, awesome food, and one of the best DJs that Vegas has to offer. Don’t miss out on the fun—stop by at 6:30pm and kick off and evening to remember. Come together.

46. HANDS-ON LABS LRS Monday, February 17 Tuesday, February 18 Wednesday, February 19 Thursday, February 20 3:00pm – 9:00pm 10:30am – 9:00pm 7:30am – 9:00pm 8:00am –1:30pm Wednesday, February 19 8:30am – 9:45am 10:15am – 11:30am 1:00pm – 2:15pm 2:45pm – 4:00pm 4:30pm – 5:45pm Thursday, February 20 9:00am – 10:15am 10:45am – 12:15pm 12:45pm – 2:00pm LOCATIONPinyon3 LOCATIONCopperleaf 12 You can also access labs on MyLync! Tuesday, February 18th5:00pm – 7:00pm

47. MyLync allows you to create a custom experience and network with the Lync Community both online and in person. • With MyLync, you can: • Build your own personalized calendar while browsing all available sessions • View breakout session material including PPTs and Videos within 48 hours of each session • Participate in the Community and find people in your social networks who are attending and interact with speakers • Arrange meetings or social activities • Navigate the Exhibit Hall floor plan and learn more about our Sponsors • Fill out evaluations to win prizes Log into MyLync at http://mylync.lyncconf.comFor MyLync support, please visit the Registration Desk.* * Please note that adding a session to your calendar does not reserve a seat. Seating is on a first-come, first-served basis.

48. Birds of a Feather Birds of a Feather flock together! Join daily breakfast discussions of relevant topics by sitting in the separately designated areas of the Meal Hall. Seating will be sorted in a different way for each Birds of a Feather breakfast: Wednesday, February 19: Where are you from? Asia/Pacific, Eastern & Central Europe, Latin America, Middle East & Africa, US (West, Central & East) and Canada, Western Europe Thursday, February 20: What is your interest? Best Practices, Business Value, Clients & Mobility, Lync Meetings and Video, Lync Online, Networking, Platform, Server & Manageability, Voice

49. Fill out evaluations to win prizes Fill out evaluations on MyLync or MyLync Mobile. Prizes awarded daily.

50. © 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.