Module 4. Planning and Designing Load Balancing

Transcription

1 Module 4 Planning and Designing Load Balancing

2 Designing Lync Server 2010 Jump Start Day 1: Topology Design Mod 1: Lync Server 2010 Design Process Overview Module 2a: Designing a LS 2010 Topology ONE Module 2b: Designing a LS 2010 Topology TWO Module 3a: Designing for Conferencing and Ext. Scenarios ONE Module 3b: Designing for Conferencing and Ext. Scenarios TWO Module 4: Planning and Designing Load Balancing Connectivity Day 2: Infrastructure & Network Design Module 5: Designing a Mediation Server Topology Module 6a: Designing Voice Infrastructure ONE Module 6b: Designing Voice Infrastructure TWO Module 7: Designing Exchange Server UM Integration Module 8a: Creating a Network Design ONE Module 8b: Creating a Network Design TWO Day 3: Services & Maintenance Design Module 9: Designing Location Services in Lync Server 2010 Module 10: Designing Response Group Services Module 11: Designing Resiliency Module 12: Designing for Backup and Disaster Recovery Module 13: Designing Monitoring and Archiving Server Module 14:Planning a Migration to Lync Server 2010

3 Module Agenda Load Balancing Requirements Planning for Load Balancing DNS-based Load Balancing Hardware Load Balancing Designing a Coexistence Strategy

4 Discussion: Assess Load Balancing Requirements Do you think that the deployment of load balancing is a mandatory requirement for environments with a large numbers of users? How does Lync Server 2010 provide for easier configuration of hardware load balancers? Describe a scenario where DNS load balancing might not be a preferred solution.

5 DNS and Hardware-Based Load Balancing Lync Server 2010 Hardware Load Balancing DNS Load Balancing

6 Planning for Load Balancing Infrastructure Plan for keeping all Front End Servers in the Lync Server 2010 pool operational Plan for identifying the components that do not support load balancing and work on mitigation strategies Plan for using hardware devices that have firmware updates to support DNS load balancing Lync Server 2010 Plan for migrating previous versions of servers and clients to Lync Server 2010

7 Planning for Load Balancing Servers and Services Assess load balancing requirements from a scalability perspective servers and services Discuss the overall load balancing plan with project stakeholders Determine the load balancing requirements for each server role Determine the load balancing requirements for each service

8 Planning for Coexistence Lync Server 2010 Hardware Load Balancing DNS Load Balancing Office Communication Server Clients Lync Server 2010 Clients

9 Discussion: Pros/Cons of Load Balancing When compared with a hardware load balancer, does DNS load balancing provide an intelligent method of load balancing client connections to a Front End Server pool? Considering that DNS load balancing is so easy to deploy and manage, shouldn t this be the default choice for all Lync Server 2010 deployments?

10 Lesson 2: Designing Load Balancing Discussion: Choosing the Appropriate Load Balancing Solution Designing DNS-Based Load Balancing Designing Hardware-Based Load Balancing Designing for Servers and Services for Load Balancing Guidelines for Deploying DNS Load Balancing for Front End Server Pool Designing a Coexistence Strategy Discussion: Sample Load Balancing Design

11 Discussion: Choosing Load Balancing Solution To save costs, a customer might want to use Windows Network Load balancing for load balancing HTTP/HTTPS traffic. Would you recommend this approach? Can DNS-based load balancing be considered a resilient load balancing mechanism? Is it equivalent to the use of redundant hardware load balancers?

12 Designing DNS-Based Load Balancing Lync Server 2010 Enterprise Pool Pool Name: pool.adatum.com Hardware Load Balancer (for web traffic) VIP: Front End Server: van-fe01.adatum.com ( ) Front End Server: van-fe02.adntum.com ( ) 3 1: DNS load balancing-aware client resolves SRV record and queries for IP address for pool.adatum.com DNS Server 2: DNS returns all A records for pool.adatum.com: and : Client initiates connection to random Front End Server Lync 2010 Client

13 Designing DNS-Based Load Balancing Lync Server 2010 Enterprise Pool Pool Name: pool.adatum.com Hardware Load Balancer (for web traffic) VIP: Front End Server: van-fe01.adatum.com ( ) Front End Server: van-fe02.adntum.com ( ) 3 1: Client resolves SRV record and queries for IP address of pool.adatum.com DNS Server 2: DNS returns VIP of hardware load balancer: : Client initiates connection to hardware load balancer Lync 2010 Client

14 Designing Servers & Services for Load Balancing Scaling requirements Organizational requirements Number of users in a given site Requirement for high availability or resiliency Mediation Server Director Server Enterprise Edition Front End Server LYNC SERVER 2010 Server Roles that support load balancing Edge Server

15 Deploying DNS Load Balancing Guidelines Scenario: Should I deploy DNS Load balancing on a Front End Server pool? Is DNS load balancing supported? Is DNS load balancing recommended? Is hardware load balancer (only) recommended? All or most users homed in the pool run Lync Server 2010 clients. Many users homed in the pool still run older clients. Interoperates only with other Lync Server 2010 servers. Interoperates with many servers running earlier versions of Office Communications Server. Running Exchange UM with Exchange 2010 SP1 (or not running Exchange UM) Running Exchange UM with earlier versions of Exchange Server

16 Designing a Coexistence Strategy Provide hardware load balancing for all clients/servers Retain existing hardware load balancing setup for legacy clients and legacy servers Provide load balancing for Lync Server 2010 clients and server only Lync Server 2010 Hardware Load Balancing DNS Load Balancing Office Communication Server Clients Lync Server 2010 Clients

17 Discussion: Sample Load Balancing Design In this scenario, which are the servers that would require load balancing? For load balancing SIP traffic, which form of load balancing would you deploy? Federated Organizations with Office Communications Server R2 Edge Servers Perimeter Perimeter DNS load balancer on Network Network external Edge Active Directory Active Directory DNS Internal Network WAN Edge Array Hard load balancer on external Edge Front End pool DNS load balancer on enterprise pool to manage SIP traffic Lync Clients Federated Organizations with Lync Server 2010 Edge Servers Monitoring Server Lync Clients

18 Module Review and Takeaways Module Review Questions and Answers Real-World Issues and Scenarios

19 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Azure, System Center, Hyper-V 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.