Jeff Mealiffe Sr. Program Manager Microsoft Corporation SESSION CODE: UNC301 Evan Morris Sr. Systems Engineer Hewlett-Packard.

Slides:



Advertisements
Similar presentations
Minimising IT costs, maximising operational efficiency minimising IT costs, maximising operational efficiency Balance.
Advertisements

Mission Critical Messaging Platform Roni Havas Unified Communications Solution Specialist Specialists Technology Unit – EPG - Microsoft Israel
© 2010 Cisco and/or its affiliates. All rights reserved. 1 Microsoft Exchange Server Ready UCS Data Center & Virtualizacion Cisco Latin America Valid through.
F5 solution for Microsoft Exchange. 2 Exchange 2010 Architecture External SMTP servers Edge Transport Routing and AV/AS Phone system (PBX or VoIP) Client.
1© Copyright 2011 EMC Corporation. All rights reserved. EMC SQL Server Data Warehouse Fast Track Solutions Nov 30, 2011 Ling Wu, EMC.
F5 Solution for Microsoft Exchange 2010 James Hendergart Business Development Manager Helen Johnson Solution Engineer.
Going 64-bit with Microsoft Exchange Server 2007 Published: November 2006.
Installing Exchange 2010 IT:Network:Applications.
Optimize for Software + Services Archiving Archiving Protect CommunicationsProtect Communications Advanced SecurityAdvanced Security Manage.
Dean Paron Product Unit Manager Microsoft Corporation SESSION CODE: WSV335 © 2010 Microsoft Corporation. All rights reserved.
Unified. Simplified. Unified Communications Launch 2007.
Exchange 2010 Overview Name Title Group. What You Tell Us Communication overload Globally distributed customers and partners High cost of communications.
Virtual Network Servers. What is a Server? 1. A software application that provides a specific one or more services to other computers  Example: Apache.
Exchange 2007 Overview. What Will We Cover? New features in Microsoft® Exchange 2007 The Exchange Management Console The Exchange Management Shell New.
Exchange 2010 Project Presentation/Discussion August 12, 2015 Project Team: Mark Dougherty – Design John Ditto – Project Manager Joel Eussen – Project.
Overview of Exchange 2013 Architecture Transport components shipping with Exchange 2013 Mail Routing Scenarios Transport High Availability SMTP Client.
Andrew Sullivan Program Manager, Outlook Microsoft Corporation SESSION CODE: OSP314.
Exchange Deployment Planning Services Exchange Server 2010 Planning and Sizing.
Introduction to Exchange Server 2010 Omar El-Sherif Solutions Specialist – Unified Communications Microsoft Egypt.
Kevin St. Clair Sr. Support Engineer Hewlett-Packard SESSION CODE: UNC306.
Jeff Mealiffe Senior Development Lead Microsoft Corporation Session Code: UNC309.
Mark Harmsworth – Architecture Nate Bruneau – Engineering Scott Kleven – Program Management Microsoft Corporation SESSION CODE: OSP321.
EXL311: Exchange Server 2013 Architecture Deep Dive Scott Schnoll Microsoft Corporation EXL311.
Mobility And Anywhere Access Clancy Priest Technology Services Director City of Hayward.
Module 6: Manage and Configure Messaging. Configuring Internet Mail Using Small Business Server (SBS) 2008 Console Configuring Protection Configuring.
IT:Network:Applications.  How messaging servers work  Initial tips for success Exchange management  Server roles  Exchange Server Management  Message.
Appendix B Planning a Virtualization Strategy for Exchange Server 2010.
Ross Smith IV Senior Program Manager, Exchange Server Microsoft Corporation SESSION CODE: UNC202 Kyryl Perederiy Senior Systems Engineer, Business Online.
Exchange Storage Sizing and Hardware Exposed Jim McBee
Copyright © 2010, Scryer Analytics, LLC. All rights reserved. Optimizing SAS System Performance − A Platform Perspective Patrick McDonald Scryer Analytics,
Ashwin Sarin Program Manager Microsoft Corporation SESSION CODE: COS204.
Mark Heneen, Steve Daigle, Tracey Jordan, Zach Beers Microsoft Corporation SESSION CODE: COS205.
Boris Jabes Senior Program Manager Microsoft Corporation SESSION CODE: DEV319 Scale & Productivity in Visual C
Harvinder Bhela General Manager, Exchange Microsoft Corporation SESSION CODE: UNC201
Module 4 Planning and Deploying Client Access Services in Microsoft® Exchange Server 2010 Presentation: 120 minutes Lab: 90 minutes After completing.
Session objectives Discuss whether or not virtualization makes sense for Exchange 2013 Describe supportability of virtualization features Explain sizing.
Transport components shipping with Exchange 2013 Overview of Exchange 2013 Architecture Architectural improvements made in Transport History, Challenges,
Appendix A UM in Microsoft® Exchange Server 2010.
Joe Yong Chief Architect Scalability Experts SESSION CODE: DAT 205.
OSP310. What is a SharePoint® Farm? A collection of one or more SharePoint Servers and SQL Servers® providing a set of basic SharePoint.
Tim Crabb Sr. Program Manager Microsoft Corporation SESSION CODE: VIR302.
Suhail Dutta Program Manager Microsoft Corporation SESSION CODE: DEV402.
Module 3 Planning and Deploying Mailbox Services.
Aaron Skonnard & Keith Brown Cofounders, Pluralsight SESSION CODE: ASI308 Programming AppFabric: Moving.NET to the Cloud.
Module 5 Planning and Deploying Message Transport in Microsoft® Exchange Server 2010.
Module 7 Planning and Deploying Messaging Compliance.
Thomas Deml Principal Program Manager Web Platform and Tools Microsoft Corporation SESSION CODE: WEB308.
AD Web browser Outlook (remote user) Mobile phone Line of business application Outlook (local user) External SMTP servers Exchange Online Protection.
Clint Huffman Microsoft Premier Field Engineer (PFE) Microsoft Corporation SESSION CODE: VIR315 Kenon Owens Technical Product Manager Microsoft Corporation.
Read/understand sizing, scalability, capacity guidance Documentation on technet, Exchange team blog, etc. Collect data on existing deployment.
Jeff King Senior Program Manager, Visual Studio Microsoft Corporation SESSION CODE: WEB305.
Lori Dirks Expression Community Manager Microsoft Corporation SESSION CODE: WEB309.
UNC301 - (Microsoft IT) Microsoft Exchange 2007 Architecture and Design at Microsoft Martin Coetzer Technical Consultant Microsoft.
Solution to help customers and partners accelerate their data.
Exchange Server 2007 Deployment and Migration Strategies Nireshen Beerbul
Chris Mayo Microsoft Corporation SESSION CODE: UNC207.
Scott Schnoll m Microsoft Corporation.
Olivier Bloch Technical Evangelist Microsoft Corporation SESSION CODE: WEM308.
Younus Aftab Program Manager Microsoft Corporation SESSION CODE: WSV324.
Thomas Deml Principal Program Manager Microsoft Corporation SESSION CODE: WSV317.
Martin Woodward Program Manager Microsoft Corporation SESSION CODE: DEV308.
Dustin Johnson Microsoft Practice Lead Dell, Inc. SESSION CODE: UNC302.
Christophe Fiessinger & Jan Kalis Senior Technical Product Manager Microsoft Corporation SESSION CODE: OSP209.
VIRTUAL SERVERS Chapter 7. 2 OVERVIEW Exchange Server 2003 virtual servers Virtual servers in a clustering environment Creating additional virtual servers.
Deployment on your terms Hybrid Exchange deployment on your terms On-premises.
Software Architecture in Practice
Design Unit 26 Design a small or home office network
Microsoft Exchange Server Virtualisation: Does It Make Sense?
Enterprise Topography
Implementing Exchange Server 2013
Presentation transcript:

Jeff Mealiffe Sr. Program Manager Microsoft Corporation SESSION CODE: UNC301 Evan Morris Sr. Systems Engineer Hewlett-Packard

Research Understand hardware Business requirements to technical requirements Understand Exchange Evaluation Solution sizing, configuration, validation Hardware selection Implementation Migrate & grow

Increased CPU efficiency e.g. Nehalem processors Next-gen: Intel Westmere & AMD Magny-Cours

Front View Rear View Side View with one 35 drive drawer extended 3.5” SAS or SATA drives 2 Power supplies 4 for redundancy Drawer 1 – 35 drivesDrawer 2 – 35 drives 4 Fans Lower cost per drive bay than shelves: $8500 / 70 = ~$121 / bay vs. $3400 / 12 = ~$283 / bay (Internet List Price) 2 port I/O modules – up to 4 per MDS600 for dual-path

Enterprise Network External SMTP servers Mailbox Storage of mailbox items Edge Transport Routing & AV/AS Unified Messaging Voice mail & voice access Phone system (PBX or VOIP) Client Access Client connectivity Web services Hub Transport Routing & Policy Web browser Outlook (remote user) Mobile phone Outlook (local user) Line of business application

Mailbox Role Sizing Rules Of Thumb 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)! 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

2GB512MB Not supported 4GB1GB 8GB3.6GB2GB 16GB10.4GB8GB 24GB17.6GB14GB 32GB24.4GB20GB 48GB39.2GB32GB 64GB53.6GB44GB 96GB82.4GB68GB 128GB111.2GB92GB

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 Outlook Anywhere Exchange ActiveSync (delta from Outlook) Exchange Web Services (Microsoft Entourage) Outlook Web Access IMAP4* POP3* * 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 L 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 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 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

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 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 8 core root CAS/HUBMailbox 16 core root CAS/HUBMailboxCAS/HUBMailbox 24 core root CAS/HUBMailboxCAS/HUBMailboxCAS/HUBMailbox

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 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 Understand hardware Business requirements to technical requirements Understand Exchange Evaluation Solution sizing, configuration, validation Hardware selection Implementation Migrate & grow

SANEVA GB BL (blade) Done SASMDS GB DL (rack) Done Shared DAS MDS GB BL (blade) Done Shared DAS MSA2000sa GB DL (rack) Done SAN P2000 (FC) GB BL (blade) Done DAS D2600 ENT GB DL (rack) In Progress DAS D2600 MDL GB 3. 5 GB DL (rack) In Progress DASInternal GB DL370 (rack or tower) In Progress

PlatinumYes32Dedicated FC/iSCSI/SAS/ MDL-SATA RAID/JBOD GoldYes21Dedicated RAID SilverYes21MBX/HT/CAS iSCSI/SAS/ MDL-SATA RAID BronzeNo10MBX/HT/CASSAS/MDL-SATARAID

Research Understand hardware Business requirements to technical requirements Understand Exchange Evaluation Solution sizing, configuration, validation Hardware selection Implementation Migrate & grow

Sign up for Tech·Ed 2011 and save $500 starting June 8 – June 31 st You can also register at the North America 2011 kiosk located at registration Join us in Atlanta next year