Research Evaluation Implementation • Understand hardware • Business requirements to technical requirements • Understand Exchange • Solution sizing, configuration, validation • Hardware selection • Migrate & grow.
Download ReportTranscript Research Evaluation Implementation • Understand hardware • Business requirements to technical requirements • Understand Exchange • Solution sizing, configuration, validation • Hardware selection • Migrate & grow.
Research Evaluation Implementation • Understand hardware • Business requirements to technical requirements • Understand Exchange • Solution sizing, configuration, validation • Hardware selection • Migrate & grow Increased CPU efficiency e.g. Nehalem processors Next-gen: Intel Westmere & AMD Magny-Cours Front View Drawer 1 – 35 drives Drawer 2 – 35 drives Side View with one 35 drive drawer extended 3.5” SAS or SATA drives 2 Power supplies 4 for redundancy Rear View 4 Fans 2 port I/O modules – up to 4 per MDS600 for dual-path Lower cost per drive bay than shelves: $8500 / 70 = ~$121 / bay vs. $3400 / 12 = ~$283 / bay (Internet List Price) Enterprise Network Edge Transport Routing & AV/AS Phone system (PBX or VOIP) Hub Transport Routing & Policy External SMTP servers Mailbox Storage of mailbox items Mobile phone Web browser Unified Messaging Voice mail & voice access Client Access Client connectivity Web services Outlook (remote user) Line of business application Outlook (local user) Mailbox Role Sizing Rules Of Thumb Storage I/O and capacity requirements Memory Database cache requirements (reduces I/O) CPU Required for RPC operations, content indexing, mailbox assistants, replication operations Network Log replication and RPC operations consume bandwidth http://tinyurl.com/262cpg9 • • • 2-socket platform best for performance and TCO User profile determines resource requirements for IOPS, memory, CPU Don’t forget about high availability (Database Availability Groups)! 50 3 .060 .050 100 6 .120 .100 150 9 .180 .150 200 12 .240 .200 250 15 .300 .250 300 18 .360 .300 350 21 .420 .350 400 24 .480 .400 450 27 .540 .450 500 30 .600 .500 50 3 100 6 150 9 200 12 250 15 300 18 350 21 400 24 450 27 500 30 2GB 512MB Not supported 4GB 1GB Not supported 8GB 3.6GB 2GB 16GB 10.4GB 8GB 24GB 17.6GB 14GB 32GB 24.4GB 20GB 48GB 39.2GB 32GB 64GB 53.6GB 44GB 96GB 82.4GB 68GB 128GB 111.2GB 92GB 50 1 .15 100 2 .3 150 3 .45 200 4 .6 250 5 .75 300 6 .9 350 7 1.05 400 8 1.2 450 9 1.35 500 10 1.5 Client Access Server Role Sizing Rules Of Thumb • • • • • 2-socket platform best for performance and TCO CPU is typically the bottleneck, memory sizing is key as well 3 CAS CPU cores for every 4 Mailbox CPU cores (servicing active users) Load balancing is important for performance and high availability 2GB RAM per CPU core is optimal CPU Required for handling client workload transactions, content conversion, garbage collection Memory Memory required for ongoing transaction processing Network All clients connect to CAS, network bandwidth and latency are important for client experience, load balancing likely required Storage Utilized for content conversion, logging Outlook 0.35 0.37 Outlook Anywhere 0.80 0.44 Exchange ActiveSync (delta from Outlook) 1.60 1.04 Exchange Web Services (Microsoft Entourage) 0.71 0.54 Outlook Web Access 0.86 0.88 IMAP4* 0.86 0.14 POP3* 0.33 0.79 * IMAP4 & POP3 protocols do not support sending new mail, so the observed costs do not reflect any sent messages within the user profile. Reference CAS server platform has 2 processor sockets on the motherboard populated with Intel Xeon L5335 4-core processors running at 2.00GHz for a total of 8 physical cores. Hyperthreading is disabled on this platform to allow for more accurate computation of CPU costs. The platform runs with 16GB of RAM. Observed costs will vary depending on user profile and other parameters defining a workload – these values are only meant to represent observed costs for a normalized sample workload. Transport Roles Sizing Rules Of Thumb CPU CPU required for message processing, hygiene activities, custom agents • Memory Database cache requirements (reduces I/O), messages in queue represented in memory for perf • Storage Low to moderate I/O requirement for relay & delivery activity, queuing needs more I/O+capacity Network Bandwidth utilized to relay/deliver messages – scales with message volume, latency can cause queuing • • 2-socket platform best for performance and TCO CPU is typically the bottleneck, memory sizing is key as well 1 Transport CPU core for every 7 Mailbox CPU cores (no A/V) or 1 Transport CPU core for every 5 Mailbox CPU cores (with A/V) 1GB RAM per CPU core is optimal Unified Messaging Role Sizing Rules Of Thumb • • • • • 2-socket platform best for performance and TCO 2GB RAM per core is optimal CPU is typically the bottleneck, particularly when Voice Mail Preview is being used Default 100 concurrent calls per server (inbound or outbound) Voice Mail Preview is CPU intensive: ~1 message/min/core CPU CPU used for media operations and Voice Mail Preview transcription – UM is typically “CPU heavy” Network Network bandwidth used for calls as well as communication with Mailbox role. Minimize latency for best user experience Memory Memory required for ongoing transaction processing Storage UM doesn’t have significant storage requirements Multi-Role Hub/CAS Servers Sizing Rules Of Thumb • • • • CAS/HUB Mailbox CAS/HUB CAS/HUB Mailbox Mailbox CAS/HUB CAS/HUB CAS/HUB Mailbox Mailbox Mailbox 2-socket platform best for performance and TCO CPU is typically the bottleneck, memory sizing is key as well 1 Hub/CAS CPU core for every 1 Mailbox CPU core 2GB RAM per CPU core is optimal Multi-Role “Brick” Servers Sizing Rules Of Thumb • • Recommend maximum 4-socket platform for multi-role deployment Use 8GB RAM plus 3-30MB per mailbox (see Mailbox role sizing details) Virtualized Server Roles Sizing Rules Of Thumb • http://tinyurl.com/26k4g5j http://tinyurl.com/5abmlh • • • http://tinyurl.com/lyko6t Size for physical resources, add ~12% CPU overhead for hypervisor Avoid resource oversubscription Don’t co-locate Mailbox databases on a root server CAS+Hub combination can make scale calculations easy Research Evaluation Implementation • Understand hardware • Business requirements to technical requirements • Understand Exchange • Solution sizing, configuration, validation • Hardware selection • Migrate & grow http://tinyurl.com/y9shhpx http://tinyurl.com/ycmey8c http://www.hp.com/solutions/microsoft/exchange http://technet.microsoft.com/en-us/exchange/ff182054.aspx SAN EVA8400 9000 2 GB BL (blade) Done SAS MDS600 7500 3 GB DL (rack) Done Shared DAS MDS600 4000 3 GB BL (blade) Done Shared DAS MSA2000sa 4000 1 GB DL (rack) Done SAN P2000 (FC) 4000 1 GB BL (blade) Done DAS D2600 ENT 6000 1 GB DL (rack) In Progress DAS D2600 MDL 3000 3.5 GB DL (rack) In Progress DAS Internal 1000 2 GB DL370 (rack or tower) In Progress Platinum Yes 3 2 Dedicated FC/iSCSI/SAS/ MDL-SATA RAID/JBOD Gold Yes 2 1 Dedicated FC/iSCSI/SAS/ MDL-SATA RAID Silver Yes 2 1 MBX/HT/CAS iSCSI/SAS/ MDL-SATA RAID Bronze No 1 0 MBX/HT/CAS SAS/MDL-SATA RAID Research Evaluation Implementation • Understand hardware • Business requirements to technical requirements • Understand Exchange • Solution sizing, configuration, validation • Hardware selection • Migrate & grow TechEd Online microsoft.com/communicationsserver Technical Library NextHop Partner Link Customer Link Exchange 2010 SP1 Beta download DrRez on Twitter Communications Server Exchange Server www.microsoft.com/teched www.microsoft.com/learning http://microsoft.com/technet http://microsoft.com/msdn Sign up for Tech·Ed 2011 and save $500 starting June 8 – June 31st http://northamerica.msteched.com/registration You can also register at the North America 2011 kiosk located at registration Join us in Atlanta next year