Microsoft Exchange Server 2007 Deployment Planning and High Availability in SP1

Colin LeeMicrosoft Certified Architect – MessagingTechnology Specialist

UNC304

Session Objectives And TakeawaysSession Objectives:

Understand new built-in Sp1 featuresUnderstand best practices for deployment and configuration

Key Takeaways:SP1 delivers in-datacenter redundancy while replicating to another datacenter Minimizes network bandwidth No distance limit or single subnet requirement

SP1 provides better monitoring and more stringent SLAs

Session Agenda

Deployment ConsiderationsStandby Continuous ReplicationReplication over Redundant NetworkWindows 2008 supportTransport Dumpster Q&A

Enterprise network

OtherSMTP

Servers

Mailbox

Mailbox

Routing

Hygiene

Routing

Policy

Voice Messagin

g

Client Access

PBX

PublicFolder

s

Fax

Applications:OWA

Protocols:ActiveSync,

POP, IMAP, RPC / HTTP …Programmabilit

y:Web services,

Web parts

Unified Messaging

EdgeTransport

HubTransport

INTERNET

Exchange 2007 Topology

Things You Need To ConsiderAD

Schema changesPermission changes from Exchange 2003AD data pushed to Edge/ADAMOPATH vs LDAP

Address lists, etc.

DNSAutodiscoverEdge resolution of Exchange servers

Exchange roles (any)

Multi-role server? Clusters? Only mailbox role!

HW and SW pre-reqManagement via roles

Mailbox roleStandalone or clustered?

CCR or SCC?Replication?

LCR/CCR or SAN basedSingle datacenter or cross?

SAN or DAS storage?What kind of disks?

Do you need PFs?

Things You Need To ConsiderHub

No alternate path routingAD site based routing

Hub sitesExchange costs

At least 2 per site (failover)

EdgeStandalone or joined to org?Agent config per Edge serverEdgeSync

CASAutodiscover

Clients part of domain or not?Urls for other services?

Subject Alternative Name (SAN) certificates?

UMLots of telephony terms!Supported IP/PBX/VoIP GWy

AD Readiness Requirements

Windows Server Active Directory ForestSchema Master DC must have Windows 2003 SP1 +GC servers running Windows 2003 SP1 +Forest Functional Level Windows Server 2000+AD Domain Functional Level Windows 2000 Server-native or higher in all domainsGC in each AD Site you will install Exchange Run topology switches (/prepare*) on a system that is in the same AD site as the Schema Master

Forest Preparation using SETUP /PrepareAD Coexistence w/Exchange 2003

/PrepareLegacyExchangePermissions

Base Hardware Requirements

Processorx64 support for Intel and AMD processors Intel Itanium IA64 processors are not supported

MemoryVaries by role2 GB minimum

Server Sizing Recommendations

Role ProcessorsMin/Max

MemoryMin/Max

EquivalentServers

Edge Transport 2; 4 1 GB/Core (2GB Minimum); 16GB/Server DL380; DL385

Hub Transport 4; 8 1 GB/Core (2GB Minimum); 16GB/Server

DL380; DL385, BL480c

Client Access Server (CAS) 4; 4 1 GB per Core (2GB minimum);8GB/Server

DL360; DL365BL460c; BL465c

Unified Messaging (UM) 4; 4 1 GB/Core (2GB Minimum); 4GB/Server

DL360; DL365BL460c;BL465c

Mailbox 4; 8

Max 32GBCalculate as:2GB +2MB to 5MB/mailbox; 32GB/Server Light = 2GB + 2 MB/mailboxMedium = 2GB + 3.5 MB/mailboxHeavy = 2 GB + 5MB per mailbox

DL380;DL385DL580; DL585BL460c;BL465cBL480c; BL685c

Exchange Server 2003Requires shared storageSMTP, OWA, and Mailbox are cluster-awareSingle copy of mailbox dataUp to 8-node Active/Passive2-Node Active/Active

Exchange Server 2007Requires shared storageMailbox Only

Simple redundancy for other rolesSingle copy of mailbox dataUp to 8-node Active/PassiveActive/Active cutImprovements in Install, Management, Behavior

Q

DB

Lo

gs

SMTPMBOWA

Q

DB

Lo

gs

MB

Single Copy Cluster

Store

DB

Replication

Service

Copy

Store

DB

Replication

Service

Copy

Cluster

Standalone Server CCR

LCRLogs

pulled by

Passive

Continuous Replication

Active Node Passive Node

Standby Continuous ReplicationStandby Continuous ReplicationContinuous Replication

SourceDB

InspectorDirectory

TargetLogDirectory

DBCopy

Store

Source LogDirectory

LastLogCopyNotified LastLogCopied

LastLogInspected

LastLogReplayed

ReplicationService

ReplicationService

ReplicationService

Continuous Replication

Standby Continuous Replication

RTM Delivered – CCR, LCR and SCCSP1 Presents - SCR

Designed for datacenter recoveryEnables standby configurations out of the box

No clustering required between servers No single subnet requirement Spans multiple AD sites

Granular configurationFlexible configurationManual activation

DB

Lo

gs

DB

DB

Lo

gs

Lo

gs

FileShare

Standby Continuous Replication

Q

LogsDatabase

LogsDatabase

Passive Node

CCR

MBX

SCC

MBX

Standby Continuous Replication

LogsDatabase

Standby Continuous Replication

Configuration at storage group levelEnable-StorageGroupCopy …–StandbyMachine:Recovery-Red01–ReplayLagTime:1.00:00:00

RequirementsOne database per storage groupSame database and log file paths at source and target50 storage group targets per standby machine

Activation/m:RecoverServer or /RecoverCmsDatabase portability

Standby Continuous Replication

Log Replay Lag TimeAt least 50 log files or ReplayLagTime

No VSS backup support for SCR copySuspend replication and do file level backups

Log truncation at the source is SCR aware

Standby Continuous ReplicationLog Truncation with Replication

CCR and LCR Copies

SCR Target

Has the log file been backed up?

Is the log file below my checkpoint?

Does the other CCR/LCR copy agree with deletion?

Has the log file been inspected by all SCR copies?

Yes Truncate

Is the log file below my checkpoint?

Is the log file older than ReplayLagTime + TruncationLagTime?

Yes Truncate

MB

X-A

DC

/GC

NO

DE-

1 NO

DE-2

CA

S

HU

B

FSW

Cluster Continuous Replication

CMS

Re-home mailboxes

Disable SCR

Enable SCR

Mount Databases

Remote SCR and Database Portability

Standby Continuous Replication and Database Portability

demo

Standby Continuous ReplicationA day in the life of a Standby cluster

with SCR…1. Configure and monitor

a. Enable-StorageGroupCopyb. Update-StorageGroupCopyc. Test-ReplicationHealth

2. Switchover to Standby clustera. Restore-StorageGroupCopyb. Setup /RecoverCms /CmsName /CmsIpAddress

3. Reverse directiona. Rebuild the original cluster or Setup /ClearLocalCMSb. Repeat from 1(a)

Replication over Redundant NetworkLeverage redundant network in CCR

Log shippingEnable-ContinuousReplicationHostName Get-ClusteredMailboxServerStatus

Output: OperationalReplicationHostNames: FailedReplicationHostNames:

InUseReplicationHostNames:Prefer and automatically switch back to Redundant network when available

SeedingUpdate-StorageGroupCopy

-DataHostNames:Host1,Host2

Replication over Redundant NetworkConfiguration Requirements

“mixed network” not “private network”Strict name checking is disabled

http://support.microsoft.com/kb/281308 DNS server configured on “mixed network” adapters

DNS server can be on public network

Sp1 Beta2Windows 2003 Windows 2008 Beta3 might need extra workarounds

Replication over Redundant Network

demo

Windows Server 2003 Windows Server 2008 Exchange Server

Support

Shared Disk Quorum Shared Disk Quorum √ …but not recommended for Windows Server 2008

MNS Quorum Node Majority Quorum √

MNS + FSW Quorum Node Majority + FSW Quorum Recommended for CCR

NA Node Majority + Disk Witness Quorum Recommended for SCC

8 Node clusters 16 Node clusters 8 nodes only

IPv4 IPv4 and IPv6 √

NA DHCP – v4 √

Single Subnet Multi Subnet √ - Same AD site

Windows Server 2008 Support

Windows Server 2008 Support

Default TTL is 20 minutesConfigurable on Windows 2008cluster.exe res  CMS1 

/priv HostRecordTTL=300

Use lower TTL for Multi-subnet clusteringStandby clustering

Transport Dumpster

Transport Dumpster support for LCRDumpster Statisticsget-storagegroupcopystatus -dumpsterstatistics

Output: DumpsterServersNotAvailable:{HUB1} DumpsterStatistics:

{HUB2( 7/22/2007

10:20:37 PM; 2; 1032KB)}

SG1xSG1

Transport Dumpster

Statistics will show Message3 as the oldest item for SG1If SG1 goes through a lossy failover, Message2 will be redelivered because it is still in the dumpsterA message does not appear in the dumpster until it is delivered to all its recipients

Dumpster resubmit requests stored and honored upon message qualifying for dumpster queue

Message1 Message2 Message3 Message4 Message5

SG1 SG1 SG1

SG2

SG3 SG3

SG2

x

Transport Dumpster

demo

Improved ManagebilitySingle task to report all aspects of Replication: Test-ReplicationHealth

Cluster status Node availabilityQuorumCluster service

Replication Service statusStorage Group Copy status

FailedSuspendedQueue lengths

Included in Microsoft Operations Manager (MOM) Management Pack

Improved ManagebilityNew GUI

Manage Clustered Mailbox Server Wizard

Move, Stop, Start CMSCCR Replication StatusSuspend, Resume, Update and Restore Replication Queue columns for storage groups

Performance Improvements

Less IO load on the copyKeep replay database cache aliveBetter than 1:1 source to copy IO ratio

Faster movesNo database cache flush for CCRPreparatory database cache flush for SCC

Set desired checkpoint lowerIf achieved in 5 minutes, continue with move

Questions?

Evaluation Forms

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