Post by David on Jul 23, 2012 19:52:41 GMT 5.5
Exchange Server 2013 Server Roles
Exchange Server 2013 has only two server roles:
¡öClient Access server
¡öMailbox server
The two roles can co-exist on the same host, or be installed separately. At least one of each server role is required in any Active Directory site where Exchange 2013 is running
Exchange Server 2013 Client Access Server
As the name suggests, the Client Access server role is the server that clients (eg Outlook, Outlook Web App, ActiveSync) connect to for mailbox access. The Client Access server authenticates, and redirects or proxies those requests to the appropriate Mailbox server.
Client Access servers can be made highly available through the use of a load balancer.
There are two main components:
¡öClient Access service ¨C this handles the client connections to mailboxes
¡öFront End Transport service ¨C this performs various email traffic filtering functions, as well as email routing between the Exchange servers and the outside world
Exchange Server 2013 Mailbox Server
Mailbox servers host the databases that contain mailbox and public folder data. As with Exchange 2010 the Exchange 2013 Mailbox server role can be made highly available by configuring a Database Availability Group.
The Mailbox server also runs two Transport services:
¡öHub Transport service ¨C similar to the Exchange 2007/2010 Hub Transport server role, this service provides email routing within the organization, and connectivity between the Front End transport service and the Mailbox Transport service
¡öMailbox Transport service ¨C this service passes email messages between the Hub Transport service and the mailbox database
Other Server Roles from Exchange 2007/2010
With the reduction in server roles to just two in Exchange Server 2013 you may be wondering what has happened to the remaining server roles that existed in Exchange Server 2007 and 2010:
¡öHub Transport server ¨C this functionality has been divided between the Client Access server (Front End Transport service) and Mailbox server (Hub Transport and Mailbox Transport services) and is no longer a dedicated server role
¡öUnified Messaging ¨C this functionality has been divided between the Client Access and Mailbox server and is no longer a dedicated server role
¡öEdge Transport ¨C Exchange 2013 Preview does not contain an Edge Transport server role, however it will function with an Exchange 2007 or 2010 Edge Transport. There have been hints that the Edge Transport server role will not be in future versions of Exchange server
The following sections provide a summary of each server role.
Client Access servers
--------------------------------------------------------------------------------
Client Access servers accept connections from clients and proxy those requests to the back-end Mailbox server that houses the active mailbox database copy. Multiple Client Access servers can be grouped together into a load-balanced array. The Client Access server performs authentication, redirection, and proxy services; it doesn¡¯t perform any data rendering. Connections to the Client Access server are stateless which means that there is no need to maintain affinity between a client and an individual Client Access server for subsequent connections because all data processing and transformation occurs on the Mailbox server. Because of this change in architecture, Exchange 2013 Preview requires layer 4 load balancing. Layer 4 load balancing is protocol-unaware and balances traffic based on IP address and TCP/UDP port.
A Client Access array includes two different components: the Client Access service and the Front End Transport service.
The Client Access service performs the following functions:
Provides a unified namespace, authentication, and network security.
Handles all client requests for Exchange.
Routes requests to the correct Mailbox server.
Proxies or redirects client requests for legacy servers, such as Exchange 2007 and Exchange 2010 Client Access.
Enables the use of layer 4 (TCP affinity) routing.
The Front End Transport service performs the following functions:
Protocol level filtering Performs connection, recipient, sender, and protocol filtering
Network protection Centralized, load-balanced egress and ingress point for the organization.
Mailbox locator Avoids unnecessary hops by determining the best Mailbox server to deliver the message to.
Load-balances client and application SMTP requests.
Mailbox servers
--------------------------------------------------------------------------------
Mailbox servers house the mailbox data for the organization and perform data rendering and other operations. Mailbox servers can be grouped into back-end clusters which consist of database availability groups (DAG). Mailbox servers perform the following functions:
Host mailbox databases.
Provide email storage.
Host public folder databases.
Calculate email address policies.
Conduct multi-mailbox searches.
Provide high availability and site resiliency.
Provide messaging records management and retention policies.
Handle connectivity because clients don't connect directly to the Mailbox servers.
Provide all core Exchange functionality for a given mailbox where that mailbox¡¯s database is currently activated.
Fails over mailbox access when a database fails over.
New Mailbox features
--------------------------------------------------------------------------------
The following briefly describes some new and some improved features in the Mailbox role for Exchange 2013 Preview:
Evolution of Exchange 2010 DAG:
Transaction log code has been refactored for fast failover with deep checkpoint on passive database copies.
To support enhanced site resiliency, servers can be in different locations.
Exchange 2013 Preview now hosts some Client Access components, the Transport components, and the Unified Messaging components.
Exchange 2013 Preview Store has been re-written in managed code to improve performance in additional IO reduction and reliability.
Each Exchange 2013 Preview database now runs under its own process.
Smart Search has replaced the Exchange 2010 multi-mailbox search infrastructure.
Exchange Server 2013 has only two server roles:
¡öClient Access server
¡öMailbox server
The two roles can co-exist on the same host, or be installed separately. At least one of each server role is required in any Active Directory site where Exchange 2013 is running
Exchange Server 2013 Client Access Server
As the name suggests, the Client Access server role is the server that clients (eg Outlook, Outlook Web App, ActiveSync) connect to for mailbox access. The Client Access server authenticates, and redirects or proxies those requests to the appropriate Mailbox server.
Client Access servers can be made highly available through the use of a load balancer.
There are two main components:
¡öClient Access service ¨C this handles the client connections to mailboxes
¡öFront End Transport service ¨C this performs various email traffic filtering functions, as well as email routing between the Exchange servers and the outside world
Exchange Server 2013 Mailbox Server
Mailbox servers host the databases that contain mailbox and public folder data. As with Exchange 2010 the Exchange 2013 Mailbox server role can be made highly available by configuring a Database Availability Group.
The Mailbox server also runs two Transport services:
¡öHub Transport service ¨C similar to the Exchange 2007/2010 Hub Transport server role, this service provides email routing within the organization, and connectivity between the Front End transport service and the Mailbox Transport service
¡öMailbox Transport service ¨C this service passes email messages between the Hub Transport service and the mailbox database
Other Server Roles from Exchange 2007/2010
With the reduction in server roles to just two in Exchange Server 2013 you may be wondering what has happened to the remaining server roles that existed in Exchange Server 2007 and 2010:
¡öHub Transport server ¨C this functionality has been divided between the Client Access server (Front End Transport service) and Mailbox server (Hub Transport and Mailbox Transport services) and is no longer a dedicated server role
¡öUnified Messaging ¨C this functionality has been divided between the Client Access and Mailbox server and is no longer a dedicated server role
¡öEdge Transport ¨C Exchange 2013 Preview does not contain an Edge Transport server role, however it will function with an Exchange 2007 or 2010 Edge Transport. There have been hints that the Edge Transport server role will not be in future versions of Exchange server
The following sections provide a summary of each server role.
Client Access servers
--------------------------------------------------------------------------------
Client Access servers accept connections from clients and proxy those requests to the back-end Mailbox server that houses the active mailbox database copy. Multiple Client Access servers can be grouped together into a load-balanced array. The Client Access server performs authentication, redirection, and proxy services; it doesn¡¯t perform any data rendering. Connections to the Client Access server are stateless which means that there is no need to maintain affinity between a client and an individual Client Access server for subsequent connections because all data processing and transformation occurs on the Mailbox server. Because of this change in architecture, Exchange 2013 Preview requires layer 4 load balancing. Layer 4 load balancing is protocol-unaware and balances traffic based on IP address and TCP/UDP port.
A Client Access array includes two different components: the Client Access service and the Front End Transport service.
The Client Access service performs the following functions:
Provides a unified namespace, authentication, and network security.
Handles all client requests for Exchange.
Routes requests to the correct Mailbox server.
Proxies or redirects client requests for legacy servers, such as Exchange 2007 and Exchange 2010 Client Access.
Enables the use of layer 4 (TCP affinity) routing.
The Front End Transport service performs the following functions:
Protocol level filtering Performs connection, recipient, sender, and protocol filtering
Network protection Centralized, load-balanced egress and ingress point for the organization.
Mailbox locator Avoids unnecessary hops by determining the best Mailbox server to deliver the message to.
Load-balances client and application SMTP requests.
Mailbox servers
--------------------------------------------------------------------------------
Mailbox servers house the mailbox data for the organization and perform data rendering and other operations. Mailbox servers can be grouped into back-end clusters which consist of database availability groups (DAG). Mailbox servers perform the following functions:
Host mailbox databases.
Provide email storage.
Host public folder databases.
Calculate email address policies.
Conduct multi-mailbox searches.
Provide high availability and site resiliency.
Provide messaging records management and retention policies.
Handle connectivity because clients don't connect directly to the Mailbox servers.
Provide all core Exchange functionality for a given mailbox where that mailbox¡¯s database is currently activated.
Fails over mailbox access when a database fails over.
New Mailbox features
--------------------------------------------------------------------------------
The following briefly describes some new and some improved features in the Mailbox role for Exchange 2013 Preview:
Evolution of Exchange 2010 DAG:
Transaction log code has been refactored for fast failover with deep checkpoint on passive database copies.
To support enhanced site resiliency, servers can be in different locations.
Exchange 2013 Preview now hosts some Client Access components, the Transport components, and the Unified Messaging components.
Exchange 2013 Preview Store has been re-written in managed code to improve performance in additional IO reduction and reliability.
Each Exchange 2013 Preview database now runs under its own process.
Smart Search has replaced the Exchange 2010 multi-mailbox search infrastructure.