exchange 2007 - erfaring fra feltet, bernt lervik

Exchange 2007 – Notes from the field

Bernt Lervik | [email protected] Architect | Avanade Norway

AgendaAgendaMicrosoft and Avanade Exchange 2007 EnvironmentMicrosoft and Avanade Exchange 2007 Environment

Avanade ITS Exchange environment overviewAvanade ITS Exchange environment overviewMicrosoft IT Exchange environment overviewMicrosoft IT Exchange environment overviewTransport and topologyTransport and topologyExchange 2007 roles and features – a quick reminderExchange 2007 roles and features – a quick reminderMailbox server and storage designsMailbox server and storage designsBackup approachBackup approachMobile messaging scenariosMobile messaging scenariosInternet mail connectivityInternet mail connectivity

Exchange Environment OverviewExchange Environment Overviewat Avanadeat Avanade

Multiple Exchange organizationsMultiple Exchange organizations~11 Exchange 2003 servers~11 Exchange 2003 servers~8 Exchange 2007 mailbox servers running in the Corp forest~8 Exchange 2007 mailbox servers running in the Corp forest

Mailboxes – 6,500+ Mailboxes – 6,500+ Maximum message size = 10 MBMaximum message size = 10 MBAvailability Goal – 99.99%Availability Goal – 99.99%

Mailbox size on Exchange 2003 = 75 MB Mailbox size on Exchange 2003 = 75 MB Mailbox sizes on Exchange 2007 = 500 MB and 2 GBMailbox sizes on Exchange 2007 = 500 MB and 2 GB

Avanade has a highly mobile, distributed work force with Avanade has a highly mobile, distributed work force with more than 80 percent of its employees working from outside more than 80 percent of its employees working from outside the company’s offices (39 offices across 21 countries)the company’s offices (39 offices across 21 countries)

Legacy Exchange 2003 EnvironmentLegacy Exchange 2003 Environmentat Avanadeat Avanade

3 sites with Exchange 3 sites with Exchange mailbox serversmailbox servers

11 Exchange servers11 Exchange servers99.99% availability goal99.99% availability goal

Exchange Environment OverviewExchange Environment Overviewat Microsoftat Microsoft

Multiple Exchange organizationsMultiple Exchange organizations~100 legacy Exchange 2003 servers / 30 mailbox servers ~100 legacy Exchange 2003 servers / 30 mailbox servers ~64 Exchange 2007 mailbox servers running in the Corp ~64 Exchange 2007 mailbox servers running in the Corp forestforest

Mailboxes – 130,000+ Mailboxes – 130,000+ Maximum message size = 10 MBMaximum message size = 10 MBAvailability Goal – 99.99%Availability Goal – 99.99%

Mailbox size on Exchange 2003 = 200 MB Mailbox size on Exchange 2003 = 200 MB Mailbox sizes on Exchange 2007 = 500 MB and 2 GBMailbox sizes on Exchange 2007 = 500 MB and 2 GB

Legacy Exchange 2003 EnvironmentLegacy Exchange 2003 Environmentat Microsoftat Microsoft

4 sites with Exchange 4 sites with Exchange mailbox serversmailbox servers

100 Exchange servers/30 100 Exchange servers/30 mailbox servers mailbox servers (clustered)(clustered)

4000x200MB per cluster 4000x200MB per cluster nodenode

99.99% availability goal99.99% availability goal

Goals of Exchange 2007 DeploymentGoals of Exchange 2007 Deploymentat Microsoftat Microsoft

Overcome scalability limitations of 32-bit platformOvercome scalability limitations of 32-bit platformMaintain 99.99% availability goalMaintain 99.99% availability goalIncrease the user mailbox size from 200MB to 500MB Increase the user mailbox size from 200MB to 500MB and 2GBand 2GBReduce hardware, storage, and backup costsReduce hardware, storage, and backup costsEstablish mailbox server resilience from storage level Establish mailbox server resilience from storage level failuresfailuresEstablish flexible and scalable middle-tier services Establish flexible and scalable middle-tier services (e.g. Client Access, Transport)(e.g. Client Access, Transport)

Legacy Exchange 2003 EnvironmentLegacy Exchange 2003 Environmentat Microsoftat Microsoft

RGCRGC

RGCRGCRGCRGC

Exchange 2007 Environment Exchange 2007 Environment at Microsoftat Microsoft

DublinDublin

SingaporeSingapore

Sao PauloSao Paulo

RedmondRedmond

Redmond-Redmond-ExchangeExchange

AD Site LinkAD Site LinkCustom Site LinkCustom Site LinkExchangeCost=10ExchangeCost=10ADCost=999ADCost=999

Exchange Exchange RoutingRouting

Goals of Exchange 2007 DeploymentGoals of Exchange 2007 Deploymentat Avanadeat Avanade

Improved fault tolerance, using Continuous Clustered Improved fault tolerance, using Continuous Clustered Replication (CCR)Replication (CCR)Increased user mailbox size to 500MB with lower cost Increased user mailbox size to 500MB with lower cost disk systems (direct attached drives vs. SAN storage)disk systems (direct attached drives vs. SAN storage)Near-real time backup with Data Protection Manager Near-real time backup with Data Protection Manager (DPM) v2 (DPM) v2 Improved security by moving most messaging servers Improved security by moving most messaging servers behind the corporate firewall (only Edge servers are behind the corporate firewall (only Edge servers are internet facing)internet facing)Consolidate Exchange mailbox servers / datacentersConsolidate Exchange mailbox servers / datacenters

Legacy Exchange 2003 EnvironmentLegacy Exchange 2003 Environmentat Avanadeat Avanade

RGCRGC

RGCRGC

Exchange 2007 Environment Exchange 2007 Environment at Avanadeat Avanade

AMERICASAMERICAS

Seattle-Seattle-ExchangeExchange

AD Site LinkAD Site Link

EMEAEMEA

APACAPAC

Exchange Server RolesExchange Server RolesA quick reminderA quick reminder

Exchange 2000 / 2003Exchange 2000 / 2003Only two rolesOnly two roles

Exchange Front-End ServerExchange Front-End ServerExchange Back-End ServerExchange Back-End Server

No ”real” gateway serverNo ”real” gateway serverUse third-party or IIS SMTP serverUse third-party or IIS SMTP server

Exchange Server 2007Exchange Server 2007Functionality implemented by 5 Server RolesFunctionality implemented by 5 Server Roles

Edge Transport Server Role (Edge)Edge Transport Server Role (Edge)Hub Transport Server Role (Hub)Hub Transport Server Role (Hub)Client Access Server Role (CAS)Client Access Server Role (CAS)Mailbox Server Role (MB)Mailbox Server Role (MB)Unified Messaging Server Role (UM)Unified Messaging Server Role (UM)

Enterprise networkOtherOther

SMTPSMTPServerServer

ss

Mailbox

Mailbox

Routing Hygiene Routin

g Policy

Voice Messagi

ng

Client Access

PBX or

VoIP

PublicFolder

s

Fax

Applications:OWA

Protocols:ActiveSync, POP, IMAP, RPC / HTTP

…Programmability:

Web services, Web parts

Unified Messaging

EdgeTransport

HubTransport

IINNTTEERRNNEETT

Exchange 2007 Enterprise TopologyExchange 2007 Enterprise Topology

Exchange Failover Clusters Exchange Failover Clusters Exchange Server 2003Exchange Server 2003

Requires shared storageRequires shared storageSingle copy of mailbox dataSingle copy of mailbox dataTransport, OWA, and Mailbox cluster awareTransport, OWA, and Mailbox cluster awareUp to 8 node active/passiveUp to 8 node active/passive2 Node active/active2 Node active/active

Exchange Server 2007 (Single Copy Cluster)Exchange Server 2007 (Single Copy Cluster)Requires shared storageRequires shared storageSingle copy of mailbox dataSingle copy of mailbox dataMailbox OnlyMailbox OnlySimple redundancy for Edge, Hub, Client Access, and UMSimple redundancy for Edge, Hub, Client Access, and UMUp to 8 node active/passive – Active/active cut!Up to 8 node active/passive – Active/active cut!Improvements in: Install, Management, BehaviorImprovements in: Install, Management, Behavior

Q

DB

Logs

SMTSMTPPMBMBOWAOWA

DB

Q

Logs

MBMB

Single Copy (failover) ClusterSingle Copy (failover) ClusterDrawbacksDrawbacks

Lacks full redundancyLacks full redundancyQuorum and Exchange levelsQuorum and Exchange levels

Deployment and operational complexity Deployment and operational complexity CostCostRecovery time after corruption or data failure varies Recovery time after corruption or data failure varies based on backup technologybased on backup technologyTwo datacenter solution (geo-cluster) requires Two datacenter solution (geo-cluster) requires integration of partner technologyintegration of partner technology

DB

Q

Logs

MB

Cluster Continuous Replication Cluster Continuous Replication For high availabilityFor high availability

Two node clusterTwo node clusterWitness on Hub TransportWitness on Hub TransportConfigurable heartbeat retriesConfigurable heartbeat retriesTwo copiesTwo copiesClusteredClusteredAutomatic recoveryAutomatic recoveryServer HCLServer HCLFull redundancy (!)Full redundancy (!)ReplayReplay1 or 2 datacenters1 or 2 datacenters

Q Q

q

DB

DB

Log

s

Log

s

FileShare

KB 921181

Benefits of CCRBenefits of CCR

Fast recovery to data problems on active nodeFast recovery to data problems on active nodeNo single point of failureNo single point of failure

More flexibility in hardware selectionMore flexibility in hardware selectionDirect Attached StorageDirect Attached Storage

No cluster validationNo cluster validationSimplified storage requirementsSimplified storage requirementsExchange-provided replication solution Exchange-provided replication solution Enables a single Mailbox server failoverEnables a single Mailbox server failoverto second data centerto second data centerSimplified deploymentSimplified deploymentImproved management experienceImproved management experienceAbility to offload workloadAbility to offload workload

Exchange 2007 Server Roles Exchange 2007 Server Roles at Avanade and Microsoftat Avanade and MicrosoftIn Exchange Server 2003 timeframe Microsoft IT and Avanade In Exchange Server 2003 timeframe Microsoft IT and Avanade ITS deployed servers roles dedicated for specific functionsITS deployed servers roles dedicated for specific functionsExchange Server 2007 deployment – similar approachExchange Server 2007 deployment – similar approachStructured system Structured system administration andadministration andmaintenancemaintenanceOptimized hardware andOptimized hardware andsoftware configurationsoftware configurationTargeted load balancingTargeted load balancingand fault toleranceand fault toleranceFlexible scaling approachFlexible scaling approach

Hub Transport ServersEdge Transport Servers

Client Access Servers

Clustered Mailbox Servers

Unified Messaging Servers

Inte

rnet

Limitations of 32-bit Exchange platformLimitations of 32-bit Exchange platformGeneral informationGeneral informationScalability limitationsScalability limitations

Virtual memory is limited to 4GB. Exchange Virtual memory is limited to 4GB. Exchange Server 2003 can use up to 3GB maxServer 2003 can use up to 3GB maxPaged Pool (256MB max with /3GB)Paged Pool (256MB max with /3GB)

Client connections, Access tokensClient connections, Access tokensNon Paged Pool (256MB max without /3GB and Non Paged Pool (256MB max without /3GB and 128MB max with /3GB)128MB max with /3GB)

HTTPs and TCP connections to the Exchange Front HTTPs and TCP connections to the Exchange Front End or GatewayEnd or Gateway

Performance limitationsPerformance limitationsSmall DB cache size = high I/O and larger Small DB cache size = high I/O and larger storage demandsstorage demands

Exchange 2007 Hardware ConfigurationsExchange 2007 Hardware Configurationsat Avanade and Microsoftat Avanade and Microsoft

RoleRole ConfigurationConfigurationBHD/EdgeBHD/Edge 4x2.2/3.0 GHz (MS/Ava) CPU*, 8GB RAM 4x2.2/3.0 GHz (MS/Ava) CPU*, 8GB RAM

CASCAS 4x2.2/3.0 GHz (MS/Ava) CPU*, 4GB RAM 4x2.2/3.0 GHz (MS/Ava) CPU*, 4GB RAM

UMUM 2x2.2 GHz CPU*, 4GB RAM (MS only)2x2.2 GHz CPU*, 4GB RAM (MS only)

MBX 2000 @ 500MB (CCR)MBX 2000 @ 500MB (CCR) 4x2.6 GHz CPU*, 12GB RAM (MS only)4x2.6 GHz CPU*, 12GB RAM (MS only)

MBX 2400 @ 2GB (CCR)MBX 2400 @ 2GB (CCR) 4x3.0 GHz CPU*, 16GB RAM (MS only)4x3.0 GHz CPU*, 16GB RAM (MS only)

MBX 3600 @ 2GB (CCR)MBX 3600 @ 2GB (CCR) 8x2.6 GHz CPU*, 24GB RAM (MS only)8x2.6 GHz CPU*, 24GB RAM (MS only)

MBX 4000 @ 500MB (CCR)MBX 4000 @ 500MB (CCR) 8x3.0 GHz CPU*, 16GB RAM (Avanade only)8x3.0 GHz CPU*, 16GB RAM (Avanade only)

* 4 way = 2 Dual Core CPUs

How to determine your capacity needHow to determine your capacity needHardware designHardware designDatabaseDatabase

14 day dumpster ~15% overhead [MSIT profile]14 day dumpster ~15% overhead [MSIT profile]5% Content Indexing overhead5% Content Indexing overhead~10% overhead for whitespace in the database~10% overhead for whitespace in the database

ExampleExample1000 User @ 250MB per mailbox1000 User @ 250MB per mailbox = 250 GB= 250 GBDumpster:Dumpster: 15% of 250 GB15% of 250 GB = 37.5= 37.5Content Indexing:Content Indexing: 5% of 250 GB5% of 250 GB = 12.5= 12.5Whitespace:Whitespace: 10% of 250 GB10% of 250 GB = 25= 25Total Total = 325 GB= 325 GB

In number of spindles (hard disks) required excluding raid:In number of spindles (hard disks) required excluding raid:Minimum 3 (2,5) spindles @ 144 GBMinimum 3 (2,5) spindles @ 144 GB

How to determine IOPS needHow to determine IOPS needHardware design – Exchange 2003Hardware design – Exchange 2003Exchange 2003 averages 3:1 Read Write ratioExchange 2003 averages 3:1 Read Write ratio

@ 400 IO (300 Read IO and 100 Write IO)@ 400 IO (300 Read IO and 100 Write IO)Raid 10 = 300*1 + 100*2 = 500 IO generatedRaid 10 = 300*1 + 100*2 = 500 IO generatedRaid 5 = 300*1 + 100*4 = 700 IO generatedRaid 5 = 300*1 + 100*4 = 700 IO generated

15K SCSI = 180 IOPS15K SCSI = 180 IOPS15K SCSI Raid 10 = 400 / 500 * 180 = 144 effective IOPS15K SCSI Raid 10 = 400 / 500 * 180 = 144 effective IOPS15K SCSI Raid 5 = 400 / 700 * 180 = 103 effective IOPS15K SCSI Raid 5 = 400 / 700 * 180 = 103 effective IOPS


How to determine IOPS in RaidHow to determine IOPS in RaidHardware design – Exchange 2007Hardware design – Exchange 2007Exchange 2007 averages 1:1 Read Write ratioExchange 2007 averages 1:1 Read Write ratio

@ 400 IO (200 Read IO and 200 Write IO)@ 400 IO (200 Read IO and 200 Write IO)Raid 1 = 200*1 + 200*2 = 600 IO generatedRaid 1 = 200*1 + 200*2 = 600 IO generatedRaid 5 = 200*1 + 200*4 = 1000 IO generatedRaid 5 = 200*1 + 200*4 = 1000 IO generated



How to determine your IOPSHow to determine your IOPSExchange 2003 exampleExchange 2003 example

1000 users @ 1.0 IO requires 1000 IOPS1000 users @ 1.0 IO requires 1000 IOPS15K Raid 10 = 1000 IOPS / 144 = 6,915K Raid 10 = 1000 IOPS / 144 = 6,9Rounded up to 8 spindlesRounded up to 8 spindles

15K Raid 5 = 1000 IOPS / 103 = 9,715K Raid 5 = 1000 IOPS / 103 = 9,7Rounded up to 10 spindlesRounded up to 10 spindles

Note: We need more spindles with Raid 5 than with Raid 10Note: We need more spindles with Raid 5 than with Raid 10

Raid 10 is the most effective (in this example)Raid 10 is the most effective (in this example)8 spindles @ 144 GB = 576 GB – we only needed 325GB!8 spindles @ 144 GB = 576 GB – we only needed 325GB!

Conclusion: Exchange 2003 is IO boundConclusion: Exchange 2003 is IO bound

How to determine your IOPSHow to determine your IOPSExchange 2007Exchange 20071000 users @ 0.3 IO requires 300 IOPS1000 users @ 0.3 IO requires 300 IOPS



Note: We need again more spindles with Raid 5 than with Raid 10Note: We need again more spindles with Raid 5 than with Raid 10

4 spindles @ 144 GB = 288 GB – 37 GB less than we 4 spindles @ 144 GB = 288 GB – 37 GB less than we needed!needed!

Conclusion: Exchange 2007 is capacity boundConclusion: Exchange 2007 is capacity bound

How to determine your storage needsHow to determine your storage needsSummarySummaryConclusion: Exchange 2007 design is capacity boundConclusion: Exchange 2007 design is capacity bound

Exchange 2003 is IO boundExchange 2003 is IO bound

IOPS is a storage group database’s I/Os divided by the number IOPS is a storage group database’s I/Os divided by the number of users in the storage group.of users in the storage group.

Once you have an Exchange 2003 baseline, apply Exchange Once you have an Exchange 2003 baseline, apply Exchange 2007 factors2007 factors

~70% IOPS reduction~70% IOPS reductionIncrease DB read reduction adding more RAMIncrease DB read reduction adding more RAM

To calculate your storage use the To calculate your storage use the Exchange 2007 Mailbox Exchange 2007 Mailbox Server Role Storage Requirements Calculator Server Role Storage Requirements Calculator

http://msexchangeteam.com/archive/2007/01/15/432207.aspxhttp://msexchangeteam.com/archive/2007/01/15/432207.aspx

Exchange 2007 Mailbox Server Exchange 2007 Mailbox Server Microsoft IT: Universal Storage Building BlockMicrosoft IT: Universal Storage Building Block

Approach:Approach:Two disk enclosuresTwo disk enclosuresCross-shelf mirroring [RAID 1+0]Cross-shelf mirroring [RAID 1+0]

LUN Capacity:LUN Capacity:600 mailboxes = 12 disks [RAID 1+0]600 mailboxes = 12 disks [RAID 1+0]7 Storage Groups/Databases7 Storage Groups/DatabasesSingle Logical DriveSingle Logical Drive

Two Database LUNs totalTwo Database LUNs total1,200 x 2GB mailboxes1,200 x 2GB mailboxes

One Log LUNOne Log LUN2 logical volumes (L:\ + M:\)2 logical volumes (L:\ + M:\)825GB of log space825GB of log space

30 x 300GB drives30 x 300GB drives24 for databases24 for databases6 for transaction logs6 for transaction logsData:Log – 4:1Data:Log – 4:1

1

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

Encl

osur

e 1

2 3 4 5 6 7 8 9 10 11 12 13 14 15

Encl

osur

e 2

DATA1 (E:\)RAID 1+01650GB

DATA2 (F:\)RAID 1+01650GB

LOG (L:\+M:\)RAID1+02x400GB

Goal: Design simple and scalable storage building blockGoal: Design simple and scalable storage building block

Exchange Server Backup SolutionExchange Server Backup Solutionat Microsoftat Microsoft

Passive NodeActive Node

SAS

Log Shipping

SAS SAS SASSAS

Backup Storage

BACKUP

Database Storage Replica Storage

Streaming Backup Schedule Streaming Backup Schedule at Microsoftat Microsoft

SG1

Mon Tue Wed Thu Fri Sat Sun

SG2

SG3

SG4

SG5

SG6

SG7

Full

Full

Full

Full

Full

Full

Full

Inc Inc Inc Inc Inc Inc

Inc Inc Inc Inc Inc

Inc Inc Inc Inc Inc

Inc Inc Inc Inc

Inc Inc Inc Inc

Inc Inc IncInc Inc Inc

Inc Inc

Inc Inc

Inc

Inc

Inc Inc Inc Inc Inc Inc

6-9TB of data to backup per server6-9TB of data to backup per serverStreaming backup schedule:Streaming backup schedule:Full Backup – weekly for each DBFull Backup – weekly for each DBIncremental – daily for each DBIncremental – daily for each DBBackup from active node onlyBackup from active node only

Backups from PassiveBackups from Passiveat Avanade and Microsoftat Avanade and MicrosoftBacking up the passive moves the performance hit off the Backing up the passive moves the performance hit off the activeactiveNeed to produce a backup which can be restored to the activeNeed to produce a backup which can be restored to the activeShould be identical to a backup from the activeShould be identical to a backup from the activeWant to backup the active or the passiveWant to backup the active or the passiveRemember, they can change designationsRemember, they can change designationsVSS onlyVSS only

Replication service coordinates backups with the storeReplication service coordinates backups with the storeReplication service contacts the store at the start/end of backupReplication service contacts the store at the start/end of backupCannot backup if the store is downCannot backup if the store is downAt the end of a backup the store modifies the database, At the end of a backup the store modifies the database, generating a log recordgenerating a log recordWhen the replication service replays the log record the When the replication service replays the log record the database header is updateddatabase header is updated

Data Protection Manager (DPM) v2 (beta)Data Protection Manager (DPM) v2 (beta) at Avanade and Microsoft at Avanade and Microsoft

Passive Node4 x 3.0GHz16GB RAM

Active Node4 x 3.0GHz16GB RAM

SAS







DPM HOST4 x 3.0GHz4GB RAM

1GigE

1GigE

1GigE

1GigE

DPM Agent

DPM Agent

DPM Agent

DPM AgentDPM Agent

DPM Agent

DPM Agent

DPM Agent

Data Protection Manager (DPM) v2Data Protection Manager (DPM) v2 at Avanade and Microsoft at Avanade and MicrosoftGoals for DPMGoals for DPM

Run backups on the passive node (use software VSS)Run backups on the passive node (use software VSS)Reduce backup timeReduce backup timeReduce recovery time and complexityReduce recovery time and complexityIncrease the backup frequencyIncrease the backup frequencyAchieve point in time recovery (recover data for the given time point)Achieve point in time recovery (recover data for the given time point)Capitalize on ability of DPM to produce full backups by copying only Capitalize on ability of DPM to produce full backups by copying only changed disk blockschanged disk blocks

Anticipate to backup up to 10K mailboxes per DPM server.Anticipate to backup up to 10K mailboxes per DPM server.

DPMv2 backup schedule:DPMv2 backup schedule:Optimized full backup daily at midnightOptimized full backup daily at midnightIncremental – every 15 minutesIncremental – every 15 minutesRecovery only on active node – hence DPM agent on active LinkRecovery only on active node – hence DPM agent on active Link

Mobile Messaging Topology Mobile Messaging Topology at Microsoftat Microsoft

Exchange 2007CAS Servers

ISA Server2006

Exchange 2007 Mailbox Servers


ISA Server2006



ISA Server2006


Dublin:-ExternalURL “https://emeamsg.microsoft.com/...”

Singapore:-ExternalURL “https://apsmsg.microsoft.com/...”

Sao Paulo:-ExternalURL “https://spamsg.microsoft.com/...”

Redmond:-ExternalURL “https://msg.microsoft.com/...”Autodiscover Service URL “https://autodiscover.microsoft.com/autodiscover”


ISA Server2006


Internet

Mobile Messaging Design Mobile Messaging Design at Microsoftat Microsoft

ISA02

ISA03

CAS-02

CAS-03

Externally trustedSSL Certificate

msg.microsoft.com

CAS-01ISA01

Exchange RPC

Exchange 2007 CAS Servers

RPC Proxy

RPC Proxy

RPC Proxy

ISA 2006Array

Internally trustedSSL Certificate

msg.microsoft.com

LOA

D B

ALA

NC

ING

(single affinity)

SSL

External users Internal usersSSL

LOA

D B

ALA

NC

ING

(single affinity)

Exchange 2007Mailbox Servers

Published Paths/exchange/*

/owa/*

/public/*

/Microsoft-Server-ActiveSync/*

/RPC/*

/Autodiscover/*

/EWS/*

/UnifiedMessaging/*

Cookie-based load

balancing

IP-based load

balancing

The Exchange front-end servers are part of a Web farm pointed to by an ISA Server 2006 array

CONNECTIVITY VERIFIERS

Mobile Messaging Design Mobile Messaging Design at Microsoftat Microsoft

Connection/Sender/Recipient FilteringRecipient LookupAntispamAttachment managementAntivirus

Perimeter Forest

Exchange 2007 Mailbox servers

MOMExchange 2007 HUB servers

Corp Forest

DC / GC

Internet

DC / GC

SMS MOM

Port 25 (SMTP)

Port 25 (SMTP)Port 53 (DNS)Port 80 (AV Signature Updates) Port 25 (SMTP)

Port 3389 (Terminal Services)Port 50389/50636 (EdgeSync)

Active Directory Forest in Perimeter Network - Non corporate AD joined OR trusted

Port 25 (SMTP)

Exchange 2007 Edge Servers

Region 1

Region 2

The resultsThe resultsLower storage costsLower storage costsEliminate tape backupsEliminate tape backupsCompliance with legal and regulatory requirements Compliance with legal and regulatory requirements Improved messaging protection Improved messaging protection Establishment of foundation for new SLAs Establishment of foundation for new SLAs Simplified operational tasks Simplified operational tasks Demonstrated confidence in the productDemonstrated confidence in the product

Case studiesCase studiesHow Microsoft does IT: Showcase | ExchangeHow Microsoft does IT: Showcase | Exchange

http://www.microsoft.com/technet/itshowcase/exchange.mspxAvanade Maximizes Advantage with Desktop, Business Productivity Avanade Maximizes Advantage with Desktop, Business Productivity Infrastructure UpgradesInfrastructure Upgrades

http://www.microsoft.com/casestudies/casestudy.aspx?casestudyid=200067Relevant linksRelevant links

Exchange Team blogExchange Team bloghttp://msexchangeteam.com/default.aspx

BenefitsBenefits

http://www.microsoft.com/technet/itshowcase/exchange.mspx

http://www.microsoft.com/casestudies/casestudy.aspx?casestudyid=200067

http://msexchangeteam.com/default.aspx

exchange 2007 - erfaring fra feltet, bernt lervik

Technology