《unc302highavailabilityinexchangeserver》由会员分享，可在线阅读，更多相关《unc302highavailabilityinexchangeserver（42页珍藏版）》请在金锄头文库上搜索。
1、UNC302_High Availability in Exchange Server 2010High Availability in Exchange Server 2010UNC302AgendaExchange 2010 High Availability Vision/GoalsExchange 2010 High Availability FeaturesExchange 2010 High Availability Deep DiveDeploying Exchange 2010 High Availability FeaturesTransitioning to Exchang
2、e 2010 High AvailabilityHigh Availability Design ExamplesExchange 2010 High Availability Vision/GoalsExchange 2010 High Availability Vision and GoalsVision: Deliver a fast, easy-to-deploy and operate, economical solution that can provide messaging service continuity for all customersGoalsDeliver a n
3、ative solution for high availability/site resilienceEnable less expensive and less complex storageSimplify administration and reduce support costsIncrease end-to-end availabilitySupport Exchange Server 2010 OnlineSupport large mailboxes at low costDB1Front End ServerNodeBNodeB(passive)(passive)Outlo
4、okOWA, ActiveSync, or Outlook AnywhereSan JoseDallas Standby ClusterThird-party data Third-party data replication needed replication needed for site resiliencefor site resilienceComplex site Complex site resilience and resilience and recoveryrecoveryClustering Clustering knowledge requiredknowledge
5、requiredDB2DB3DB4DB5DB6Failover at Mailbox Failover at Mailbox server levelserver levelDB1DB2DB3Clustered Mailbox Clustered Mailbox Server had to be Server had to be created manuallycreated manuallyExchange Server 2003NodeANodeA(active)(active)DB1Client Access ServerNodeBNodeB(passive)(passive)SCRSC
6、ROutlookOWA, ActiveSync, or Outlook AnywhereSan JoseDallas Standby ClusterNo GUI to No GUI to manage SCRmanage SCRComplex activation Complex activation for remote server / for remote server / datacenterdatacenterClustering Clustering knowledge requiredknowledge requiredDB2DB3DB4DB5DB6DB1DB2DB3DB4DB5
7、DB6Failover at Mailbox Failover at Mailbox server levelserver levelDB1DB2DB3Clustered Mailbox Clustered Mailbox Server cant co-exist Server cant co-exist with other roleswith other rolesExchange Server 2007NodeANodeA(active)(active)CCRCCRDB2DB3DB2DB3DB4DB4DB5Client Access ServerMailbox Server 1Mailb
8、ox Server 2Mailbox Server 3Mailbox Server 6Mailbox Server 4Dallas San JoseMailbox Server 5DB5DB2DB3DB4DB5DB1DB1DB1DB1Failover managed by/with ExchangeDatabase level failoverEasy to extend across sitesAll clients connect via CAS serversDB3DB5DB1ClientClientExchange Server 2010Exchange 2010 High Avail
9、ability FeaturesExchange 2010 High Availability TerminologyHigh Availability Solution must provide data availability, service availability, and automatic recovery from failuresDisaster Recovery Process used to manually recover from a failureSite Resilience Disaster recovery solution used for recover
10、y from site failure*over Short for switchover/failover; a switchover is a manual activation of one or more databases; a failover is an automatic activation of one or more databases after a failureExchange 2010 High Availability Feature NamesMailbox Resiliency Name of Unified High Availability and Si
11、te Resilience SolutionDatabase Mobility The ability of a single mailbox database to be replicated to and mounted on other mailbox serversIncremental Deployment The ability to deploy high availability /site resilience after Exchange is installedExchange Third Party Replication API An Exchange-provide
12、d API that enables use of third-party replication for a DAG in lieu of continuous replicationExchange 2010 High Availability Feature NamesDatabase Availability Group A group of up to 16 Mailbox servers that host a set of replicated databasesMailbox Database Copy A mailbox database (.edb file and log
13、s) that is either active or passiveRPC Client Access service A Client Access server feature that provides a MAPI endpoint for Outlook clientsShadow Redundancy A transport feature that provides redundancy for messages for the entire time they are in transitExchange 2010 *oversWithin a datacenterDatab
14、ase or server *oversDatacenter level: switchoverBetween datacentersDatabase or server *oversAssumptions:Each datacenter is a separate Active Directory siteEach datacenter has live, active messaging servicesStandby datacenter must be active to support single database *overExchange 2007 Concepts Broug
15、ht ForwardExtensible Storage Engine (ESE)Databases and log filesContinuous ReplicationLog shipping and replayDatabase seedingStore service/Replication serviceDatabase health and status monitoringDivergenceAutomatic database mount behaviorConcepts of quorum and witnessConcepts of *oversExchange 2010
16、Cut ConceptsStorage GroupsDatabases identified by the server on which they liveServer names as part of database namesClustered Mailbox ServersPre-installing a Windows Failover ClusterRunning Setup in Clustered ModeMoving a CMS network identity between serversShared StorageTwo HA Copy LimitsPrivate a
17、nd Public NetworksExchange 2010 High Availability Deep DiveExchange 2010 HA FundamentalsDatabase Availability GroupServerDatabaseDatabase CopyActive ManagerRPC Client AccessDAGDAGcopycopycopycopyAMAMSVRSVRcopycopycopycopyAMAMSVRSVRDBDBDBDBRPC CASRPC CASRPC CASRPC CASDatabase Availability GroupBase c
18、omponent of high availability and site resilienceA group of up to 16 servers that host a set of replicated databases“Wraps” a Windows Failover ClusterManages membership (DAG member = node)Provides heartbeat of DAG member serversActive Manager stores data in cluster databaseDefines a boundary for:Mai
19、lbox database replicationDatabase and server *oversActive ManagerActive ManagerExchange component that manages *oversRuns on every server in the DAGSelects best available copy on failoversIs the definitive source of information on where a database is activeStores this information in cluster database
20、Provides this information to other Exchange components (e.g., RPC Client Access and Hub Transport)Two Active Manager roles: PAM and SAMActive Manager client runs on CAS and HubActive ManagerPrimary Active Manager (PAM)Runs on the node that owns the cluster groupGets topology change notificationsReac
21、ts to server failuresSelects the best database copy on *oversStandby Active Manager (SAM)Runs on every other node in the DAGResponds to queries about which server hosts the active copy of the mailbox databaseBoth roles are necessary for automatic recoveryIf Replication service is stopped, automatic
22、recovery will not happenActive ManagerSelection of Active Database CopyActive Manager selects the “best” copy to become active when existing active fails1.Ignores servers that are unreachable or activation is temporarily or regularly blocked2.Sorts copies by currency to minimize data loss3.Breaks ti
23、es during sort based on Activation Preference4.Selects from sorted listed based on copy status of each copyActive ManagerSelection of Active Database CopyActive Manager selects the “best” copy to become active when existing active failsCatalogHealthyCopy statusHealthy, DisconnectedAndHealthy,Disconn
24、ectedAndResynchronizing, orSeedingSourceCopyQueueLength 10ReplayQueueLength 50CatalogCrawlingCopy statusHealthy, DisconnectedAndHealthy,DisconnectedAndResynchronizing, orSeedingSourceCopyQueueLength 10ReplayQueueLength 50CatalogHealthyCopy statusHealthy, DisconnectedAndHealthy,DisconnectedAndResynch
25、ronizing, orSeedingSourceReplayQueueLength 50CatalogCrawlingCopy statusHealthy, DisconnectedAndHealthy,DisconnectedAndResynchronizing, orSeedingSourceReplayQueueLength 505Copy statusHealthy, DisconnectedAndHealthy,DisconnectedAndResynchronizing, orSeedingSourceReplayQueueLength 506CatalogHealthyCopy
26、 statusHealthy, DisconnectedAndHealthy,DisconnectedAndResynchronizing, orSeedingSourceCopyQueueLength 107CatalogCrawlingCopy statusHealthy, DisconnectedAndHealthy,DisconnectedAndResynchronizing, orSeedingSourceCopyQueueLength 3 physical Copies 2 servers out - manual activation of server 3 In 3 serve
27、r DAG, quorum is lostDAGs with more servers sustain more failures greater resiliency High Availability Design ExampleDouble Resilience Maintenance + DB FailureSingle SiteSingle Site4 Nodes4 Nodes3 HA Copies3 HA CopiesJBOD - 3 physical CopiesJBOD - 3 physical CopiesDatabase Availability Group (DAG)DB
28、2DB2DB3DB3DB5DB5DB4DB4DB7DB7DB8DB8DB1DB1DB2DB2DB3DB3DB4DB4MailboxServer 1DB5DB5DB6DB6DB7DB7DB8DB8DB1DB1DB2DB2MailboxServer 2MailboxServer 3XCAS NLB FarmCAS NLB FarmAD: DublinAD: DublinDB3DB3DB4DB4DB5DB5DB6DB6DB7DB7DB8DB8MailboxServer 4DB1DB1XDB6DB6Upgrade server 1Upgrade server 1Server 2 failsServer
29、 2 failsServer 1 upgrade is doneServer 1 upgrade is done2 active copies die2 active copies dieHigh Availability Design ExampleDouble Node/Disk Failure ResilienceKey TakeawaysGreater end-to-end availability with Mailbox ResiliencyUnified framework for high availability and site resilienceFaster and easier to deploy with Incremental DeploymentSupports large mailboxes for less moneyQ & AAsk the Expert (F4)In next 70 minutes, I will be available at the “Ask the Expert” area to answer your questions
