Exchange 2013
Server Architecture:
Part 1
Jeff Mealiffe
Senior Program Manager Exchange Product Group
Agenda
• Part 1
– Overview of the new Architecture
– The Client Access server role
• Part 2
– The Mailbox server role
– Transport Architecture
AD 5 major roles Tightly coupled • Functionality • Geo affinity • Versioning • User partitioning Web browser Outlook (remote user) Mobile phone Line of business application Client Access Client connectivity Web services
Outlook (local user)
Layer 7 LB
External SMTP servers
Hub Transport
Routing & policy
Forefront Online Protection for Exchange Mailbox Storage of mailbox items
Enterprise Network Phone system
(PBX or VOIP)
Unified Messaging
Voice mail and voice access
Edge Transport
Routing and AV/AS
E2007/E2010 Server Role Architecture
E2007/E2010 Server Role
What’s wrong with the existing model?
• Exchange deployments are overly complicated
• Doing Exchange load balancing “right” is hard and often requires
expensive solutions
– Requiring session affinity at the load balancer significantly impacts scalability – Many hardware load balancing solutions are expensive and thus, are a luxury
many of our customers can’t afford or don’t have the expertise to deploy
• Customers deploy based on dedicated server roles
– This means that in many cases, hardware is deployed that is unutilized (e.g., DIMM slots and disk slots, etc.) or under-utilized
Separate roles for ease of deployment and mgmt. segmentation
Support cheaper storage
2007
Simplify for scale, balanced utilization, isolation
Integrate HA for all roles Simplify network
architecture
2013
Separate HA solutions for each role
Introduced the DAG Rich management experience using RBAC Leaves resources on the ground in each role
2010
Role differentiation through manual configuration Hardware solutions for “reliability” ($$$$) Ex Ex Ex Ex SAN 2000/2003 L7 LB CAS HT MBX MBX LB
Exchange 2013 architecture theme
Use Building Blocks to facilitate deployments at all scales – from self-hosted small organizations to Office 365– Server role evolution
– Network layer improvements
– Versioning and inter-op principles
Benefits
– Hardware efficiency – Deployment simplicity
– Low friction cross-version inter-op – Failure isolation
AD Web browser Outlook (remote user) Mobile phone Line of business application Outlook (local user)
External SMTP servers Forefront Online Protection for Exchange Enterprise Network Phone system (PBX or VOIP) Edge Transport
Routing and AV/AS
2 Building Blocks Client Access Array
• Evolution of E2010 CAS Array • SMTP Front-End Database Availability Group • Evolution of E2010 DAG • Includes core server protocols Loosely coupled • Functionality • Versioning • User partitioning • Geo affinity La ye r 4L B CAS CAS CAS CAS CAS CAS Array MBX MBX MBX MBX MBX DAG
E2010 Banned Server1 (Vn) Server2 (Vn+1) Protocols, Server Agents EWS RPC CA Transport Assistants MRS MRSProxy Transport Assistants EWS RPC CA MRS MRSProxy
Business Logic XSO Mail Item
Other API CTS
XSO Mail Item Other API CTS Storage Store Content index File system ESE
Store Content index File system ESE SMTP MRS proxy protocol EWS protocol Custom WS
E2013 Architecture Hardware LB CAS, HT, UM MBX L7LB E2010 Architecture
AuthN, Proxy, Re-direct Protocols, API, Biz-logic
Assistants, Store, CI
Load Balancer AuthN, Proxy, Re-direct
CA
S2013
Store, CI
Protocols, API, Biz-logic MB
X2013
CAS For a given mailbox’s connectivity, the
protocol being used is always served by the server that hosts the active database copy Each CAS determines the right end point for the traffic, and so all sessions, regardless of where they started, end up in the same place
This means that the rendering for clients like OWA occurs on the Mailbox server, Transport transcoding is occurring on the Mailbox server etc…. User DAG1 MBX-A MBX-B MBX-B MBX-A Layer 4LB
What is the CAS2013 role?
• CAS2013 is comprised of three components:
– Client protocols (HTTP, IMAP, POP) – SMTP
– UM Call Router
• Thin, stateless (protocol session) servers organized in a load balanced
configuration
– Session affinity NOT required at the load balancer
• Provides a unified namespace and authentication for clients
• Where the logic “lives” to route a specific protocol request to the
“correct” destination end point
– Capable of supporting legacy servers with redirect or proxy logic
CAS2013
MBX2013
RPC CA
IIS
RPS OWA, EAS, EWS, ECP, OAB
POP IMAP Transport UM RpcProxy MDB MailQ HTTP Proxy IIS POP IMAP SMTP UM Telephony IMAP SMTP
OWA Outlook EAS EAC PowerShell
Load Balancer HTTP POP IMAP SMTP Redirect SIP + RTP
CAS2013 client protocol
architecture
Outlook Connectivity
RPC/HTTP and the death of RPC/TCP
• What are the benefits?
– Does not require a “RPC CAS array namespace” for the DAG
– No longer have to worry about “The Exchange administrator has made a
change that requires you to quit and restart Outlook” during mailbox
moves or *over events
– Extremely reliable and stable connectivity model – the RPC session is
always on the MBX2013 server hosting the active database copy
• What changes?
– RPC end point for Outlook client is now a GUID (and SMTP suffix)
– Support for internal and external Outlook Anywhere namespaces
Third-Party MAPI Products
• Third-party MAPI products will need to use RPC/HTTP to connect to
CAS2013
• Exchange 2013 will be the last release that supports a MAPI/CDO
download
– Third-parties must move to EWS in the future
• The MAPI/CDO download will be updated to include support for
RPC/HTTP connectivity
– Will require third-party application configuration; either by
programmatically editing a dynamic MAPI profile or setting registry keys
– Legacy environments can continue to use RPC/TCP
CAS HTTP Proxy IIS MBX CAS Load Balancer HTTP Proxy IIS DB Protocol Head
Local Proxy Request
HTTP HTTP Site B ou ndar y MBX CAS Load Balancer HTTP Proxy IIS DB Protocol Head HTTP
OWA Cross-Site Redirect Request
HTTP
MBX
DB Protocol Head HTTP
Cross-Site Proxy Request HTTP Site B ou ndar y
CAS2013 client protocol connectivity
flow
Exchange load balancing options
Generalist IT admin
Those with increased
network flexibility
Those who want to
maximize server
availability
+ Simple, fast, no affinity LB + Single, unified namespace + Minimal networking skillset - Per Server Availability
+ Per protocol availability + Single, unified namespace - SSL termination @ LB - Requires increase networking skillset + Simple, fast, no affinity LB
+ Per protocol availability - One namespace per protocol
Simplicity
Functionality
W
ho’
s
it
for?
T
rad
e
-of
fs
Sue (somewhere in NA) DNS Resolution DAG VIP #1 VIP #2 Sue (traveling in APAC) DNS Resolution via Geo-DNS
Round-Robin between # of VIPs
DAG
VIP #3 VIP #4
mail.contoso.com
Round-Robin between # of VIPs
A single common namespace example
Summary: CAS2013 Client Protocol Benefits
• Simplifies the network layer
– No longer requires session affinity at the load balancer – Just get the traffic to CAS2013 and let it handle the affinity
– CAS2013 can be “farther away” from MBX2013 and still offer good client performance (because it is a 1:1 proxy)
– Removes the need for RPC Client Access arrays
• Deployment flexibility
– CAS2013 provides more deployment flexibility; for example, consolidate to fewer sites
– Can deploy a single world-wide namespace
• Simplifies upgrade and inter-op
– Designed to proxy to multiple Mailbox server versions, up and down level – DAGs can be replaced with E2013 at any desired pace
Coming up in part 2
• Mailbox server role
• Transport architecture
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Office 365, and other product and service names are or may be registered
trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational
purposes only and represents the current view of Microsoft Corporation as of the date of this
presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR
STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.