Академический Документы
Профессиональный Документы
Культура Документы
Agenda
Exchange 2010 High Availability Vision/Goals Exchange 2010 High Availability Features Exchange 2010 High Availability Deep Dive Deploying Exchange 2010 High Availability Features Transitioning to Exchange 2010 High Availability High Availability Design Examples
Goals
Deliver a native solution for high availability/site resilience Enable less expensive and less complex storage Simplify administration and reduce support costs Increase end-to-end availability Support Exchange Server 2010 Online Support large mailboxes at low cost
Complex site resilience and recovery Clustered Mailbox Server had to be created manually
Dallas
DB1 DB2
Standby Cluster
DB3
San Jose
Front End Server
NodeA (active)
NodeB (passive)
Complex activation for remote server / datacenter Clustered Mailbox Server cant co-exist with other roles
Dallas
SCR
Standby Cluster
DB1 DB2
DB3
San Jose
Client Access Server
NodeA (active)
CCR
NodeB (passive)
DB2 DB3
DB5 DB1
DB4
DB2
Continuous Replication
Log shipping and replay Database seeding Store service/Replication service Database health and status monitoring Divergence Automatic database mount behavior
DAG
Active Manager
Exchange component that manages *overs
Runs on every server in the DAG Selects best available copy on failovers Is the definitive source of information on where a database is active
Stores this information in cluster database Provides this information to other Exchange components (e.g., RPC Client Access and Hub Transport)
Active Manager
Primary Active Manager (PAM)
Runs on the node that owns the cluster group Gets topology change notifications Reacts to server failures Selects the best database copy on *overs
Active Manager
Selection of Active Database Copy
Active Manager selects the best copy to become active when existing active fails
1. Ignores servers that are unreachable or activation is
temporarily or regularly blocked 2. Sorts copies by currency to minimize data loss 3. Breaks ties during sort based on Activation Preference 4. Selects from sorted listed based on copy status of each copy
Active Manager
Selection of Active Database Copy
Active Manager selects the best copy to become active when existing active fails
10 8 6 9 5 7
Catalog Copy status Crawling Healthy Healthy, DisconnectedAndHealthy, DisconnectedAndResynchronizing, or SeedingSource ReplayQueueLength CopyQueueLength < 10 50 ReplayQueueLength < 50
Mailbox Server 1
Mailbox Server 2
Mailbox Server 3
Mailbox Server 4
Mailbox Server 5
DB3
DB4 DB5
Mailbox Server 1
Mailbox Server 2
Mailbox Server 3
Mailbox Server 4
Mailbox Server 5
DB4
DB5 DB1
DAG Lifecycle
DAG is created initially as empty object in Active Directory
Continuous replication or 3rd party replication using Third Party Replication mode DAG is given a name and one or more IP addresses (or configured to use DHCP)
DAG Lifecycle
When second and subsequent Mailbox server is added to a DAG
The server is joined to cluster for the DAG The quorum model is automatically adjusted
Node Majority - DAGs with odd number of members Node and File Share Majority - DAGs with even number of members File share witness cluster resource, directory, and share are automatically created by Exchange when needed
The server is added to the DAG object in Active Directory The cluster database for the DAG is updated with info on configured databases, including if they are locally active (which they should be)
DAG Lifecycle
After servers have been added to a DAG
Configure the DAG
Network Encryption Network Compression
DAG Lifecycle
Before you can remove a server from a DAG, you must first remove all replicated databases from the server When a server is removed from a DAG:
The server is evicted from the cluster The cluster quorum is adjusted as needed The server is removed from the DAG object in Active Directory
Before you can remove a DAG, you must first remove all servers from the DAG
Add-DatabaseAvailabilityGroupServer -Identity DAG1 -MailboxServer EXMBX2 Add-DatabaseAvailabilityGroupServer -Identity DAG1 -MailboxServer EXMBX2 -DatabaseAvailablityGroupIpAddresses 10.0.0.8,10.0.1.8
Add second and subsequent Mailbox Server Add a Mailbox Database Copy Extend as needed
Add-DatabaseAvailabilityGroupServer -Identity DAG1 -MailboxServer EXMBX2 Add-MailboxDatabaseCopy -Identity MBXDB1 -MailboxServer EXMBX3
Transition Steps
Verify that you meet requirements for Exchange 2010 Deploy Exchange 2010 Use Exchange 2010 mailbox move features to migrate Unsupported Transitions
In-place upgrade to Exchange 2010 from any previous version of Exchange Using database portability between Exchange 2010 and non-Exchange 2010 databases Backup and restore of earlier versions of Exchange databases on Exchange 2010 Using continuous replication between Exchange 2010 and Exchange 2007
DB2
3 Nodes In 3 server DAG, quorum is lost 3 HA Copiesservers sustain more DAGs with more JBOD -> 3 physical Copies failures greater resiliency
Mailbox Server 3
Mailbox Server 1
Mailbox Server 2
X
Database Availability Group
Mailbox Server 1
Mailbox Server 2
Mailbox Server 3
Mailbox Server 4
X
Database Availability Group (DAG)
Separate DAGs needed when users are affiliated with a specific site
For example: DAG1 for Redmond users and DAG1 stretches to Dublin site DAG2 for Dublin users and DAG2 stretches to Redmond site
Key Takeaways
Greater end-to-end availability with Mailbox Resiliency Unified framework for high availability and site resilience Faster and easier to deploy with Incremental Deployment Reduced TCO with core ESE architecture changes and more storage options Supports large mailboxes for less money
Win!
LifeCam Show
Ultra-Thin Mobile Design World-Class High Definition Optics
Question:
What protocol is used for log shipping in Exchange 2007? What protocol is used for log shipping in Exchange 2010?
Resources
www.microsoft.com/teched
Sessions On-Demand & Community
www.microsoft.com/learning
Microsoft Certification & Training Resources
http://microsoft.com/technet
Resources for IT Professionals
http://microsoft.com/msdn
Resources for Developers
Related Content
Breakout Sessions (session codes and titles) UNC308 - Microsoft Exchange Server 2010 Architecture UNC310 - Microsoft Exchange Server 2010 Transition and Deployment UNC312 - Storage in Microsoft Exchange Server 2010 UNC311 - Unified Messaging in Microsoft Exchange Server 2010 UNC309 - Microsoft Exchange Server 2010 Management Tools UNC307 - Archiving and Retention in Microsoft Exchange Server 2010 Interactive Theater Sessions (session codes and titles)
UNC12H - Microsoft Exchange Server 2010 High Availability and Storage Scenarios
UNC13H - Microsoft Exchange Server 2010 Server Management Tools UNC14H - Microsoft Exchange Server 2010 Setup and Deployment
Whiteboard Sessions (session codes and titles) WTB304 - Designing Microsoft Exchange Server 2010 High Availability Solutions
Track Resources
Exchange Server 2010 Documentation
http://technet.microsoft.com/library/bb124558(EXCHG.140).aspx
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.