exchange 2010 high availability and storage

25
Exchange 2010 High Availability Harold Wong IT Pro Evangelist blogs.technet.com/haroldwong

Post on 19-Oct-2014

20.366 views

Category:

Technology


1 download

DESCRIPTION

Exchange Server 2010 Launch Deck: High Availability and Storage

TRANSCRIPT

Page 1: Exchange 2010 High Availability And Storage

Exchange 2010 High AvailabilityHarold WongIT Pro Evangelistblogs.technet.com/haroldwong

Page 2: Exchange 2010 High Availability And Storage

High Availability Fundamentals

Storage Improvements

Agenda

Exchange 2010 High Availability Fundamentals

High Availability Design Examples

End-to-End Availability Improvements

Page 3: Exchange 2010 High Availability And Storage

E-Mail Trends

The average corporate user can expect to send and receive about 156 messages a day, and this number is expected to grow to about 233 messages a day by 2012. An increase of 33% over the four-year period. (Radicati, 2008)

Business users report that they currently spend 19% of their work day, or close to 2 hours/day on email. (Radicati, 2007)

2008 2010 2012 20140

50

100

150

200

250

Messages Sent/Received Per User/Day

“The company runs

on e-mail”

“If e-mail stops,

business stops”

Page 4: Exchange 2010 High Availability And Storage

High Availability ImprovementsKey benefits

Easier & cheaper to manage

Better SLAs

Further IO reductions RAID-less / JBOD support

Better end-to-end availability

Reduced storage costs Larger mailboxes

Further IO reductions RAID-less / JBOD support

More storage

flexibility

Easier & cheaper to deploy

Easier & cheaper to manage

Better SLAs

Improved failover granularity

Simplified administration Incremental deployment Unification of CCR + SCR Easy stretching across

sites Up to 16 replicated copies

Improved mailbox uptime

Page 5: Exchange 2010 High Availability And Storage

Unified Platform for High Availability and Disaster Recovery

Evolution of continuous replication technology Combines the capabilities of CCR and SCR into one

platform Easier than traditional clustering to deploy and manage Allows each database to have up to 16 replicated copies Provides full redundancy of Exchange roles on two servers

San Jose Dallas

Mailbox Server

DB1

DB3DB2

DB4DB5

Mailbox Server

DB1DB2

DB4DB5

DB3

Mailbox Server

DB1DB2

DB4DB5

DB3

Recover quickly from disk and database failures

Replicate databases to remote datacenter

Page 6: Exchange 2010 High Availability And Storage

Client Access Server

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

Failover managed within Exchange

Easy to stretch across sites

Client Access Server

All clients connect via CAS servers

Database Availability Group

Client

DB2

DB3

DB1 DB4

DB5

DB1

DB2

DB3

DB4

DB5

DB1

DB2

DB3

DB4

DB5

DB1

DB3

DB5

DB1

DB1

Database centric failover

Exchange 2010 High Availability Overview

Page 7: Exchange 2010 High Availability And Storage

Database Availability Group (DAG) Mailbox Servers Mailbox Database Database Copy Active Manager RPC Client Access Service

(Active Manager Client)

High Availability Fundamentals

DB2

DB1

DB2

DB3

DB1

DB2

DB3

DB1

Active Manager

Active Manager

Active Manager

DB3

Database Availability Group

RPC Client Access Service

Page 8: Exchange 2010 High Availability And Storage

Exchange 2010 HA FundamentalsDatabase Availability Group (DAG)

Group of up to 16 servers Wraps a Windows® Failover Cluster Defines the boundary of replication and

failover/switchover

Mailbox Servers …. Host the active and passive copies of

multiple mailbox databases Support up to 100 databases per server

Page 9: Exchange 2010 High Availability And Storage

Mailbox Database Unit of Failover/Switchover 30 second Database Failover/Switchover Database names are unique across an forest

Mailbox Database Copy A database has one active copy in a DAG A server may not host more than one copy of a

given database Replication of copies using Log Shipping System tracks health of each copy

Exchange 2010 HA FundamentalsMailbox Databases and Copies

Page 10: Exchange 2010 High Availability And Storage

High Availability’s Brain Manages which database copies should

be active and passive Source of definitive information on

where a database is active and mounted Active Directory is primary source for

configuration information Active Manager is primary source for

changeable state information such as active and mounted

A process that runs on every server in DAG

Exchange 2010 HA FundamentalsActive Manager

Active Manager

Page 11: Exchange 2010 High Availability And Storage

Incremental DeploymentReduces cost and complexity of HA deployments Easy to add high availability to existing deployment High availability configuration is post-setup

HA Mailbox servers can host other server roles

Mailbox Server 1

Mailbox Server 2

Database Availability Group

Mailbox Server 3

Datacenter 1 Datacenter 2

DB2

DB3

DB1

DB2

DB3

DB1

DB2

DB3

DB1

Page 12: Exchange 2010 High Availability And Storage

Simplified ManagementReduces cost and complexity of management

HA Administration within Exchange Recovery uses the same simple operation

for a wide range of failures Simplified activation of Exchange services

in a standby datacenter

Page 13: Exchange 2010 High Availability And Storage

High Availability Management

demo

Page 14: Exchange 2010 High Availability And Storage

DB2

DB3

DB1

DB2

DB3

DB1

DB2

DB3

Use a VSS backup solution Backup from any copy of the database/logs Always choose passive (or active) copy Backup an entire server Designate a dedicated backup server for a given database

Restore from any of these backups:

Exchange Server 2010 Backups

VSS request

or

DB1

Mailbox Server 1

Mailbox Server 2

Database Availability Group

Mailbox Server 3

Page 15: Exchange 2010 High Availability And Storage

Storage ImprovementsPerformance enhancements enable new options

Exchange 2010 Storage Enhancements

70% reduction in IOPS Smoother IO patterns Resilience against corruption

Read IOPS Write IOPS

Ex 2003

Ex 2007

Ex 2010

Choose from a wide range of storage technologies without sacrificing system availability:

Storage Area Network (SAN)Direct Attached w/ SAS Disks

JBOD SATA (RAID-less)Direct Attached w/ SAS Disks

Page 16: Exchange 2010 High Availability And Storage

Lowering Exchange 2010 Storage Costs Optimized for DAS storage Use larger, slower, cheaper disks

Support larger mailboxes at lower cost HA provides resilience from disk failures

HA Solution remains unchanged regardless of data volume size

JBOD/RAID-less storage now an option Requires 3+ DB Copies

Page 17: Exchange 2010 High Availability And Storage

Exchange 2010 Cost Savings

Storage flexibility Simplified

management Simplified site

resilience All server roles on

one server (Small deployments)

Storage Cost savings examples

E2003 SCC (FC SAN)

E2007 CCR (SAS DAS)

E2010 DAG (SATA DAS)

$0

$5

$10

$15

$20

$25

$30

$35

$27

$19

$13

$0

$34

$21

Server/Storage Capex $/Mailbox

$/Mailbox (500 MB)

$/Mailbox (2 GB)

3000 Mailboxes2 Node Cluster

E2007 CCR (SAS DAS)

E2010 DAG (SATA DAS)

$0$5

$10$15$20$25$30$35

$32

$8

Hardware Capex $/Mailbox

$/Mailbox (2GB)

24,000 Mailboxes

4 x 2 Node CCR

2 copies (RAID)

6 Node DAG 3 copies (JBOD)

Double Server/Disk

Failure Resiliency

Page 18: Exchange 2010 High Availability And Storage

Automatic protection against loss of queued e-mails due to hardware failure

Simplifies hub and edge transport server upgrades and maintenance

Improved Transport Resiliency

Mailbox Server

HubTransport

Edge Transport

EdgeTransport

Servers keep “shadow copies” of items until they are delivered to the next

hop

X

Page 19: Exchange 2010 High Availability And Storage

E-Mail Client

Mailbox Server 1 Mailbox Server 2

Client Access Server

Exchange 2010 & Exchange 2007 SP2 Online

Exchange 2003 Offline

Users remain online while their mailboxes are moved

between servers Sending messages Receiving messages Accessing entire mailbox

Administrators can perform migration and maintenance during regular hours

Also can be used to migrate users from on-premise server to Exchange Online

Online Move MailboxLimit user disruption during mailbox moves and maintenance

Page 20: Exchange 2010 High Availability And Storage

CAS/HUB/

MAILBOX 1

CAS/HUB/

MAILBOX 2

Mailbox servers in a DAG can host other Exchange server roles

Hardware Load Balancer

DB1

DB2

DB3

DB2

DB1

DB2

DB3

2 server configurations, should always use RAID

High Availability Design ExampleBranch office or smaller deployment

Page 21: Exchange 2010 High Availability And Storage

High Availability for Other Server Roles

Configure IP gateway to point to more than

one UM server

Unified Messaging

No special configuration required (load balancing and failover is automatic)

Hub Transport

Hardware load balancer (recommended) or Windows Network Load Balancing (NLB)

Client Access

Use DNS round robin, multiple MX recordsEdge

Transport

Page 22: Exchange 2010 High Availability And Storage

High Availability Management (Closure)

demo

Page 23: Exchange 2010 High Availability And Storage

Exchange 2010 High Availability ….. Easier & cheaper to deploy Simplified administration Granular failover & recovery Better end-to-end availability One technology for both high availability and

site resilience

Summary

Page 24: Exchange 2010 High Availability And Storage

Learn More About Exchange 2010

Technical Resources

The New Efficiency Virtual Launch Experience TechNet Exchange Website Exchange Webcasts and Podcasts

Get Hands on Training

Training Offers—Exclusive for Launch Attendees

Community Resources

Exchange Team Blog Exchange Forums

http://msexchangeteam.com/URL here

http://social.technet.microsoft.com/Forums/en-US/exchange2010/threads

www.microsoft.com/learning/careeroffers

www.thenewefficiency.com

http://technet.microsoft.com/en-us/exchange/default.aspx

http://technet.microsoft.com/en-us/exchange/bb288465.aspx

Page 25: Exchange 2010 High Availability And Storage

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