Exchange 2010HA CTD

7/30/2019 Exchange 2010HA CTD

1/44


2/44

Kaliyan SelvarajTechnical ConsultantDell India Pvt. Ltd.,


3/44

Review of Exchange Server 2007 Availability SolutionsOverview of Exchange 2010 High Availability

Exchange 2010 High Availability Fundamentals

Exchange 2010 Incremental Deployment

DAG Demo (Creation, Adding Database Copy, *Over)Exchange 2010 High Availability Design Examples


4/44

Exchange Server 2007Availability Solutions


5/44

Single Copy Cluster (SCC) out-of-box provides little highavailability value

On Store failure, SCC restarts store on the same machine;no clustered mailbox server (CMS) failover

SCC does not automatically recover from storage failuresSCC does not protect your data, your most valuable asset

SCC does not protect against site failures

SCC redundant network is not leveraged by CMS

Conclusion

SCC only provides protection from server hardware failuresand bluescreens, the relatively easy components to recover

Supports rolling upgrades without losing redundancy


6/44

1. Copy logs

E00.log

E0000000012.log

E0000000011.log

2. Inspect logs

3. Replay logs

Log Log

Log shipping to a localdisk

LocalFile

Share

Log shipping within a cluster

Cluster

Log shipping to a standbyserver or cluster

Standby

Database

Database


7/44

DB1

Client Access

Server

CCR #1

Node A

CCR #1

Node B

CCR #2

Node BCCR #2

Node A

SCR

Outlook (MAPI)client

Windows cluster Windows cluster

OWA, ActiveSync, orOutlook Anywhere

AD site: San Jose

AD site: Dallas

Client Access

Server

Standby

Server

SCR managed

separately; no

GUI

Manual

activation of

remote mailbox

server

Clustering

knowledgerequired

DB2

DB3

DB1

DB2

DB3

DB4

DB5

DB6

DB4

DB5

DB6

Database failure

requires server

failover

DB4

DB5

DB6Mailbox server

cant co-exist

with other roles


8/44

Windows Failover Cluster

Default Cluster

Group

Cluster IP Address

Cluster NameCluster Quorum

Cluster

Database

Clustered Mailbox

Server (CMS)

CMS IP Address

CMS NameCMS resources

(exres.dll)

CMS disk resources

Cluster

Networks


9/44

Database Availability Group

Windows Failover Cluster

Default Cluster Group

Cluster IP Address

Cluster Name

Cluster Quorum

Cluster

Database

Active Manager

PAM

SAM

DAG Networks


10/44


Mailbox Server

Get-

MailboxDatabaseCopyStatus

Primary Active Manager

Move-

ActiveMailboxDatabase

Storage

Mailbox Server

Get-


Standby Active Manager

Move-


Storage

Mailbox Server

Get-


Standby Active Manager

Move-


Storage


11/44

Overview of Exchange 2010 HighAvailability


12/44

Reduce complexity

Reduce cost

Native solution - no single point of failure

Improve recovery timesSupport larger mailboxes

Support large scale deployments

Make High Availability Exchange

deployments mainstream!


13/44

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

Easier and cheaper to deploy

Easier and cheaper to manage

Better Service Level

Agreements (SLAs)

Reduced storage costs

Larger mailboxes Further Input/Output (I/O)

reductions

RAID*-less/JBOD** support

Key Benefits

Online mailbox moves

Improved transport resiliency


Better SLAs

Improved mailbox uptime

More storage flexibility

Better end-to-end availability

*Redundant Array of Independent Disks (RAID) **Just a Bunch of Disks (JBOD)


14/44

Client

DB2

DB3

DB2

DB3

DB4

DB4

DB5

Client Access

Server (CAS)

Mailbox

Server 1

Mailbox

Server 2

Mailbox

Server 3

Mailbox

Server 6

Mailbox

Server 4

AD site: Dallas

AD site: San Jose

Mailbox

Server 5

DB5

DB2

DB3

DB4

DB5DB1

DB1DB1

DB1

Failover

managed within

Exchange

Database

(DB) centric

failover

Easy to

stretch across

sites

Client Access

ServerAll clients connect

via CAS servers DB3

DB5

DB1


15/44

Exchange 2010High Availability Fundamentals


16/44

Database AvailabilityGroup

Server

Database

Database Copy

Active Manager (AM)

Remote Procedure Call(RPC) Client Accessservice

DAG


17/44

A group of up to 16 servers hosting a set of replicateddatabases

Wraps a Windows Failover Cluster

Manages servers membership in the group

Heartbeats servers, quorum, cluster database

Defines the boundary of database replication

Defines the boundary of failover/switchover (*over)

Defines boundary for DAGs Active Manager

Mailbox

Server 1

Mailbox

Server 2

Mailbox

Server 3

Mailbox

Server 4

Mailbox

Server 16


18/44

Unit of membership for a DAG

Hosts the active and passive copies of multiple mailbox databases

Executes Information Store, CI, Assistants, etc., services on active

mailbox database copiesExecutes replication services on passive mailbox database copies

DB2

DB3

DB4

Mailbox

Server 1

Mailbox

Server 2

Mailbox

Server 3

DB1

DB1 DB3

DB4

DB2


19/44

Unit of *over

A database has 1 active copy active copy can be

mounted or dismountedMaximum # of passive copies == # servers in DAG 1

DB2

DB3

DB4

Mailbox

Server 1

Mailbox

Server 2

Mailbox

Server 3

DB1

DB1 DB3

DB4

DB2 DB1


20/44

Scope of replication

A copy is either source or target of replication at any given time

A copy is either active or passive at any given time

Only 1 copy of each database in a DAG is active at a timeA server may not host >1 copy of a any database

MailboxServer 1 MailboxServer 2

DB1

DB3

DB2

DB1

DB3

XDB2DB1


21/44

Primary Active Manager (PAM)Runs on the node that owns the default cluster group(quorum resource)

Gets topology change notifications

Reacts to server failures

Selects the best database copy on *overs

Standby Active Manager (SAM)

Runs on every other node in the DAG

Responds to queries from other Exchange components for

which server hosts the active copy of the mailbox database


22/44

Continuous replication has the following basic steps:

Database copy seeding of target

Log copying from source to target

Log inspection at target

Log replay into database copy


23/44

There are three ways to seed the target instance:

Automatic Seeding

Requires 1st

log file containing CreateDB recordUpdate-MailboxDatabaseCopy cmdlet

Can be performed from active or passive copies

Manually copy the database


24/44

Log shipping in Exchange 2010 leverages TransmissionControl Protocol (TCP) sockets

Supports encryption and compressionAdministrator can set TCP port to be used

Replication service on target notifies the active instancethe next log file it expects

Based on last log file which it inspectedReplication service on source responds by sending therequired log file(s)

Copied log files are placed in the targets Inspectordirectory


25/44

Active Manager selects the best copy to become

active when existing active fails

Catalog Healthy

Copy status Healthy, DisconnectedAndHealthy,

DisconnectedAndResynchronizing,or

SeedingSource

CopyQueueLength < 10

ReplayQueueLength < 50

Catalog Crawling



SeedingSource



Catalog Healthy



SeedingSource


Catalog Crawling



SeedingSource


5Copy status Healthy, DisconnectedAndHealthy,


SeedingSource


6Catalog Healthy



SeedingSource


7Catalog Crawling



SeedingSource


8Catalog Healthy



SeedingSource

9Catalog Crawling



SeedingSource

10Copy status Healthy, DisconnectedAndHealthy,


SeedingSource


26/44

Streaming backup APIs for public use have been cut, must use VolumeShadow Copy Service (VSS) for backups

Backup from any copy of the database/logs

Always choose Passive (or Active) copy

Backup an entire serverDesignate a dedicated backup server for a given database

Restore from any of these backups scenarios

DB2

DB3

DB2

DB3

DB1

DB3

DB1 DB1

VSS requestor

DB2


Mailbox

Server 1Mailbox

Server 2

Mailbox

Server 3


27/44

Exchange 2010 HA

E-mail archive

Extended/protected dumpsterretention

7-14 day lag copy

X


Mailbox

Server 1Mailbox

Server 2

Mailbox

Server 3

DB1

DB2

DB3

DB1

DB2

DB3

DB1

DB2

DB3

Site/server/disk failure

Archiving/compliance

Recover deleted items


28/44

Legacy Deployment Steps (CCR/SCC) Exchange 2010 Incremental Deployment

1. Prepare hardware, install proper OS,

and update

Extra for SCC: configure storage

2. Build Windows Failover Cluster

Extra for SCC: configure storage

3. Configure cluster quorum, file share

witness, and public and private

networks

4. Run Setup in Custom mode and install

clustered mailbox server5. Configure clustered mailbox server

Extra for SCC: configure disk

resource dependencies

6. Test *overs

1. Prepare hardware, install proper OS,

and update

2. Run Setup and install Mailbox role

3. Create a DAG and replicate databases

4. Test *overs


29/44

Easy to add high availability to existing deployment

High availability configuration is post-setupHA Mailbox servers can host other Server Roles

Mailbox

Server 1

Mailbox

Server 2


Mailbox

Server 3

Datacenter 1 Datacenter 2

Reduces cost and complexity of HA deployments


30/44

Exchange Management Console


31/44



32/44



33/44

Exchange Management Shell

Create a DAGNew-DatabaseAvailabilityGroup -Name DAG1 -FileShareWitnessShare\\CTD-CH02\DAGWitness -FileShareWitnessDirectory C:\DAGWitness

Add first Mailbox Server to DAGAdd-DatabaseAvailbilityGroupServer -Identity DAG1 -MailboxServer CTD-MBX1 -DatabaseAvailablityGroupIpAddresses 192.168.1.100

Add second and subsequent Mailbox ServerAdd-DatabaseAvailabilityGroupServer -Identity DAG1 -MailboxServer CTD-MBX2

Add-DatabaseAvailabilityGroupServer -Identity DAG1 -MailboxServer

EXMBX3 -DatabaseAvailablityGroupIpAddresses 192.168.1.100,192.168.2.10

Add Mailbox Database CopyAdd-MailboxDatabaseCopy -Identity MBXDB1 -MailboxServer CTD-MBX2

Extend as needed


34/44

HA Administration within ExchangeRecovery uses the same simpleoperation for a wide range of failures

Simplified activation of Exchangeservices in a standby datacenter

Reduces cost andcomplexity of management

M i A il bilit i th E h M t C l


35/44

1

2

Managing Availability in the Exchange Management Console

3View locations and status of

replicated copies

Take action (add copies,

change master, etc.)

Select a database


36/44

DAG D LAB S t Di


37/44

DAG Demo LAB Setup Diagram


38/44

Exchange 2010High Availability Design Examples


39/44

File

Share

File

Share

File

Share

File

Share

File

Share


40/44

Single Site

3 HA Copies

Database Availability Group (DAG)

Mailbox

Server 1

Mailbox

Server 2Mailbox

Server 3

3 Nodes

X

JBOD -> 3 physical Copies

2 servers out -> manualactivation of server 3

In 3 server DAG, quorum is lost

DAGs with more servers sustain

more failures greater resiliency


41/44

CAS/HUB/

MAILBOX 1

CAS/HUB/

MAILBOX 2

Member servers of DAGcan host other server roles

DB2

2 server DAGs, with server

roles combined or not, should

use RAID


42/44

With each release, our goals are to make Exchangehigh availability:

Easier and cheaper to deploy


Support better SLAs with faster and more granular

recoveriesImprove site resiliency support

Our other goal is for highly available deployments to bemainstream!


43/44


44/44

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.

Exchange 2010HA CTD

Documents

Transcript of Exchange 2010HA CTD