AD Web browser Outlook (remote user) Mobile phone Line of business application Outlook (local user) External SMTP servers Exchange Online Protection.

Slides:



Advertisements
Similar presentations
Minimising IT costs, maximising operational efficiency minimising IT costs, maximising operational efficiency Balance.
Advertisements

5 server roles Tightly-coupled in terms of versioning functionality user partitioning geo-affinity Previous Server Role Architecture Internal Network.
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,
Daniel Kenyon-Smith UC Consultant – MCS UK. Optimize for Software + Services Deployment Flexibility Continuous Availability Simplify Administration Manage.
Exchange Server 2010 Upgrade and Deployment Meelis Nigols koolitaja IT Koolitus.
Overview of Server Roles in Exchange Server 2010 In Exchange Server 2010, servers are installed with specific functional roles: Mailbox Server role Edge.
Scott Schnoll Exchange Server 2013 Site Resilience.
Welcome to the Exchange 2013 Webcast Deployment & Coexistence.
F5 solution for Microsoft Exchange. 2 Exchange 2010 Architecture External SMTP servers Edge Transport Routing and AV/AS Phone system (PBX or VoIP) Client.
F5 Solution for Microsoft Exchange 2010 James Hendergart Business Development Manager Helen Johnson Solution Engineer.
EXL305. Section 1 What’s the Same / What’s New / What’s Different in Exchange 2010 (background on where things will trip you up during the transition.
Part 2 Transport Unified Messaging Managed Availability.
Pre-Release Programs Be first in line! Exchange & SharePoint On-Premises Programs Customers get: Early access to new features Opportunity to shape features.
Jaap Wesselius May 27, 2009 Exchange Server 2010 what’s new?

Exchange 2007 Overview. What Will We Cover? New features in Microsoft® Exchange 2007 The Exchange Management Console The Exchange Management Shell New.
Implementing High Availability
EXC11: Migrating to Exchange 2010 from Exchange 2003 Jim McBee Ithicos Solutions LLC
Copyright© Microsoft Corporation DAG Architecture.
Exchange 2010 Project Presentation/Discussion August 12, 2015 Project Team: Mark Dougherty – Design John Ditto – Project Manager Joel Eussen – Project.
Overview of Exchange 2013 Architecture Transport components shipping with Exchange 2013 Mail Routing Scenarios Transport High Availability SMTP Client.
Exchange Storage for Insiders
Andrew Sullivan Program Manager, Outlook Microsoft Corporation SESSION CODE: OSP314.
CAS Array DAG MBX-A MBX-B DB1 Load Balancer.
TechEd /20/2017 2:02 AM © 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks.
Managing Client Access
Module 4 Managing Client Access. Module Overview Configuring the Client Access Server Role Configuring Client Access Services for Outlook Clients Configuring.
Microsoft Exchange Server 2007 אייל רגב מנהל תחום מיקרוסופט בחברת אומניטק.
Eesti. Baltimaad. Põhja Euroopa. Priit Timpson Atea teenuste osakond.
EXL311: Exchange Server 2013 Architecture Deep Dive Scott Schnoll Microsoft Corporation EXL311.
Chris Goosen Infrastructure Consultant Kloud Solutions.
CAS Exchange 2013 architecture For a given mailbox’s connectivity, the protocol being used is always served by the server that hosts the active database.
MCSE Guide to Microsoft Exchange Server 2003 Administration Chapter Four Configuring Outlook and Outlook Web Access.
User CAS DAG For any given mailbox’s connectivity, the user is always served by the server that hosts the active database copy Each CAS determines.
New | Remove-SearchDocumentFormat New | Remove | Set | Get- IntraOrganizationConnector Get-IntraOrganizationConfiguration.
INSTALLING MICROSOFT EXCHANGE SERVER 2003 CLUSTERS AND FRONT-END AND BACK ‑ END SERVERS Chapter 4.
Sofia, Bulgaria | 9-10 October SQL Server 2005 High Availability for developers Vladimir Tchalkov Crossroad Ltd. Vladimir Tchalkov Crossroad Ltd.
CH2 System models.
Ross Smith IV Senior Program Manager, Exchange Server Microsoft Corporation SESSION CODE: UNC202 Kyryl Perederiy Senior Systems Engineer, Business Online.
Exchange Exchange Server Role Architecture in Exchange Server 2013 Server roles in Exchange Server 2013: Client Access Server Mailbox Server Client.
Click to edit Master title style TechNet goes virtual ©2009 Microsoft Corporation. All Rights Reserved. TechNet goes virtual Upgrading and Coexisting with.
Scott Schnoll m Microsoft Corporation.
Exchange Server versionForest "rangeUpper" attribute of ms-Exch-Schema-Version-Pt Exchange 2000 Server RTM4397 Exchange 2000 Server SP34406.
Module 4 Planning and Deploying Client Access Services in Microsoft® Exchange Server 2010 Presentation: 120 minutes Lab: 90 minutes After completing.
Transport components shipping with Exchange 2013 Overview of Exchange 2013 Architecture Architectural improvements made in Transport History, Challenges,
Module 11: Implementing ISA Server 2004 Enterprise Edition.
Module 3 Planning and Deploying Mailbox Services.
Module 6: Managing Client Access. Overview Implementing Client Access Servers Implementing Client Access Features Implementing Outlook Web Access Introduction.
Exchange Server 2013 Architecture
AD Web browser Outlook (remote user) Mobile phone Line of business application Outlook (local user) External SMTP servers Exchange Online Protection.
Read/understand sizing, scalability, capacity guidance Documentation on technet, Exchange team blog, etc. Collect data on existing deployment.
UNC301 - (Microsoft IT) Microsoft Exchange 2007 Architecture and Design at Microsoft Martin Coetzer Technical Consultant Microsoft.
Exchange Server 2007 Deployment and Migration Strategies Nireshen Beerbul
Scott Schnoll m Microsoft Corporation.
Exchange Server versionForest "rangeUpper" attribute of ms-Exch-Schema-Version-Pt Exchange 2000 Server RTM4397 Exchange 2000 Server SP34406 Exchange.
Enhancing Scalability and Availability of the Microsoft Application Platform Damir Bersinic Ruth Morton IT Pro Advisor Microsoft Canada
ProductExchange 2013 SP1Exchange 2013 RTMExchange 2010 SP3Exchange 2007 SP3 Outlook 2013 SP1 or later MAPI over HTTP Outlook Anywhere Outlook Anywhere.
MCSE Guide to Microsoft Exchange Server 2003 Administration Chapter One Introduction to Exchange Server 2003.
Information explosion 1.4X 44X Internet AD Web browser Outlook (remote user) Mobile phone Line of business application Outlook (local user) External.
Microsoft Exchange Server 2013 Security Mick Tomlinson– Technical Instructor New Horizons.
VIRTUAL SERVERS Chapter 7. 2 OVERVIEW Exchange Server 2003 virtual servers Virtual servers in a clustering environment Creating additional virtual servers.
Redmond Protocols Plugfest 2016 Andrew Davidoff Exchange 2016 Protocol Overview Senior Software Engineer.
Deployment on your terms Hybrid Exchange deployment on your terms On-premises.
Microsoft ® Exchange Server 2010 Mailbox Resiliency Name Title Microsoft Corporation.
Autodiscover is Hero of Exchange Motherland!
Maximum Availability Architecture Enterprise Technology Centre.
The EPIC Exchange Preferred Architecture Debate
CompTIA Server+ Certification (Exam SK0-004)
TechEd /17/ :40 PM © 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered.
Enterprise Topography
Presentation transcript:

AD Web browser Outlook (remote user) Mobile phone Line of business application Outlook (local user) External SMTP servers Exchange Online Protection 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 Layer 4LB CAS CAS Array MBX DAG

E2010Banned Server1 (V n )Server2 (V n+1 ) Protocols, Server Agents EWS RPC CA Transport Assistants MRS MRSProxy Transport Assistants EWS RPC CA MRS MRSProxy Business Logic XSO Mail Item Other APICTS XSO Mail Item Other APICTS Storage Store Content index File systemESE Store Content index File systemESE SMTP MRS proxy protocol EWS protocol Custom WS

CAS For a given mailbox’s connectivity, the protocol being used is always served by the protocol instance that is local to 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

MBX1 MBX2 MBX16

DB IOPS/Mailbox Exchange 2003Exchange 2007Exchange 2010Exchange % reduction!

8KB Page Size STM Removed Store Quarantin e 10GB Mailboxes Elimination of Partial B+ Merges Cache Warming on Passive Log Roll 32KB Page Size Message properties stored as blobs Per-Database Process Fast Failover TBA Store Maintenance Lost Write Detection Cache Maintained after Recovery 100GB Mailboxes Database Compressio n 1 Million Items / Folder Managed Store Lost Log Resilience Page Dependency Removal Online Page Zeroing Per- Mailbox Tables 100MB Checkpoint Depth on Passive Copies Lagged Copy Enhancements OS Upgrade Support 128MB Extent Size Optimized for 7.2K RPM Disks 100 Databases / Server Hung IO and Bluescreen Support Gap Coalescing Smooth IO Writes Incremental Resync Improved Async Read Capability Support for 2 31 log generations 1GB Mailboxes 64-bit architecture Standby Continuous Replication 20,000 Items / Folder Log checksum recovery from single- bit errors 50 Databases / server Database Cache Compression Improved IO Coalescing Continuous Replication Parallel Mounting Database Space Allocation Hints Multiple Databases / JBOD Disk Lazy View Update Changes Lazy Indexes Online Database Checksum 1MB Log Files 100MB Checkpoint Depth on Active Copies Version Store Improvements 1:1 Read:Write Ratio Physical Contiguity Store Schema Changes Tuned Maintenance Writes Single Page Restore 100,000 Items / Folder JBOD Support Database Cache Priority B+ Tree Defrag BDM for Active and Passives Pre-read Keys 2010 No more deferred content conversion 2007 AutoReseed 2013

External SMTP servers EOP Edge Transport Servers Mailbox Servers AD EdgeSync TCP Mail flow Client Access Servers

MDB Transport MBX Transport Front-End Transport 2 Recipients DAG CAS MBX MDB Transport MBX Transport Front-End Transport CAS MBX

—OWA send —OWA failure —OWA failure detected —OWA recycle AppPool —OWA recycle complete —OWA verified as healthy —OWA send —OWA failure —OWA failure detected —OWA recycle AppPool —OWA recycle AppPool failed —Failover server’s databases —OWA service restarts —OWA verified as healthy —Server becomes “good” failover target (again) LB CAS-1 CAS-2 DAG MBX-1 DB1 DB2 MBX-2 OWA DB1 DB2 MBX-3 OWA DB1 DB2 OWA DB1

CAS2013 MBX2013 RPC CA IIS RPSOWA, EAS, EWS, ECP, OAB POP IMAP TransportUM RpcProxy MDB MailQ HTTP Proxy IIS POP IMAP SMTPUM TelephonyIMAPSMTPOWAEASEACOutlookPowerShell Load Balancer HTTP POP IMAP SMTP Redirec t SIP + RTP

CAS2013 MBX2013 RPC CA IIS HTTP Proxy IIS LB HTTP MDB HTTPS RPC_DATA_IN HTTPS RPC_DATA_OUT HTTPS RPC_DATA_IN HTTPS RPC_DATA_OUT HTTPS RPC_DATA_IN HTTPS RPC_DATA_OUT RpcProxy HTTP RPC MAPI Outlook

CAS2013 MBX2013 HTTP Proxy IIS LB HTTP MDB HTTPS Req/Response HTTPS Req/Response HTTPS Req/Response HTTPS Hanging Notification HTTP MAPI Outlook IIS MAPI HTTP Handler

MBX2013 CAS2013 Load Balancer HTTP Proxy IIS DB Protocol Head HTTP MBX2007 CAS2007 Load Balancer IIS DB Middle Tier Layer OWA Legacy Redirect Request MBX2007 DB Cross-Site OWA Proxy Request CAS2007 IIS Middle Tier Layer Outlook Anywhere Proxy Request ActiveSync Proxy Request Site Boundary

MBX2013 CAS2013 Load Balancer HTTP Proxy IIS DB Protocol Head HTTP Legacy Proxy Request MBX2010 DB Cross-Site Legacy Proxy Request CAS2010 IIS Middle Tier Layer Load Balancer Cross-Site OWA Redirect Request Site Boundary MBX2010 CAS2010 Load Balancer DB Middle Tier Layer IIS

MBX CAS Load Balancer HTTP Proxy IIS DB Protocol Head Local Proxy Request HTTP Site Boundary 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 Boundary CAS HTTP Proxy IIS

Sue (somewhere in NA) DNS Resolution DAG1 mail VIPmail2 VIP mail.contoso.com mail2.contoso.com DAG2 Jane (somewhere in NA) DNS Resolution Passive Active Passive

Round-Robin between # of VIPs Sue (somewhere in NA) DNS Resolution DAG VIP #1VIP #2 mail.contoso.com

CAS OWA ECP EWS EAS OAB MAPI RPC Auto D autodiscover.contoso.co m User Layer 4LB mail.contoso.com health check

CAS OWA ECP EWS EAS OAB MAPI RPC Auto D autodiscover.contoso.co m User Layer 7LB mail.contoso.com health check

mapi.contoso.com User Layer 4LB mail.contoso.com ecp.contoso.com ews.contoso.com eas.contoso.com oab.contoso.com oa.contoso.com CAS OWA ECP EWS EAS OAB MAPI RPC Auto D autodiscover.contoso.co m

Generalist IT adminThose 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 LB - Requires increase networking skillset + Simple, fast, no affinity LB + Per protocol availability - One namespace per app protocol - One VIP per protocol SimplicityFunctionality Who’s it for? Trade-Offs

mail VIP

Each datacenter should be its own Active Directory site Deploy unbound DAG model spanning each DAG across two datacenters Distribute active copies across all servers in the DAG Deploy 4 copies, 2 copies in each datacenter One copy will be a lagged copy (7 days) with automatic play down enabled Native Data Protection is utilized Single network for replication and client traffic Utilize a third datacenter for Witness server placement, if possible Increase DAG size density before creating new DAGs DAG mail VIP

DAG mail VIP

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

Selina (somewhere in NA) DNS Resolution DAG na VIP Batman (somewhere in Europe) DNS Resolution DAG eur VIP na.contoso.com eur.contoso.com