EMC makes Exchange 2010 Better!!

1© Copyright 2010 EMC Corporation. All rights reserved.

EMC makes Exchange 2010 Better!!

Optimizing Exchange 2010 while driving out cost and complexity.


Microsoft adds new Features & FunctionsExchange 2010 has evolved, even since RTM…

• Reduce TCO by– Allowing use of SATA drives, JBOD, DAS– Increase mailbox sizes, increase speed,

facilitate Legal Hold– Eliminate need for third-party journaling,

archiving, & search• Enable Cloud/Private Cloud

– Support for Virtualization– Open support for SAN/iSCSI/FCoE…– Open reality check on JBOD usage– Support for more DAG-Replication

scenarios


What are your concerns as you move to Exchange 2010?• Server virtualization

– Microsoft used to discourage it, but it’s widely successful– I love VMware, should I like Hyper-V too?

• Storage – DAS vs Array– I need 2TB to finish the migration; can I add more space later?– What’s wrong with my SAN?!

• High Availability– How many copies should I have?!– How many servers should I deploy

• Backup and Recovery — system, databases, items– If I have three copies, do I need to back it up?!– What if I use NearPoint? How does that affect my HA,BR,DR plans

• Disaster Recovery– Oy.– Can I have one remote copy and make it part of the Active DAG?– Can I have Active databases at both sites?


EMC makes Exchange 2010 Better!How can EMC drive costs out while adding…• Control

– I want to control my own servers, storage, network, and OS’s– I don’t care how many servers I need, but I need to patch them…

• Capacity– Microsoft tells me to allocate for three years, what if I’m wrong?!– Why do I need SIX bloody times the space of my 2003 SCC implementation?!

• Flexibility– Can I add servers to the DAG as I add users, capacity?– Can I take servers away? Can I add servers to the DR site to handle load?

• Performance– I don’t need to worry about performance any more… RIGHT?!– My boss will let me overbuild this, but how much is too much, what’s enough?

• Functionality– Boy I wish I could provide Legal Search to our Legal Counsel– How do I handle rolling corruption? That’s not going to happen RIGHT?!


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

2009 - Exchange DAG Overview Microsoft Confidential -- Ross Smith IV

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

DB1Database centric failover

Exchange DAG Overview


Store • FAST VP: Dynamic Provisioning, Dynamic Performance

• VSI: Storage creation and monitoring

Protect • Integrated-Block-Level CRC:• Proactive Hot-Sparing:• Snapshots & Reserve LUN Pool

Replicate• RecoverPoint/REE for DAG-integrated

*over• RecoverPoint/CE for Cloud-failover• SRDF/CE for VMAX Cloud-failover

Optimize• Automated Storage Tiering• Storage/Virtualization Integration• Bandwidth-Reducing Replication• IO-Reducing Data-protection

Four-pronged ApproachVisionary Thought Leadership redefines lowest possible TCO


Virtual LUN

RP-Journal


Virtual LUN

RP-Journal

Exchange 2010 – the EMC WayOptimized – Infrastructure, WAN, Storage, Backup

EMC’s Unified, Lower Cost, More Capable Solution for Exchange 2010• Fewer

• Physical Servers, • OS & Application licenses, • OS & Application installations• Database copies

• Increased• Data protection• Item-level recovery• Mailbox sizes

• Simplified• Day-to-day management• Patch management• Site-to-site failover

• Lower• Cost of initial deployment• Cost of growth• Cost of management

Exchange 2010 – the EMC Way


Store:Exchange 2010 Brings:• Contiguous Mailboxes• Removal of SIS• Concatenated Mailboxes• Compression of HTML• Background Database

Maintenance (BDM)• 64KB and 256KB disk

operations• 100MB Checkpoint

Cache


E2K10: Store Table Architecture

E2007

Message/Folder Table (MFT)

Joe:Inbox:H3

Joe:Inbox:H2

Joe:Inbox:H1

Per Database Per Folder

Mailbox Table

Jeff’s Mbx

Ann’s Mbx

Joe’s Mbx

Attachments Table

Jeff:Excel.xls

Ann:Pic.bmp

Joe:Help.doc

Message Table (Msg)

Joe:Msg10

Jeff:Msg32

Ann:Msg180

Folders Table

Jeff:Inbox

Ann:Drafts

Joe:Unread

E2010

View Tables (e.g. From)

Joe:H920

Joe:H302

Joe:H10

Secondary Indexes used for Views

Per Mailbox

Mailbox Table

Jeff’s Mbx

Ann’s Mbx

Joe’s Mbx

Body

Joe:Msg10

Joe:Help.doc

Joe:Msg302

Message Header Table

Joe:H10

Joe:H302

Joe:H920

Folders Table

Joe:Inbox

Joe:Drafts

Joe:Unread

Per Database

New Store Schema = no more single instance storage within a DB

Per View

Source: Matt Gossage, Microsoft Sr. Program Manager


E2K10: Logical Contiguity

E2007

E2010

Many, small size, IOs

Fewer, large size, IOs

Inbox

M1

Calendar

M3

Drafts

M5

For Follow-up

M4

DL Mail

M2

MailboxDL Mail M1Calendar M2Drafts M3For Follow-up M4Inbox M5

Mailbox

Random

Sequential

Source: Matt Gossage, Microsoft Sr. Program Manager


Store:Exchange 2010 Brings:• Contiguous Mailboxes• Removal of SIS• Concatenated Mailboxes• Compression of HTML• Background Database

Maintenance (BDM)• 64KB and 256KB disk

operations• 100MB Checkpoint

Cache

EMC makes Exchange Better:• Capacity as needed• Higher density storage• Cache pre-fetching• Automated storage tiering• Storage Processors built

for high bandwidth operations

• Storage Pools ideally suited for consolidated queue operations


Store:Microsoft “Best Practices”• Pre-allocate all storage

on “day one” and add best guess for growth

• Store 3 copies of mailboxes, reseed often – develop operational excellence

• Replicate mail at least twice over the WAN

• Reseed after remote site backup

EMC makes Exchange Better• Allocate storage to complete

migration – add storage based on trends

• Let the array Protect the data: – Store one copy of mail,– Use disks for storing more mail,

not copying the mail– No “BINGO Sheet talent”

required• Replicate mail once:

– Optimize WAN utilization by using 1/3rd the bandwidth

– Optimize use of remote site for HA, DR, and BC

– Optimize replication by avoiding reseeds


Store:Microsoft allocation method• Measure mail from

source platform – based on Profiler

• Calculate required storage for concatenated mailboxes

• Guess growth requirements

EMC makes Exchange Better• Measure mail in source

platform, calculate SIS ratio

• Design storage to absorb migrated mail

• Collect trend data, plan for storage increases

1.7X

Add 0.5X in 1yr


Store: Storage Pools• Optimize disk usage:

mix different drive types (Drive mix user selected)

• Recommended Ratio: SSD:SAS:SATA ~ 5%:20%:75%

• Protect with RAID5, RAID6, RAID1/0, or even RAID 0!

• Storage Pools are expanded dynamically

• Add SSDs for more performance

• Add SATA for more capacity•Thick or Thin Provision

• LUNs are expandable• LUNs can be migrated on-the-

fly


Store: FAST VP: Automated Performance Tuning for Exchange Databases

Flash–10%

Fibre Channel–40%

SATA–50%

Flash–10%

NL-SAS–90%

Traditional FAST(Volume/LUN

level)FAST VP

(Sub-LUN)No need for• Policies, • Personal Archive

Folders, • Moving users from dB to

dBAdd storage based on

• Capacity needs• Performance

needs

DONE!


Store: EMC Storage Integrator (ESI) Providing Simplified Management for Windows Hosts • Storage provisioning

for Windows Servers• Application-aware

storage provisioning• Windows MMC based• Agent-less architecture• Supports VMAX, VNX,

VNXe, CX4, and NS series

– Block and file supportEasy-to-use MMC Snap-ins for the Server/Application Admin


Store: DEMOView your Exchange storage from the tools you know


Protect: Exchange 2010 Brings:• CRC-level checking in

three-copy DAG via BDM• DAG-Replication creates

“secondary failure domains”

• Store Schema, DAG-R and BDM allows use of “cheap storage”


Protect: Exchange 2010 “outage-mitigation technologies”:• Background Database

Maintenance– 256KB blocks

continuously scanned and inspected for “page tears”

– Page-level reordering to continuously defrag dB

– Insertion of additional white-space to enhance dB efficiency, sequentially

• Secondary dB copies updated via Log Shipping

– Data commit-based replication to avoid rolling corruption

– Lagged copy option allows recovery to previous points-in-time


Protect: Exchange 2010 Brings:• CRC-level checking in

three-copy DAG via BDM• DAG-Replication creates

“secondary failure domains”

• Store Schema, DAG-R and BDM allows use of “cheep storage”

EMC makes Exchange Better:• Integrated block-level

CRC offloads all data integrity checks

• Proactive hot sparing allows designers to cancel-out RAID-rebuilds

• Rebuild logging prevents *over events by keeping volumes online

• UltraPoint


True or False:• Two copies of a SQL

database linked by log-shipping

• Two copies of Exchange dBs replicated with HW VSS

• A single Exchange dB and an indexed Journal of all it’s mail

True or False:• Two copies of a SQL

database replicated synchronously

• Three copies of Exchange dBs replicated with DAG-Replication

• A single Exchange dB and an archive with 75% of the mail “stubbed” from the dB

…a logical/physical boundary between systems

What the heck is a “failure domain”?!

FALSE!

TRUE!

TRUE, but..!

FALSE!

…sorry, nope…

Not even close!


Store, Protect Exchange 2010Basic – Local High Availability & Local Disaster Recovery

Dynamic Provisioning• Capacity on demand• Dynamic performance

allocation• Rebuild avoidanceSame cost…• Twice the performance• 1/3 the management• Eliminate need for

redundancy duplicates• ½ the capacity requirement• All of the uptime


Consolidated Storage• Single-interface, permissions-

based administration• Simplified management• Centralized service & support• 24x7x365 manufacturer

maintenance• Total system-level redundancySame cost…• Increased mailbox sizes• Increased data protection• Increased Item-Level Recovery• Near-zero maintenance• 99.999% real uptime• 10-year proven solution

Industry Standard Hypervisor• Fewer number of Servers• Facilitates dynamic resource allocation• Reduced or No additional licensing• Assign memory and vCPU as needed• Enables advanced network

architectures• Frees OS from Hardware• Facilitates hardware repurposingSame cost…• Fully supported by Microsoft• No loss of control• No additional management stations

needed

Multiple Direct Attached Storage ArraysVirtual

LUN

Virtual LUN

Snap-shot

Snap-shot

Add secondary failure domains with Array-based Point-in-Time Recovery Points• LUN-level copies taken as often as 4-per hour• Allows point-in-time recovery of entire database• Maintains database locality of referenceSignificantly lower cost compared to additional DAG copies…• Completely automated management (creation and expiration)• Significantly less complex restoration process compared to Lagged DAG

copies• Avoids multi-hour outages related to corruption events• Keep copies for 1-day or up to 1-week


DEMOCreate Point-in-Time copies of Exchange databases in 80% less space with recovery in minutes

Break to follow demonstration…


Replicate: Exchange 2010 Brings:• DAG Technology

– High Availability– Data Protection– Disaster Recovery

• LAN-based log-shipping


Terminology• Active Node – The server or application

instance actively serving a data set• Active Copy – The data set served by

the Active Node• Failover Manager – The process by

which the Active Node is chosen• Replication Engine – The process used

to replicate the Active Copy• Native DAG – Combination of a Failover

Manager (Active Manager) and Replication Engine (Log Replication)


Native DAG

Site 1

DAG Repl Active Physical

Copy

Passive Physical

Copy

Active Member

PassiveMember

FailoverManager

ReplicationEngine

Site 2

Active MgrActive Mgr Active Mgr


Site 2VMHost 3 VMHost 4

Site 1VMHost 1

Virtualized Local DAG

Active Physical

Copy

Passive Physical

Copy

Active Member

PassiveMember

FailoverManager

ReplicationEngine

DAG Repl

VMHost 2

RecoverPointMirrorView

SRDFDAG Repl

SRMPowerShell

ManualActive Mgr Active Mgr


Site 2VMHost 3 VMHost 4

Site 1VMHost 1

Virtual Host Clustering

Active Physical

Copy

Passive Physical

Copy

Active Member

PassiveMember

FailoverManager

ReplicationEngine

VMHost 2

RecoverPointMirrorView

SRDFVPLEX

VMHAHyper-V WFC

SRMCluster Enabler

Manual VMHAHyper-V WFC


Third Party Replication

Site 1

Active Physical

Copy

Passive Physical

Copy

Active Member

PassiveMember

FailoverManager

ReplicationEngine

Site 2

RecoverPoint, SRDF, MV

Active Mgr Active Mgr Active Mgr


Replicate: Exchange 2010 Brings:• DAG Technology


• LAN-based log-shipping

EMC makes Exchange Better:• Additional options for


• Points-in-time data protection

– Managed by Exchange Admins

– Automated operations– Minimal recovery steps


Virtual LUN

Virtual LUN

Virtual LUN


Replicate:Native DAG

Virtual LUN

Virtual LUN

Virtual LUN

Virtual LUN

Leverage Exchange DAG Replication• Take advantage of native tools• Maintain minimum number of databases to

achieve Exchange Native Backup• Add failure domains by using snapshots• Fully Automated DAG-based HA, with

manual or automatic DR failover• Total system-level redundancyFollows Microsoft Guidance, but…• Reduced database copies (3-total, not three on

each side)• Reduced infrastructure (1/2 the servers)• 99.999% real uptime (based on actual

customer data)• Reduced licensing costs


Virtual LUN

RP-Journal

Virtual LUN

RP-Journal

Third-Party Failover and ReplicationReplicate:

Fabric-based Recovery Points• Write-by-write copies journaled to remote

site• Allows point-in-time recovery of entire

database• Maintains database locality of reference• Eliminates LAN replication traffic• Eliminates dedicated replication LAN/vLAN• Reduces WAN bandwidth by 70% over

DAG-replication• Keep minute-by-minute copies for 1-day or

up to 1-month

Deduplicated Replication of Backups• Create backups at remote site• Copy only “deltas” to production site• Run production from DR or DR from

productionPay only for what you store…• Backup as many copies of the database as

you want – messages are stored only once• Never send the same over the wire twice• Dramatic reduction in WAN bandwidth

over competing “solutions”


Virtual LUN

RP-Journal


Virtual LUN

RP-Journal

Replicate: Third-Party Replication, Native Failover

Fabric-based Long-distance Recovery Points• Write-by-write copies journaled to remote

site• Allows point-in-time recovery of entire

database• Maintains database locality of reference• Eliminates LAN replication traffic• Eliminates dedicated replication LAN/vLANSame cost as additional DAG copies…• Fully integrated/automated DAG-

based failover• Reduces WAN bandwidth by 70% over

DAG-replication• Keep minute-by-minute copies for 1-day or

up to 1-month


DEMOSite-to-site automated failover using Replication Enabler for Exchange


Virtual LUN

RP-Journal


Virtual LUN

RP-Journal

EMC makes Exchange Better!Optimized – Infrastructure, WAN, Storage, Backup

• EMC’s Unified, Lower Cost, More Capable Solution for Exchange 2010

• Fewer• Physical Servers, • OS & Application licenses, • OS & Application installations• Database copies

• Increased• Data protection• Item-level recovery• Mailbox sizes

• Simplified• Day-to-day management• Patch management• Site-to-site failover

• Lower• Cost of initial deployment• Cost of growth• Cost of management


THANK YOU

EMC makes Exchange 2010 Better!!

Documents

Transcript of EMC makes Exchange 2010 Better!!