Exchange Server 2010 Launch Deck: High Availability and Storage

1. Exchange 2010 High Availability Harold Wong IT Pro Evangelist blogs.technet.com/haroldwong

2. Agenda Exchange 2010 High Availability Fundamentals End-to-End Availability Improvements High Availability Fundamentals High Availability Design Examples Storage Improvements

5. Simplified administration

6. Incremental deployment

7. Unification of CCR + SCR

8. Easy stretching across sites

9. Up to 16 replicated copies

10. Easier & cheaper to deploy

11. Easier & cheaper to manage

13. Larger mailboxes

14. Further IO reductions

16. Better SLAs

17. Further IO reductions

19. Exchange 2010 High Availability Overview AD site: Dallas Client Access Server All clients connect via CAS servers DB1 Client DB3 Mailbox Server 6 DB5 AD site: San Jose Client Access Server Easy to stretch across sites Failover managed within Exchange Mailbox Server 1 Mailbox Server 2 Mailbox Server 3 Mailbox Server 4 Mailbox Server 5 Database Availability Group DB1 DB1 DB1 DB4 DB2 DB5 DB3 DB2 DB5 DB3 DB4 DB1 Database centric failover DB1 DB3 DB2 DB5 DB4

20. Database Availability Group (DAG) Mailbox Servers Mailbox Database Database Copy Active Manager RPC Client Access Service (Active Manager Client) High Availability Fundamentals RPC Client Access Service Active Manager Active Manager Active Manager DB1 DB1 DB1 DB2 DB2 DB2 Database Availability Group DB3 DB3 DB3

21. Exchange 2010 HA FundamentalsDatabase Availability Group (DAG) Group of up to 16 servers Wraps a Windows® Failover Cluster Defines the boundary of replication and failover/switchover Mailbox Servers …. Host the active and passive copies of multiple mailbox databases Support up to 100 databases per server

22. Mailbox Database Unit of Failover/Switchover 30 second Database Failover/Switchover Database names are unique across an forest Mailbox Database Copy A database has one active copy in a DAG A server may not host more than one copy of a given database Replication of copies using Log Shipping System tracks health of each copy Exchange 2010 HA FundamentalsMailbox Databases and Copies

23. High Availability’s Brain Manages which database copies should be active and passive Source of definitive information on where a database is active and mounted Active Directory is primary source for configuration information Active Manager is primary source for changeable state information such as active and mounted A process that runs on every server in DAG Exchange 2010 HA FundamentalsActive Manager Active Manager

24. Incremental DeploymentReduces cost and complexity of HA deployments Easy to add high availability to existing deployment High availability configuration is post-setup HA Mailbox servers can host other server roles Datacenter 1 Datacenter 2 Database Availability Group Mailbox Server 3 Mailbox Server 1 Mailbox Server 2 DB1 DB1 DB1 DB2 DB2 DB2 DB3 DB3 DB3

25. Simplified ManagementReduces cost and complexity of management HA Administration within Exchange Recovery uses the same simple operation for a wide range of failures Simplified activation of Exchange services in a standby datacenter

26. High Availability Management demo

27. Use a VSS backup solution Backup from any copy of the database/logs Always choose passive (or active) copy Backup an entire server Designate a dedicated backup server for a given database Restore from any of these backups: Database Availability Group Mailbox Server 3 Mailbox Server 1 Mailbox Server 2 DB1 DB1 DB1 VSS requestor DB2 DB2 DB2 DB3 DB3 DB3 Exchange Server 2010 Backups

28. Storage ImprovementsPerformance enhancements enable new options Exchange 2010 Storage Enhancements 70% reduction in IOPS Smoother IO patterns Resilience against corruption Choose from a wide range of storage technologies without sacrificing system availability: Storage Area Network (SAN) Direct Attached w/ SAS Disks JBOD SATA (RAID-less) Direct Attached w/ SAS Disks

29. Lowering Exchange 2010 Storage Costs Optimized for DAS storage Use larger, slower, cheaper disks Support larger mailboxes at lower cost HA provides resilience from disk failures HA Solution remains unchanged regardless of data volume size JBOD/RAID-less storage now an option Requires 3+ DB Copies

31. Simplified management

32. Simplified site resilience

33. All server roles on one server (Small deployments)3000 Mailboxes 2 Node Cluster Double Server/Disk Failure Resiliency 24,000 Mailboxes 6 Node DAG 3 copies (JBOD) 4 x 2 Node CCR 2 copies (RAID) Storage Cost savings examples

34. Automatic protection against loss of queued e-mails due to hardware failure Simplifies hub and edge transport server upgrades and maintenance Improved Transport Resiliency X Mailbox Server EdgeTransport Servers keep “shadow copies” of items until they are delivered to the next hop Edge Transport HubTransport

35. Online Move MailboxLimit user disruption during mailbox moves and maintenance Users remain online while their mailboxes are moved between servers Sending messages Receiving messages Accessing entire mailbox Administrators can perform migration and maintenance during regular hours Also can be used to migrate users from on-premise server to Exchange Online E-Mail Client Client Access Server Exchange 2010 & Exchange 2007 SP2 Online Exchange 2003 Offline Mailbox Server 1 Mailbox Server 2

36. Hardware Load Balancer Mailbox servers in a DAG can host other Exchange server roles CAS/HUB/MAILBOX 2 CAS/HUB/MAILBOX 1 DB1 DB1 2 server configurations, should always use RAID DB2 DB2 DB2 DB3 DB3 High Availability Design ExampleBranch office or smaller deployment

38. Configure IP gateway to point to more than one UM serverUnified Messaging

39. High Availability Management (Closure) demo

40. Exchange 2010 High Availability ….. Easier & cheaper to deploy Simplified administration Granular failover & recovery Better end-to-end availability One technology for both high availability and site resilience Summary

42. Exchange Forums

43. The New Efficiency Virtual Launch Experience

44. TechNet Exchange Website

46. © 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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.