Exchange Server 2016 VII: Architecture

The new Exchange Server 2016 has been combined with 2013 of the front-end roles on a single service, and the reduced architecture has changed the 16 highly available architecture! Let's take a look at what the architecture in Exchange 2016 looks like, and see how our highly available architecture should be designed.

Most of the following are from TechNet:

https://technet.microsoft.com/zh-cn/library/jj150491 (v=exchg.160). aspx

—————————————————— Gorgeous split-line ———————————————————

is the entire completion architecture of Exchange 2016, which, in the view of the local Exchange environment, is only an Edge Transport server and a mailbox server, and the load balancer is already out of the entire exchange architecture and is already a separate load balancer device. From a new architecture, our high-availability design has to change.

650) this.width=650; "title=" IC835300 "style=" border:0px;background-image:none;padding-top:0px;padding-left:0px; padding-right:0px;width:600px;height:714px; "border=" 0 "alt=" IC835300 "src=" http://s3.51cto.com/wyfs02/M02/78/74/ Wkiol1z8_purdccoaagym0pdmv0999.png "height=" 714 "width=" "hspace=" 0 "vspace=" 0 "/>

Server communication Architecture

Communication between Exchange 2016 servers and past and future versions of Exchange occurs at the protocol layer. Cross-layer communication is not allowed. We summarize this communication architecture as "every server is an island". This architecture has the following advantages:

• Reduce inter-server communication.

• Provides version-aware communication.

• Isolate the fault.

• Integrate the design within each server.

The protocol layer communication between Exchange 2016 servers is as shown in.

650) this.width=650; "title=" IC835301 "style=" border:0px;background-image:none;padding-top:0px;padding-left:0px; padding-right:0px;width:600px;height:476px; "border=" 0 "alt=" IC835301 "src=" http://s3.51cto.com/wyfs02/M00/78/74/ Wkiol1z8_pzrwekraafmhl2obig903.png "height=" 476 "width=" "hspace=" 0 "vspace=" 0 "/>

Server Role Architecture

Exchange 2016 uses mailbox servers and Edge Transport servers. The following sections describe these server roles, respectively.

Mailbox server

• The mailbox server contains the transport service that is used to route messages. For more information, see Mail Flow and the transport pipeline

• Mailbox servers contain mailbox databases that process, render, and store data.

• The mailbox server contains client Access services that accept client connections for all protocols. These front-end services are responsible for routing or brokering connections to the appropriate backend services on the mailbox server. The client does not directly connect to the backend service. For more information, see the Client Access Protocol Architecture section later in this topic .

• A mailbox server contains a Unified Messaging (UM) service that provides voice mail and other telephony features to a mailbox.

• You can use the Exchange Admin Center (EAC) and the Exchange Management Shell to manage Mailbox servers. For more information, see Exchange Admin Center in Exchange 2013 and use PowerShell and exchange (Exchange Management Shell) in conjunction with .

Edge Transport Server

• Edge Transport server processing All external mail flow for the Exchange organization.

• Edge Transport servers are typically installed in the perimeter network, and subscribe to the internal Exchange organization. When the Exchange organization receives and sends messages, the EdgeSync synchronization process provides recipient information and other configuration information to the Edge Transport server.

• antispam Protection in Exchange

• You can use Exchange Management Shell to manage Edge Transport servers. For more information, see

For more information about Edge Transport servers, see Edge Transport Server .

High Availability Architecture

The following sections describe the high availability features in Exchange 2016, respectively.

Mailbox High Availability

Database availability groups (DAGS) are the basic elements of a highly available site resilience framework built into Exchange 2016. A DAG is a group of mailbox servers that not only host a set of databases, but also provide database-level automatic recovery capabilities for database, network, and server failures. The DAG in Exchange 2016 has been improved compared to exchange 2013.

Transport High Availability

• The transport service creates a redundant copy of all messages in the transport. This feature is known as Shadow redundancy .

• The transport service creates a redundant copy of all delivered messages. This feature is known as a secure network .

• In Exchange 2016, a DAG represents a transport high availability boundary. You can deploy dags across multiple Active Directory sites for site resiliency.

• In Exchange 2016, to achieve high availability of transport, it is not just necessary to ensure that the message is redundant, because redundancy does not depend on the features supported by the sending mail server. Therefore, you can say that Exchange 2016 tries to keep multiple copies of the message during and after message delivery to ensure message redundancy.

Client Access Protocol Architecture

The Client Access service on an Exchange 2016 mailbox server is responsible for accepting all forms of client connectivity. The Client access (front-end) service proxies these connections to the backend service on the destination mailbox server (the local server or remote mailbox server that holds the active copy of the user's mailbox). The client does not directly connect to the backend service. This communication architecture is shown in.

650) this.width=650; "title=" IC835302 "style=" border:0px;background-image:none;padding-top:0px;padding-left:0px; padding-right:0px;width:600px;height:536px; "border=" 0 "alt=" IC835302 "src=" http://s3.51cto.com/wyfs02/M01/78/76/ Wkiom1z8_oetfmgiaagbrpnugmq354.png "height=" 536 "width=" "hspace=" 0 "vspace=" 0 "/>

The protocol used by the client determines the protocol used to proxy the request to the backend service on the target mailbox server. For example, if the client is using an HTTP connection, the Mailbox server uses HTTP to proxy the request to the target mailbox server (using a self-signed certificate to secure it over SSL). If the client is using IMAP or POP, the protocol used is also IMAP or pop.

The Telephony service request differs from other client connections. The mailbox server does not proxy the request, but instead redirects the request to the mailbox server that holds the active copy of the user's mailbox. You must have a telephony device to establish a SIP and RTP session directly on the target mailbox server using the Unified Messaging service.

Exchange 2016 architecture changes

• server roles are merged in Legacy Exchange, you can install the Client Access server role and the mailbox server role on different computers. In Exchange 2016, the Client Access server role is automatically installed as part of the mailbox server role, and the Client Access server role is no longer a separate installation option. This change reflects the idea of co-locating Exchange Server roles (recommended best practices since Exchange 2010). The multi-Role Exchange server architecture provides the following tangible benefits:

  • All Exchange servers in the environment (except for all Edge Transport servers) can all be identical, with the same hardware, configuration, and so on. This uniformity simplifies the purchase of hardware and the maintenance and management of Exchange servers.

  • Resiliency has been improved because of the multi-role The Exchange server can recover from more client access roles (or services) failures and still provide services.

• The search feature improves The local search instance to now read data from the local mailbox database copy. As a result, passive search instances no longer need to collaborate with active search instances to perform index updates, and bandwidth requirements between the active copy and the passive copy have been reduced by 40% compared to the previous version of Exchange. In addition, the search function can now perform multiple asynchronous disk reads before the user completes the search term. This not only fills in the information in the cache, but also provides a second-second search query delay for online clients such as Outlook on the Web.

• Office Online Server Preview document previews for Outlook on the Web in older versions of Exchange, Outlook Web App contains a W that can be built-in to preview office and PDF documents Ebready Document viewing. In Exchange 2016, Outlook on the Web uses Office Online Server Preview to provide rich preview and editing capabilities for documents. Although this provides a document experience that is consistent with other products, such as SharePoint and Skype for business, you must still deploy Office Online Server Preview in your on-premises environment (if you have not already deployed it). For more information, see install the next version of Office Web Apps server .

• MAPI over HTTP is the default method for Outlook connections MAPI over HTTP was introduced in Exchange Service Pack 1 and was improved on the basis of the traditional Outlook Anywhere (RPC over HTTP) connection method. In Exchange 2016, MAPI over HTTP is enabled by default and provides additional controls, such as the ability for each user to enable or disable MAPI over HTTP, and whether to advertise it to external clients.

Summarize:

From the Exchange 2016 architecture, the original two roles were merged on a single server. And NLB is no longer used as a network load balancer in Exchange2016, and the rest of the network load balancer is used as a unified portal for access to Exchange 2016, so that the schema tuning can lead to the absence of the rest of the load balancer in the enterprise. Only Dags can be configured for high availability of Exchange2016.

So how do we go through Exchange 2016 to do our dag, and even if there is a way to do Network Load Balancing, the next article will explain how to achieve only through Exchange2016 Network Load Balancing and dag!

This article is from the "Li Fei _ignore" blog, be sure to keep this source http://ignore.blog.51cto.com/2247529/1728328

Exchange Server 2016 VII: Architecture