1 / 36

EMC makes Exchange 2010 Better!!

EMC makes Exchange 2010 Better!!. Optimizing Exchange 2010 while driving out cost and complexity. . Microsoft adds new Features & Functions. Exchange 2010 has evolved, even since RTM…. Reduce TCO by Allowing use of SATA drives, JBOD, DAS

knut
Download Presentation

EMC makes Exchange 2010 Better!!

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EMC makes Exchange 2010 Better!! Optimizing Exchange 2010 while driving out cost and complexity.

  2. Microsoft adds new Features & Functions Exchange 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

  3. 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 vsArray • 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?

  4. 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?!

  5. Exchange DAG Overview AD site: Dallas All clients connect via CAS servers Client Access Server DB1 Client DB3 Mailbox Server 6 AD site: San Jose DB5 Client Access Server Easy to stretch across sites Failover managed within Exchange Mailbox Server 1 Mailbox Server 2 Mailbox Server 3 Mailbox Server 4 Mailbox Server 5 Database Availability Group DB1 DB1 DB1 DB4 DB2 DB5 DB3 DB2 DB5 DB3 DB4 DB1 Database centric failover DB3 DB1 DB2 DB5 DB4 2009 - Exchange DAG Overview Microsoft Confidential -- Ross Smith IV

  6. Four-pronged ApproachVisionary Thought Leadership redefines lowest possible TCO

  7. Flash Flash Fibre Channel Fibre Channel SATA SATA Exchange 2010 – the EMC Way Exchange 2010 – the EMC Way Database Availability Group 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 Virtual LUN Virtual LUN RP-Journal RP-Journal

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

  9. E2K10: Store Table Architecture Per Database Per Folder E2007 Secondary Indexes used for Views Per Mailbox Per Database Per View E2010 New Store Schema = no more single instance storage within a DB Source: Matt Gossage, Microsoft Sr. Program Manager

  10. E2K10: Logical Contiguity Mailbox E2007 Many, small size, IOs Random E2010 Sequential Fewer, large size, IOs Source: Matt Gossage, Microsoft Sr. Program Manager

  11. Store: Exchange 2010 Brings: 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 • Contiguous Mailboxes • Removal of SIS • Concatenated Mailboxes • Compression of HTML • Background Database Maintenance (BDM) • 64KB and 256KB disk operations • 100MB Checkpoint Cache

  12. Store: Microsoft “Best Practices” 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 • 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

  13. Store: Microsoft allocation method 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 • Measure mail from source platform – based on Profiler • Calculate required storage for concatenated mailboxes • Guess growth requirements 1.7X Add 0.5X in 1yr

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

  15. Store: FAST VP: Automated Performance Tuning for Exchange Databases Traditional FAST (Volume/LUN level) FAST VP (Sub-LUN) • No need for • Policies, • Personal Archive Folders, • Moving users from dB to dB • Add storage based on • Capacity needs • Performance needs • DONE! Flash–10% NL-SAS–90% Flash–10% Fibre Channel–40% SATA–50%

  16. 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 support Easy-to-use MMC Snap-ins for the Server/Application Admin

  17. Store: DEMO View your Exchange storage from the tools you know

  18. 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”

  19. Protect: Exchange 2010 “outage-mitigation technologies”: 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 • 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

  20. Protect: Exchange 2010 Brings: 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 • 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”

  21. What the heck is a “failure domain”?! True or False: 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 • 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 FALSE! FALSE! …sorry, nope… TRUE! TRUE, but..! Not even close!

  22. Flash Fibre Channel SATA Store, Protect Exchange 2010 Database Availability Group Basic – Local High Availability & Local Disaster Recovery • 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 repurposing • Same cost… • Fully supported by Microsoft • No loss of control • No additional management stations needed Snap-shot Virtual LUN Multiple Direct Attached Storage Arrays • Dynamic Provisioning • Capacity on demand • Dynamic performance allocation • Rebuild avoidance • Same 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 redundancy • Same cost… • Increased mailbox sizes • Increased data protection • Increased Item-Level Recovery • Near-zero maintenance • 99.999% real uptime • 10-year proven solution • 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 reference • Significantly 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 Snap-shot Virtual LUN

  23. DEMO Create Point-in-Time copies of Exchange databases in 80% less space with recovery in minutes Break to follow demonstration…

  24. Replicate: Exchange 2010 Brings: • DAG Technology • High Availability • Data Protection • Disaster Recovery • LAN-based log-shipping

  25. 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)

  26. Native DAG Failover Manager Replication Engine Site 1 Site 2 PASSIVE Active Member Active Mgr Active Mgr Active Mgr Passive Member DAG Repl Active Physical Copy Passive Physical Copy

  27. Virtualized Local DAG Failover Manager Site 1 Site 2 STANDBY Replication Engine Active Member SRM PowerShell Manual VMHost 1 VMHost 2 VMHost1 VMHost 2 Active Mgr Active Mgr Passive Member RecoverPoint MirrorView SRDF DAG Repl DAG Repl Active Physical Copy Passive Physical Copy

  28. Virtual Host Clustering Failover Manager Site 1 Site 2 STANDBY Replication Engine Active Member SRM Cluster Enabler Manual VMHost 1 VMHost 2 VMHost1 VMHost2 VMHA Hyper-V WFC VMHA Hyper-V WFC Passive Member RecoverPoint MirrorView SRDF VPLEX Active Physical Copy Passive Physical Copy

  29. Third Party Replication Failover Manager Replication Engine Site 1 Site 2 PASSIVE Active Member Active Mgr Active Mgr Active Mgr Passive Member RecoverPoint, SRDF, MV Active Physical Copy Passive Physical Copy

  30. Replicate: Exchange 2010 Brings: EMC makes Exchange Better: Additional options for High Availability Data Protection Disaster Recovery Points-in-time data protection Managed by Exchange Admins Automated operations Minimal recovery steps • DAG Technology • High Availability • Data Protection • Disaster Recovery • LAN-based log-shipping

  31. Flash Flash Flash Flash Fibre Channel Fibre Channel Fibre Channel Fibre Channel SATA SATA SATA SATA Replicate: Database Availability Group Native DAG Virtual LUN Virtual LUN 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 manualor automatic DR failover • Total system-level redundancy • Follows 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

  32. Replicate: Flash Flash Fibre Channel Fibre Channel SATA SATA Third-Party Failover and Replication Virtual LUN Virtual LUN RP-Journal RP-Journal • 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 production • Pay 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”

  33. Flash Flash Fibre Channel Fibre Channel SATA SATA Replicate: Database Availability Group Third-Party Replication, Native Failover Virtual LUN Virtual LUN • 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/vLAN • Same 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 RP-Journal RP-Journal

  34. DEMO Site-to-site automated failover using Replication Enabler for Exchange

  35. Flash Flash Fibre Channel Fibre Channel SATA SATA EMC makes Exchange Better! Database Availability Group 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 Virtual LUN Virtual LUN RP-Journal RP-Journal

More Related