540 likes | 806 Views
Required Slide. SESSION CODE: UNC306. Going Big! Deploying Large Mailboxes with Microsoft Exchange Server 2010 without Breaking the Bank . Kevin St. Clair Sr. Support Engineer Hewlett-Packard. AGENDA. What do large mailboxes give me?
E N D
Required Slide SESSION CODE: UNC306 Going Big! Deploying Large Mailboxes with Microsoft Exchange Server 2010 without Breaking the Bank Kevin St. Clair Sr. Support Engineer Hewlett-Packard
AGENDA • What do large mailboxes give me? • What do I need to consider when deploying large mailboxes? • How do all of the parts fit together in a solid design?
Why large mailboxes?Get PST files under control • User’s PST files at risk on the laptop or desktop • User’s PST files typically not backed up • Recovery from corruption is painful 2006-PST 2007-PST 2010-PST 2008-PST 2009-PST
Why large mailboxes?Add value for users • Search historical data • Don’t recreate work • Reduce time spent managing mailbox
2010-PST Why large mailboxes?Add value for users • PST files only available on single machine 2010-PST
Why large mailboxes?Adding IT Value • Search across all mailboxes including data that was in a PST • Dumpster 2.0 – searchable as well! • Legal Hold • Use high-capacity drives efficiently
Large mailbox considerationsPresent Environment • Skillset and training of staff • Stability Issues • Pain points
Large mailbox considerationsBusiness Needs • Business requirements, expectations and SLA • Productivity Features – Mailbox moves online • Search historical information
Large mailbox considerationsDisaster Recovery • Backup & restore methods ~30 seconds 2+ hours – weekly full
Large mailbox considerationsDisaster Recovery • Availability consideration • Continuous availability (DAG)
Large mailbox considerationsDisaster Recovery • Availability consideration • Continuous availability (DAG) • Restoration of service (non-DAG)
Large mailbox designKnow your environment • Strengths and weaknesses • User profile and data quantity = Mailbox data + PST data • Exchange Server 2003 support ending when the next version of Exchange releases
Large mailbox designSelect appropriate options • Business requirements • Storage • Licensing
Large mailbox designBusiness requirements • Service Level Agreements (SLA) • Business requirements • Regulatory compliance • Increase in mail volume for users
Large mailbox designStorage Performance 0.12 IOPS • Balancing act between performance and capacity Capacity 10 GB
Large mailbox designStorage • Performance Drivers • User workload
Large mailbox designStorage • Performance Drivers • User workload • Third party applications – BlackBerry • Desktop Search
Large mailbox designStorage • Exchange Storage changes • Move from random to sequential IO • Larger database page size: • Exchange 2010 has 32 KB page size • Exchange 2007 has 8 KB page size
Large mailbox designStorage • Exchange Storage changes • Reduction in IOPs
Large mailbox designStorage • Performance Drivers • Maintenance • Default is 24x7 • Large block sequential
Large mailbox designStorage • Disks increasing in size • Disk speed has remained unchanged • Largest capacity disks are midline SAS and SATA
Large mailbox designStorage • Database capacity • Message data • Deleted Items • White space • Legal Hold • Performance and capacity overhead Database
Large mailbox designStorage • Two LUNs per database or backup set • RAID Free Space 20% Content Index 10% Database Free Space 20% Transaction Logs
Large mailbox designStorage • One LUN per database • JBOD Free Space 20% Content Index 10% Database Transaction Logs
Large mailbox designStorage • Mount Point Root
Large mailbox designStorage • Types of storage • Internal direct-attached storage (DAS) • External direct-attached storage (DAS) • Storage Area Network (SAN)
Large mailbox designStorage • Storage connectivity • Array controller • Cache • Logical and physical drives • Host Bus Adapter (HBA) • Fibre Channel
Large mailbox designStorage – per spindle • Exchange 2007 • Heavy user profile (20 sent/80 received) • 0.32 IOPS per user • 300 GB – 15K RPM disk (useable 279 GB – 20%) = 223 GB with 150 IOPS • Performance - 150 IOPS / 0.32 IOPS per user = 468 mailboxes per disk • Disk size 223 GB / 468 mailboxes= 476 MBper mailbox
Large mailbox designStorage – per spindle • Exchange 2010 • Heavy user profile (100 sent & received) • 0.12 IOPS per user • 300 GB – 15K RPM disk (useable 279 GB – 20%) = 223 GB with 150 IOPS • Performance - 150 IOPS / 0.12 IOPS per user = 1,250 mailboxes per disk • Disk size - 223 GB / 1,250 mailboxes= 178 MB per mailbox
Large mailbox designStorage – per spindle • Exchange 2010 • Heavy user profile (100 sent & received) • 0.12 IOPS per user • 2 TB – 7,200 RPM disk (useable 1.818 TB – 20%) = 1.454 TB with 50 IOPS • Performance - 50 IOPS / 0.12 IOPS per user = 416 mailboxes per disk • Disk size – 1,454 TB / 416 mailboxes= 3.50 GB per mailbox
Large mailbox designActual Design – Large Enterprise Company • 150,000 Mailboxes • Current – 150 MB mailbox size • 200 Messages sent and received • Mailbox sizes discussed • 1 GB, 5 GB, 10 GB and 12 GB • SAN and DAS both considered • Exchange team wants to control all aspects of Exchange • Cost • Reliability
Large mailbox designActual Design – Large Enterprise Company • Exchange high-availability (DAG) • Two copies in primary site • Site resilience – two copies in DR site • 12 GB Mailbox size • 8,192 – 2 TB drives (JBOD) • 36,000 – 600 GB drives (RAID5) • 19,344 – 2 TB drives (RAID10)
Large mailbox designActual Design – Large Enterprise Company • Exchange high-availability (DAG) • Two copies in primary site • Site resilience – two copies in DR site • Reduced to 4 GB Mailbox size • 5,600 – 2 TB drives (RAID10)
Large mailbox designActual Design – Large Enterprise Company • Exchange high-availability (DAG) • Two copies in primary site (RAID10) • Site resilience – two copies in DR site • Copy 1 – Site Resiliency (RAID10) • Copy 2 – 14-day Lagged copy (RAID10) • Exchange Native Data Availability
Large mailbox designStorage - cost • Cost comparison
Large mailbox designStorage - features • Feature comparison
Large mailbox designStorage • Online Personal Archive • Smaller primary mailbox with larger archive Exchange database Personal Archive Mailbox Primary Mailbox
Large mailbox designStorage • Online Personal Archive • Smaller primary mailbox with larger archive • Online access only • Service Pack 1 changes to Personal Archive Exchange database Exchange database Personal Archive Mailbox Primary Mailbox
Large mailbox designClient Experience • Outlook • Support for 10GB+ mailboxes • Support for 100,000 items per folder • Indexing performance doubled • Real-time search results
Large mailbox designLicensing highlights • Windows Enterprise license • Exchange high availability (DAG) – failover clustering • Exchange Server 2010 • Database copy count = ACTIVE + Passive database copies • Standardlicense – 1 to 5 databases per server • Enterpriselicense – up to 100 databases per server • Client Access Licenses • Exchange Enterprise CAL • Personal Archiving, Advanced Journaling, Unified Messaging
Large mailbox ImplementationStrategy • Plan • Phases for implementation • Amount of mail to move • Test • Lab: develop documentation, timelines and migration procedures • Jetstress & LoadGen • Impact of corruption on mailbox move • Validate • Pilot: Delegate access, third-party application functionality • User migration timing
Large mailbox ImplementationConsiderations • Disk formatting • Quick format • Full format • BitLocker encryption • Time to encrypt is significanton larger disks
Large mailboxesSummary • Can I deploy large mailboxes cost-effectively? • Designed to be cost effective on larger disks with lower performance • Exchange Server 2010 storage enhancements
Large mailboxesSummary • What storage challenges do you face? • Choosing the type of design: SAN, DAS, JBOD • Exchange native data protection or typical backup • Where is RAID used? JBOD?
Large mailboxesSummary • When do I use Exchange DAGs? • Continuous client access to Exchange data • Point in time recovery – Lagged database copy • Deploying JBOD solutions
Large mailboxesKey takeaways… • Exchange 2010 makes more storage options available… • Large mailboxes can be deployed in a cost-effective way… • Clearly identify what your company needs Exchange to do…
Required Slide Speakers, please list the Breakout Sessions, Interactive Sessions, Labs and Demo Stations that are related to your session. Related Content • Breakout Sessions • UNC301 – Microsoft Exchange Server 2010: Sizing and Performance - Get It Right the First Time – Thurs 6/10 5pm • UNC305 – Microsoft Exchange Server 2010 High Availability Design Considerations – Tues 6/8 8am • Interactive Sessions • UNC02-INT – Busting Microsoft Exchange Server 2010 Storage Myths! – Tues 6/8 3:15pm • Hands-on Labs • UNC02-HOL – Microsoft Exchange Server 2010 High Availability and Storage Scenarios
Unified Communications Track Call to Action! Learn More! • View Related Unified Communications (UNC) Content at TechEd/after at TechEd Online • Visit microsoft.com/communicationsserver for more Communications Server “14” product information • Find additional Communications Server “14” content in the Technical Library, weekly technical articles at NextHop, and follow DrRez on Twitter • Check out Microsoft TechNet resources for Communications Server and Exchange Server • Visit additional Exchange 2010 IT Professional-focused content • Partner LinkorCustomer Link (Name: ExProPword: EHLO!world) Try It Out! • Exchange 2010 SP1 Beta downloadis now available from the download center!
Required Slide Resources Learning • Sessions On-Demand & Community • Microsoft Certification & Training Resources www.microsoft.com/teched www.microsoft.com/learning • Resources for IT Professionals • Resources for Developers • http://microsoft.com/technet • http://microsoft.com/msdn