5 server roles Tightly-coupled in terms of versioning functionality user partitioning geo-affinity Previous Server Role Architecture Internal Network Phone system (PBX or VOIP) Web browser Outlook (remote user) Mobile phone Line of business application Mailbox Stores mailbox and public folder items Unified Messaging Voice mail and voice access Client Access Client connectivity Web services Outlook (local user) Layer 7 LB AD External SMTP servers Edge Transport Routing and AV/AS Hub Transport Routing and policy Forefront Online Protection for Exchange

Enterprise networkInternet Layer 4 load balancer CAS PBXLocal clientsRemote clients & devices Edge MBX

AuthN, Proxy, Re-direct Protocols, API, Biz-logic Assistants, Store, CI Exchange 2010 AuthN, Proxy, Re- direct Store, CI Protocols, Assistants, API, Biz-logic Exchange 2013 Client Access Mailbox Client Access Hub Transport, Unified Messaging Mailbox Hardware Load Balancer L4 LB L7 LB

Load Balancer MDB HTTP Proxy IIS Client Access RPC CA Mailbox IIS RPS OWA, EAS, EWS, ECP, OAB POP, IMAP SMTPUM POP IMAP Transpo rt UM SMTP POP, IMAP HTTP MailQ RpcProxy SMTP SI P Redirect SIP + RTP POP/IMAP Outlook Web AppOutlookEASEACPowerShell

A Single Common Namespace Example Geographical DNS Solution Sue (somewhere in NA) DNS Resolution DAG VIP #1VIP #2 Sue (traveling in APAC) DNS Resolution via Geo-DNS Round-Robin between # of VIPs DAG VIP #3VIP #4 mail.contoso.com Round-Robin between # of VIPs

Layer 4 LB CAS IIS HTTP Proxy MBX Protocol Head DB Layer 4 LB CAS IIS HTTP Proxy MBX Protocol Head DB Site Boundary HTTP Local Proxy RequestOWA Cross-Site Redirect Request MBX Protocol Head DB Site Boundary Cross-Site Proxy Request HTTP 13

Layer 4 LB CAS 2013 IIS HTTP Proxy MBX 2013 Protocol Head DB Exchange 2010 CAS Protocol Head MBX Store DB Site Boundary E2010 CAS Protocol Head MBX Store DB RPC Cross-Site Proxy Request Layer 7 LB OWA Cross-Site Redirect Request HTTP 14

MBX1 MBX2 MBX16

48-76% IOPS reduction (disk IOPS capacity not expected to change) 18-41% Average RPC Latency reduction 17-34% increase in CPU per RPC processed (offset by additional CPU cores) ~4X increase in store memory overhead (~4GB vs. ~1GB not including ESE cache) 24

~99.5% Reduction!

1 Day15011 MB 1 Month MB 1 Year GB 2 Years GB 4 Years GB

MBX 2013 MBX 2013 CAS2013 MBX 2013 MBX 2013 MBX 2013 MBX 2013 Public logon Private logon Public logon Content Mailbox Hierarchy Mailbox

Core Catalog CTS Incoming Documents Filter Word Break Content XForm MARS Writer Incoming Queries CTS Flow IMS Content XForm QueryParse IMS Flow Results

Mailbox DBDB Id x Passive Transport CTS Mailbox Store DBDB Index Node Id x ExSearch Local Delivery Reliable Event CTS Read Content Log

36

DAG MBX MBX Transport Transport DB2 DB1 MBX MBX Transport Transport CAS 2013 or MBX 2013 DB2 DB1 MAPI SMTP 37

39

DB2 Layer 4 LB CAS-1 MBX-1 DB2 OWA MBX-2 DB1 DB2 OWA MBX-3 DB1 CAS-2 OWA MA: Failover database OWA restart complete OWA send OWA failure detected OWA failure OWA restart service OWA verified as healthy OWA restart service failed OWA send OWA failure detected OWA failure OWA restart service OWA verified as healthy OWA service restarts time Managed availability + retries … Stuff breaks and the experience does not DB1 DAG 40

41

42

43

44

45

CAS2013 or MBX Maintain a copy of the message in the queue database but dont acknowledge the DATA verb 2.Generate a shadow copy on another MBX 2013 server in the DAG (remote site preferred) 3.Wait for acknowledgement from the shadow server 4.Send acknowledgement to SMTP client 5.Delete message from queue after SafetyNet threshold has expired MBX2 Transport MBX Transport Mail.que Store DB1 DB2 MBX3 Transport MBX Transport Mail.que Store DB1 DB2 MBX4 Transport MBX Transport Mail.que Store DB1 DB2 MBX5 Transport MBX Transport Mail.que Store DB3 DB4 MBX6 Transport MBX Transport Mail.que Store DB3 DB4 MBX7 Transport MBX Transport Mail.que Store DB3 DB4 MBX8 Transport MBX Transport Mail.que Store DB3 DB4 MBX1 Transport MBX Transport Store DB1 DB2 Mail.que SMTP R1, R2, R3 R2R1R3 Site Boundary 250 OK R3 R1, R2, R3 250 OK 250 OK Recipient State R1 – Active R2 – Active R3 – Active Recipient State R1 – Active R2 – Active R3 – Active Recipient State R1 – WaitingMDBRepl R2 – Active R3 – Active Recipient State R1 – WaitingMDBRepl R2 – Active R3 – Active Recipient State R1 – WaitingMDBRepl R2 – WaitingMDBRepl R3 – Active Recipient State R1 – WaitingMDBRepl R2 – WaitingMDBRepl R3 – Active Recipient State R1 – WaitingMDBRepl R2 – WaitingMDBRepl R3 – Processed Recipient State R1 – WaitingMDBRepl R2 – WaitingMDBRepl R3 – Processed Recipient State R3 – Active Recipient State R3 – Active Recipient State R3 – WaitingMDBRepl Recipient State R3 – WaitingMDBRepl Recipient State R3 – Processed Recipient State R3 – Processed Recipient State R1 – Processed R2 – WaitingMDBRepl R3 – Processed Recipient State R1 – Processed R2 – WaitingMDBRepl R3 – Processed Recipient State R1 – Processed R2 – Processed R3 – Processed Recipient State R1 – Processed R2 – Processed R3 – Processed Log 46

© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product 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.