Exchange Server Continuous Replication. Cluster. Local. Standby. 2. Inspect logs. 1. Copy logs. 3. Replay logs. Log. Log

Size: px

Start display at page:

Download "Exchange Server Continuous Replication. Cluster. Local. Standby. 2. Inspect logs. 1. Copy logs. 3. Replay logs. Log. Log"

Madeline Robbins
5 years ago
Views:

Exchange Server 2007 Continuous Replication 2. Inspect logs Database Log E00.log E0000000012.log E0000000011.log 1. Copy logs Log Database 3.

3 Exchange Server 2007 Continuous Replication 2. Inspect logs Database Log E00.log E log E log 1. Copy logs Log Database 3. Replay logs Local Cluster File Share Standby Log shipping to a local disk Log shipping within a cluster Log shipping to a standby server or cluster 3

Exchange Server 2007 CCR + SCR Outlook (MAPI) client AD site: San

Manual activation of remote mailbox server Mailbox server can t

Standby Server SCR DB4 DB5 DB6 CCR #1 Node A CCR #1 Node B CCR #2

cluster DB1 DB4 Windows cluster DB4 Clustering knowledge required

4 Exchange Server 2007 CCR + SCR Outlook (MAPI) client AD site: San Jose OWA, ActiveSync, or Outlook Anywhere Client Access Server Manual activation of remote mailbox server Mailbox server can t co-exist with other roles AD site: Dallas Client Access Server Standby Server SCR DB4 DB5 DB6 CCR #1 Node A CCR #1 Node B CCR #2 Node A CCR #2 Node B SCR managed separately; no GUI DB1 Windows cluster DB1 DB4 Windows cluster DB4 Clustering knowledge required DB2 DB3 DB2 DB3 DB5 DB6 DB5 DB6 Database failure requires server failover 4

5 DB1 DB2 DB4 DB5 DB1 DB2 DB3 DB4 DB5

6 Make High Availability Exchange deployments mainstream! 6

Improved mailbox uptime Improved failover granularity Simplified administration Incremental deployment Unification of CCR + SCR Easy stretching across sites Up to 16 replicated copies Key Benefits

7 Improved mailbox uptime Improved failover granularity Simplified administration Incremental deployment Unification of CCR + SCR Easy stretching across sites Up to 16 replicated copies Key Benefits Easier and cheaper to deploy Easier and cheaper to manage Better Service Level Agreements (SLAs) More storage flexibility Further Input/Output (I/O) reductions RAID*-less/JBOD** support Reduced storage costs Larger mailboxes Better end-to-end availability Online mailbox moves Improved transport resiliency Easier and cheaper to manage Better SLAs *Redundant Array of Independent Disks (RAID) **Just a Bunch of Disks (JBOD) 7

25 Keeping Users Connected

26 Keeping Users Connected

27 Keeping Users Connected

37 DAG 37

38 Mailbox Server 1 Mailbox Server 2 Mailbox Server 3 Mailbox Server 4 Mailbox Server 16 38

39 Mailbox Server 1 Mailbox Server 2 Mailbox Server 3 DB1 DB2 DB3 DB4 DB1 DB2 DB3 DB4 39

40 RCA Mailbox Server 1 Mailbox Server 2 Mailbox Server 3 DB1 DB2 DB3 DB4 DB1 DB2 DB3 DB4 40

41 Mailbox Server 1 Mailbox Server 2 Mailbox Server 3 DB1 DB2 DB3 DB4 DB1 DB2 DB3 DB4 DB1 41

42 Exchange Server 2010 High Availability Fundamentals Mailbox Database (Continued) 42

43 43

44 Exchange Server 2010 High Availability Fundamentals Mailbox Database Copy Mailbox Server 1 Mailbox Server 2 DB1 DB2 DB3 X DB1 DB1 DB2 DB3 44

45 Exchange Server 2010 High Availability Fundamentals Mailbox Database Copy ActiveCopy ActivationSuspended 45

46 46

47 47

48 48

49 49

50 Database Availability Group Mailbox Server 1 Mailbox Server 2 Mailbox Server 3 DB1 DB2 DB1 DB2 DB1 DB2 50 DB3 DB3 DB3 VSS requestor

51 Site/server/disk failure Archiving/compliance Recover deleted items Database Availability Group Mailbox Server 1 Mailbox Server 2 Mailbox Server day lag copy DB1 DB1 DB1 DB2 DB2 DB2 DB3 DB3 DB3 X 51

53 File Share File Share File Share File Share File Share 53

54 2 servers out -> manual activation Single of server Site 3 Nodes In 3 server DAG, quorum is lost HA Copies DAGs with more servers sustain more JBOD failures -> 3 physical greater resiliency Copies Mailbox Server 1 Mailbox Server 2 Mailbox Server 3 X Database Availability Group (DAG) 54

55 CAS/HUB/ MAILBOX 1 CAS/HUB/ MAILBOX 2 Member servers of DAG can host other server roles DB2 2 server DAGs, with server roles combined or not, should use RAID 55

57 57

58 58

59 59

Recovering Failure Scenario: Primary Database Server Center Failure Center Failure 1. Verify MBX-A-1 Primary primary data DB1 fails center data fails center fails is capable of hosting service 2.

necessary) ActiveDirectorySite Redmond 3.

60 Recovering Failure Scenario: Primary Database Server Center Failure Center Failure 1. Verify MBX-A-1 Primary primary data DB1 fails center data fails center fails is capable of hosting service 2. Add Automatic Adjust primary DNS failover records data center to for MBX-A-2 SMTP servers and back HTTPS to DAG: access Start-DatabaseAvailabilityGroup and adjust CAS configuration DAG1 (if necessary) ActiveDirectorySite Redmond 3. Reconfigure MBX-A-1 Run Stop-DatabaseAvailabilityGroup DB1 is fixed DAG is fixed use and File Share Witness DAG1 ActiveDirectorySite in primary data center: Redmond Set-DatabaseAvailabilityGroup ConfigurationOnly (in both DAG1 data WitnessDirectory c:\fsw\dag1 becomes centers) a copy WitnessServer HT-A 4. Reseed Stop the data cluster or allow service replication the nodes: to occur Stop-Service and update ClusSvc copies in primary data center 5. Schedule Restore-DatabaseAvailabilityGroup downtime for the mailbox databases DAG1 ActiveDirectorySite and dismount them Bel Air AlternateWitnessDirectory 6. Change c:\fsw\dag1 MX records AlternateWitnessServer and HTTP access HT-B back to primary data center Legend Active Database Move Databases databases mount back (no activation to primary block data center: scenario) Move-Activ boxDatabase DB1 ActivateOnServer MBX-A-1 Database Copy 8. Mount databases in primary data center Unhealthy? Database Edge-A Proxy-A 2.1.x.x Perimeter Network Contoso.com (MX Record) Autodiscover.contoso.com Mail.contoso.com Load Balance Array Records Proxy-B Edge-B 2.2.x.x Perimeter Network DC-A HT-A CAS-A CAS-B HT-B DC-B x.x MAPI Network DAG x.x MAPI Network DAG1 DB1 MBX-A-1 DB2 DB1 MBX-A-2 DB2 MBX-B-3 DB1 DB2 MBX-B-4 DB1 DB2 DB3 DB4 DB3 DB4 DB3 DB4 DB3 DB x.x Replication Network AD Site Redmond Outlook 2007/14 (MBX on DB1) x.x Replication Network AD Site Bel Air 60

61 61

62 One Technology for High Availability, Disaster Recovery and Backup

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.

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

63 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.

64 64

65 65

66 66

67 67

68 68

65 98 7 10 Catalog Healthy Crawling Copy status Healthy, DisconnectedAndHealthy,

69 Catalog Healthy Crawling Copy status Healthy, DisconnectedAndHealthy, DisconnectedAndResynchronizing, or SeedingSource ReplayQueueLength CopyQueueLength < 10 < 50 ReplayQueueLength < 50 69

70 Mailbox Server 1 Mailbox Server 2 Mailbox Server 3 DB1 X DB1 DB1 70

71 71

72 72

Kunal Mahajan Microsoft Corporation

Kunal Mahajan Microsoft Corporation 65+ Million Customer hosted Mailboxes 30+ Million Partner hosted Mailboxes 1,800 Partners Strategic Business Challenges Our Sales teams need to connect with the right