For example with the Outlook Web Access service you would use:
To ensure that load balancers do not route traffic to a Mailbox server that Managed Availability has marked as offline, load balancer health probes must be configured to check a specific URL for each service in the format: But most importantly layer 7 now has ample performance for even the largest Exchange deployments. This change was made for several reasons: Layer 7 is easy to configure, the servers can be positioned on any routeable network, no Exchange Server configuration changes are required to handle the ARP problem.
We've recently changed our recommended deployment mode from layer 4 DR -> layer 7 SNAT. If this is not feasible for any reason – for example, the Exchange Servers are located on a different subnet to the VIP - then two-arm layer 4 NAT mode is suggested as this also offers high performance. One-arm layer 4 DR mode is the fastest and most scalable option so where possible this is recommended. However, for very large deployments supporting many 1000s of mailboxes, layer 4 DR mode can be leveraged to provide maximum load balancing performance. This mode requires no changes to the Exchange Servers and enables the Exchange Servers to be located on any route-able network. Layer 7 utilizes SNAT mode.įor simplicity we recommend using layer 7 SNAT mode. At layer 4, either DR (Direct Return) or NAT mode can be used. Load balancer deployment methodĮxchange 2016 can be deployed using either layer 4 or layer 7 methods. However, you still need to think about your basic network architecture, your health checks and SSL offloading. Load balancing considerationsĬorrectly configuring Exchange 2016 as a cluster is a lot easier than the older versions of the product. Older versions of Outlook do not support MAPI over HTTPS and use RPC over HTTPS (Outlook Anywhere). Outlook 2013 SP1 and all later versions of Outlook use MAPI over HTTPS to access their mailbox. One of the main differences from Exchange 2010 is that all client connections are made using HTTPS. No client connectivity directly via MAPI is allowed. The mailbox server hosting the active copy of the mailbox will serve the user accessing it, even if the user connects to another mailbox server.įinally, all client traffic from native Exchange clients like Outlook connect over HTTP/HTTPS. The Exchange 2016 mailbox role includes the same proxied functionality that was in Exchange 2013, meaning that if two servers host different mailboxes they will proxy traffic for each other when required. In Exchange Server 2016, the Mailbox Servers form the DAG. Exchange 2016 has been consolidated into two roles: the Mailbox Server role and the Edge Transport Server role. The CAS role that used to be in Exchange 20 has now been merged into the Mailbox role.
This has greatly simplified both the deployment process and the implementation of a load balancer. It has been designed for simplicity of scale, hardware utilization, and failure isolation. Exchange 2016 is Microsoft's latest enterprise level messaging and collaboration server.
0 kommentar(er)
