NYExUG_2009.11.10 - New York Exchange User Group

Download Report

Transcript NYExUG_2009.11.10 - New York Exchange User Group



Exchange Server 2007
Continuous Replication
2. Inspect logs
Database
Log
Log
E00.log
E0000000012.log
E0000000011.log
1. Copy logs
Local
Cluster
Database
3. Replay logs
Standby
File
Share
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
OWA, ActiveSync, or
Outlook Anywhere
AD site: San Jose
Client Access
Server
CCR #1
Node A
CCR #1
Node B
Windows cluster
Manual
“activation” of
remote mailbox
server
AD site: Dallas
Client Access
Server
DB4
DB5
Standby
Server
Mailbox server
can’t co-exist
with other roles
CCR #2
Node A
DB6
SCR
CCR #2
Node B
Windows cluster
DB1
DB1
DB4
DB4
DB2
DB2
DB5
DB5
DB3
DB3
DB6
DB6
SCR managed
separately; no
GUI
Clustering
knowledge
required
Database failure
requires server
failover
4
DB1
DB1
DB2
DB2
DB3
DB4
DB4
DB5
DB5
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
More storage flexibility
•
•
Further Input/Output (I/O)
reductions
RAID*-less/JBOD** support
Key Benefits
 Easier and cheaper to deploy
 Easier and cheaper to manage
 Better Service Level
Agreements (SLAs)
 Reduced storage costs
 Larger mailboxes
Better end-to-end availability
• Online mailbox moves
• Improved transport resiliency
 Easier and cheaper to manage
 Better SLAs
7
*Redundant Array of Independent Disks (RAID)
**Just a Bunch of Disks (JBOD)
Keeping Users Connected
Keeping Users Connected
Keeping Users Connected
DAG
37
Mailbox
Server 1
Mailbox
Server 2
Mailbox
Server 3
Mailbox
Server 4
Mailbox
Server 16
38
Mailbox
Server 1
Mailbox
Server 2
Mailbox
Server 3
DB1
DB4
DB3
DB2
DB1
DB4
DB3
DB2
39
RCA
Mailbox
Server 1
Mailbox
Server 2
Mailbox
Server 3
DB1
DB4
DB3
DB2
DB1
DB4
DB3
DB2
40
Mailbox
Server 1
Mailbox
Server 2
Mailbox
Server 3
DB1
DB4
DB3
DB2
DB1
DB4
DB3
DB2
DB1
41
Exchange Server 2010 High
Availability Fundamentals
Mailbox Database (Continued)
42
43
Exchange Server 2010 High
Availability Fundamentals
Mailbox Database Copy
Mailbox
Server 1
DB1
Mailbox
Server 2
X
DB1
DB2
DB2
DB1
DB3
DB3
44
Exchange Server 2010 High
Availability Fundamentals
Mailbox Database Copy
ActiveCopy
ActivationSuspended
45
46
47
48
49
Database Availability Group
Mailbox
Server 1
Mailbox
Server 2
Mailbox
Server 3
DB1
DB1
DB1
DB2
DB2
DB2
DB3
DB3
DB3
VSS requestor
50
Site/server/disk failure
Archiving/compliance
Recover deleted items
Database Availability Group
Mailbox
Server 1
Mailbox
Server 2
Mailbox
Server 3
7-14 day lag copy
DB1
DB1
DB1
DB2
DB2
DB2
DB3
DB3
DB3
X
51
File
Share
File
Share
53
File
Share
File
Share
File
Share
2 servers out -> manual
Single
Site 3
activation
of server
3
Nodes
In 3 server DAG, quorum is lost
3 HA Copies
DAGs with more servers sustain
JBOD
-> 3–physical
Copies
more
failures
greater resiliency
Mailbox
Server 1
Mailbox
Server 2
Mailbox
Server 3
X
Database Availability Group (DAG)
54
CAS/HUB/
MAILBOX 1
CAS/HUB/
MAILBOX 2
DB2
Member servers of DAG
can host other server roles
2 server DAGs, with server
roles combined or not, should
use RAID
55
57
58
59
Recovering
Primary
Data
Center
Failure Scenario:
Data
Center
Failure
Database
Server
Failure
Failure
1.
Verify
primary
data
Primary
data
fails is capable of hosting service
MBX-A-1
DB1center
fails
fails center
2.
Add
primary
data center
servers
back
to DAG:
Start-DatabaseAvailabilityGroup
–ActiveDirectorySite Redmond
Adjust
DNSfailover
records
SMTP
and
HTTPS
access
and adjust CAS configurationDAG1
(if necessary)
Automatic
tofor
MBX-A-2
3.
Reconfigure
DAG
to use
File Share Witness
in primary data center:
Set-DatabaseAvailabilityGroup
DAG1
–WitnessDirectory
Run
Stop-DatabaseAvailabilityGroup
DAG1 –ActiveDirectorySite
Redmond
–ConfigurationOnly (in both
data
MBX-A-1
DB1
is
fixed
is fixed
and
c:\fsw\dag1
–WitnessServer HT-A
centers)
becomes a copy
4.
Reseed
or allow
replication
to occur
and updateClusSvc
copies in primary data center
Stop thedata
cluster
service
on the nodes:
Stop-Service
5.
Schedule
downtime for the mailbox databases
and dismount them
Restore-DatabaseAvailabilityGroup
DAG1 –ActiveDirectorySite
“Bel Air” –AlternateWitnessDirectory
Legend
Active Database
6.
Change
MX
records
and
HTTP
access
back
to
primary
data
center
c:\fsw\DAG1 –AlternateWitnessServer HT-B
Database Copy
7.
Move
databases
to primaryblock
data center:
Move-ActiveMailboxDatabase DB1 –ActivateOnServer MBX-A-1
6.
Databases
mountback
(no activation
scenario)
8.
Mount databases in primary data center
Unhealthy? Database
Contoso.com (MX Record)
Autodiscover.contoso.com
Mail.contoso.com
Load Balance Array
Records
Edge-A
Proxy-A
2.1.x.x Perimeter Network
DC-A
HT-A
Proxy-B
Edge-B
2.2.x.x Perimeter Network
CAS-A
CAS-B
172.16.x.x “MAPI” Network
HT-B
DC-B
172.18.x.x “MAPI” Network
DAG1
DAG1
MBX-A-1
MBX-A-2
MBX-B-3
MBX-B-4
DB1
DB2
DB1
DB2
DB1
DB2
DB1
DB2
DB3
DB4
DB3
DB4
DB3
DB4
DB3
DB4
172.17.x.x “Replication” Network
AD Site Redmond
Outlook
2007/14
(MBX on DB1)
172.19.x.x “Replication” Network
60
AD Site Bel Air
61
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. 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
65
66
67
68
10
8
6
9
5
7
Catalog
Copy status
Crawling
Healthy
Healthy, DisconnectedAndHealthy,
DisconnectedAndResynchronizing,
or
SeedingSource
CopyQueueLength
ReplayQueueLength< 10 < 50
ReplayQueueLength
< 50
69
Mailbox
Server 1
Mailbox
Server 2
X
DB1
DB1
Mailbox
Server 3
DB1
70
71
72