Looking for more information on load balancing Exchange 2010?
Microsoft Exchange protocols and client access services have different load balancing requirements. Some Microsoft Exchange protocols and client access services require client to Client Access server affinity. Others will work without it but will display performance improvements from such affinity. Other Exchange protocols don’t require client to Client Access server affinity and performance doesn’t decrease without affinity.
- Exchange protocols that require client to CAS affinity
- Exchange protocols that benefit from client to CAS affinity
- Exchange protocols that don’t require affinity
- Understating IP ports
Load balancing is a way to manage which of your servers receive traffic. Load balancing provides failover redundancy to ensure your users continue to receive Exchange service in case of computer failure. It also enables your deployment to handle more traffic than one server can process while offering a single host name for your clients.
- Overview of Load Balancing
- Understanding Exchange 2010 Traffic loads
- Understanding Load Balancing Options
- Load Balancing Recommendations
- Affinity Options