easthas.blogg.se - Skype web services

Please follow all the best practices which are required for HLB.

It caters all the services but you need expertise to configure and manage the HLB and it is not as simple as DNS load balancing. Second Method (Only HLB configuration): Full-fledged HLB deployment.

You need HLB if you are using Exchange UM services with prior to Exchange 2010 SP1 (applicable only for remote users).

You need HLB if you are federating with OCS and OCS R2 or federating for PIC connectivity.

But there are some caveats which you have to consider while planning this method for Edge pools: You can use this method for all the internal servers pool as well as for Edge pools. This a best method to choose as it reduces dependency on HLB and simplify the solution using DNS for most of the traffic. Therefore, there are two ways to configuring load balancing.įirst Method (Mixed mode configuration): HLB for web traffic and DNS load balancing for rest of the traffic. HLB supports both the traffic web and non-web while DNS load balacing supports only non-web (Non-HTTP/HTTPS) traffic. Lync/Skype4B supports two types of load balancing: Based on the traffic, you can decide the load balancing methodology. Non-web (Non-HTTP/HTTPS) traffic and Web (HTTP/HTTPS) traffic. Simply, the traffic can be divided into two part i.e. Planning and decision making is a key for client-to-server traffic which decides how the traffic will route from end-users to the servers. It is an automatic process and doesn’t need any external intervention.Ĭlient-to-server traffic: Client-to-server traffic is an important configuration part after Lync/Skype4B pool deployment. Servers read the Central Management store which are part of the published topology and obtain the FQDNs of servers in the topology to distribute the traffic among the servers. Lync/Skype4B is intelligent enough to handle traffic between servers. Server-to-server traffic: Server-to-server traffic doesn’t need any external load balancing method it uses topology-aware load balancing. Now, it is very important to understand which kind of traffic you deal with when you deploy enterprise edition pool. If you have a Standard Edition deployment then obviously you don’t need any load balancing method because each server is responsible for a specific set of users.

In layman language if you have more than one server in a group/pool which are responsible for same service, you need a method to balance the traffic among those servers. Load Balancing is a not a good to have requirement for any Enterprise Edition pool but it is a must to have requirement.