Exchange Storage Sizing and Hardware Exposed Jim McBee

Slides:



Advertisements
Similar presentations
Module 10 Planning Microsoft® Exchange Server 2010 Monitoring and Troubleshooting.
Advertisements

Module 11 Maintaining Microsoft Exchange Server 2010.
SharePoint and SQL Server integration Demo: SQL Server Optimizing Configurations SQL Server 2014 for SharePoint 2013 Avoiding ginormous transaction.
2.1 © 2004 Pearson Education, Inc. Exam Managing and Maintaining a Microsoft® Windows® Server 2003 Environment Lesson 2: Installing Windows Server.
CCC/WNUG Exchange Update May 5, 2005 Nate Wilken Web and Messaging Applications Information Technology Arizona State University.
70-290: MCSE Guide to Managing a Microsoft Windows Server 2003 Environment Chapter 11: Monitoring Server Performance.
Lesson 18 – INSTALLING AND SETTING UP WINDOWS 2000 SERVER.
Installing Exchange 2010 IT:Network:Applications.
1.1 Installing Windows Server 2008 Windows Server 2008 Editions Windows Server 2008 Installation Requirements X64 Installation Considerations Preparing.
Jaap Wesselius May 27, 2009 Exchange Server 2010 what’s new?
13.1 © 2004 Pearson Education, Inc. Exam Planning, Implementing, and Maintaining a Microsoft® Windows® Server 2003 Active Directory Infrastructure.
70-290: MCSE Guide to Managing a Microsoft Windows Server 2003 Environment Chapter 2: Managing Hardware Devices.
Lesson 4-Installing Network Operating Systems. Overview Installing and configuring Novell NetWare 6.0. Installing and configuring Windows 2000 Server.
70-290: MCSE Guide to Managing a Microsoft Windows Server 2003 Environment Chapter 2: Managing Hardware Devices.
MCITP Guide to Microsoft Windows Server 2008 Server Administration (Exam #70-646) Chapter 14 Server and Network Monitoring.
Yes, yes it does! 1.Guest Clustering is supported with SQL Server when running a guest operating system of Windows Server 2008 SP2 or newer.
Virtualized Workloads Supported Instant Messaging (IM) IM Conferencing Presence Enterprise Voice (PSTN) Audio/Video Conferencing Web Conferencing.
Chapter 9 Overview  Reasons to monitor SQL Server  Performance Monitoring and Tuning  Tools for Monitoring SQL Server  Common Monitoring and Tuning.
Module 8: Monitoring SQL Server for Performance. Overview Why to Monitor SQL Server Performance Monitoring and Tuning Tools for Monitoring SQL Server.
Presented by Jacob Wilson SharePoint Practice Lead Bross Group 1.
EXC11: Migrating to Exchange 2010 from Exchange 2003 Jim McBee Ithicos Solutions LLC
Capacity Planning in SharePoint Capacity Planning Process of evaluating a technology … Deciding … Hardware … Variety of Ways Different Services.
NovaBACKUP 10 xSP Technical Training By: Nathan Fouarge
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network, Enhanced Chapter 14: Problem Recovery.
Nexenta Proprietary Global Leader in Software Defined Storage Nexenta Technical Sales Professional (NTSP) COURSE CONTENT.
MCITP Administrator: Microsoft SQL Server 2005 Database Server Infrastructure Design Study Guide (70-443) Chapter 1: Designing the Hardware and Software.
Welcome Thank you for taking our training. Collection 6421: Configure and Troubleshoot Windows Server® 2008 Network Course 6690 – 6709 at
WINDOWS XP PROFESSIONAL Bilal Munir Mughal Chapter-1 1.
70-290: MCSE Guide to Managing a Microsoft Windows Server 2003 Environment, Enhanced Chapter 2: Managing Hardware Devices.
Nexenta Proprietary Global Leader in Software Defined Storage Nexenta Technical Sales Professional (NTSP) COURSE CONTENT.
Appendix B Planning a Virtualization Strategy for Exchange Server 2010.
Module 1: Installing and Upgrading to Exchange Server 2003.
© Wiley Inc All Rights Reserved. MCSE: Windows Server 2003 Active Directory Planning, Implementation, and Maintenance Study Guide, Second Edition.
70-290: MCSE Guide to Managing a Microsoft Windows Server 2003 Environment, Enhanced Chapter 11: Monitoring Server Performance.
Exchange 2007 The First 100 Days Jim McBee Ithicos Solutions
Guide to MCSE , Second Edition, Enhanced1 The Microsoft Networking Family Collection of operating systems (OS) Operating Systems Work directly with.
1 Microsoft Exchange 2000 Server Maintenance and Troubleshooting System Maintenance and Monitoring Database Operation and Maintenance Backup, Restore,
Module 1: Installing and Configuring Servers. Module Overview Installing Windows Server 2008 Managing Server Roles and Features Overview of the Server.
1 Computer and Network Bottlenecks Author: Rodger Burgess 27th October 2008 © Copyright reserved.
MCSE Guide to Microsoft Exchange Server 2003 Administration Chapter Two Installing and Configuring Exchange Server 2003.
Microsoft ® Exchange Server 2010 with Service Pack 1 Infrastructure Planning and Design Published: December 2010 Updated: July 2011.
Module 4 Planning and Deploying Client Access Services in Microsoft® Exchange Server 2010 Presentation: 120 minutes Lab: 90 minutes After completing.
Designing and Deploying a Scalable EPM Solution Ken Toole Platform Test Manager MS Project Microsoft.
Monitoring Windows Server 2012
Module 11 Maintaining Microsoft® Exchange Server 2010.
© 2008 Quest Software, Inc. ALL RIGHTS RESERVED. Perfmon and Profiler 101.
70-294: MCSE Guide to Microsoft Windows Server 2003 Active Directory, Enhanced Chapter 13: Monitoring and Optimizing Active Directory.
70-290: MCSE Guide to Managing a Microsoft Windows Server 2003 Environment, Enhanced Chapter 11: Monitoring Server Performance.
Module 3 Planning and Deploying Mailbox Services.
Module 5 Planning and Deploying Message Transport in Microsoft® Exchange Server 2010.
11 CLUSTERING AND AVAILABILITY Chapter 11. Chapter 11: CLUSTERING AND AVAILABILITY2 OVERVIEW  Describe the clustering capabilities of Microsoft Windows.
1 Chapter Overview Planning to Install SQL Server 2000 Deciding SQL Server 2000 Setup Configuration Options Running the SQL Server 2000 Setup Program Using.
Exchange Server 2007 Deployment and Migration Strategies Nireshen Beerbul
Managing Hardware Devices Facilitator: Suleiman Mohammed(mcpn, mncs) Institute of Computing & ICT, Ahmadu Bello University, Zaria.
1 | SharePoint Saturday Calgary – 31 MAY 2014 About Me.
Installation of Storage Foundation for Windows High Availability 5.1 SP2 1 Daniel Schnack Principle Technical Support Engineer.
Windows Server 2003 系統效能監視 林寶森
Jeff Mealiffe Sr. Program Manager Microsoft Corporation SESSION CODE: UNC301 Evan Morris Sr. Systems Engineer Hewlett-Packard.
1 Chapter Overview Monitoring Access to Shared Folders Creating and Sharing Local and Remote Folders Monitoring Network Users Using Offline Folders and.
Maximizing Performance – Why is the disk subsystem crucial to console performance and what’s the best disk configuration. Extending Performance – How.
Hands-On Microsoft Windows Server 2008 Chapter 7 Configuring and Managing Data Storage.
EXCHANGE UTILITY BELT TIPS (AKA EXCHANGE TOOLS) Speaker: Dave Stork Company: OGD ict-diensten bv Position: Architect.
Configuring SQL Server for a successful SharePoint Server Deployment Haaron Gonzalez Solution Architect & Consultant Microsoft MVP SharePoint Server
CygNet Database Service Diagnostics and Performance Tuning
SharePoint Solutions Architect, Protiviti
Installation and database instance essentials
Software Architecture in Practice
Migration Strategies – Business Desktop Deployment (BDD) Overview
Design Unit 26 Design a small or home office network
Microsoft Exchange Server Virtualisation: Does It Make Sense?
Presentation transcript:

Exchange Storage Sizing and Hardware Exposed Jim McBee

Who is Jim McBee!!?? Consultant, Writer, MCSE, MVP and MCT – Honolulu, Hawaii Principal clients (Dell, Microsoft, SAIC, Servco Pacific) Author – Exchange 2003 Advanced Administration (Sybex) Contributor – Exchange and Outlook Administrator Blog ● ●

Agenda The sizing quandary User usage profiles Microsoft’s hardware recommendations Network sizing RAM sizing CPU sizing Disk sizing Did you get it right?

The sizing quandary

Typical solution Throw hardware at the solution… Sometimes you get it right… ● and sometimes you don’t… Often disk capacity is still undersized

Usage profiles

Messaging user types TypeMessages sent/received Mailbox size Light5 sent 20 received 50MB Average10 sent 40 received 100MB Heavy20 sent 80 received 200MB Large30 sent 120 received 500MB

Active Directory

Sizing domain controllers Use Windows 2003 SP1 if possible Windows 2003 domain and forest functional level Use 4:1 ratio ● For each 4 Exchange CPUs/cores use 1 DC/GC core ● This ratio assumes dedicated Exchange DCs Redundant DNS servers and domain controllers Larger Active Directories… ● Put transaction logs and databases on different spindles ● If NTDS.DIT database exceeds about 1GB, use Windows the /3GB /USERVA=3030 switches ● If the NTDS.DIT database exceeds about 2.5GB, use Windows 2003 x64 or Windows 2008 x64

Problem indicators MSExchangeDSAccess Process – E2K3 MSExchange ADAccess Domain Controllers ● LDAP Read Time ● LDAP Search Time Should be below 50 milliseconds on average Should never exceed 100 milliseconds

Network sizing

Network connections 100Mbps / Full Duplex Switched backbone is best Ensure that network adapter is inserted in to network at maximum speed possible ● May require manual configuration on server and switch Use separate 1GB Ethernet connections for iSCSI

Key indicator you may have network problems Performance monitor: ● MSExchangeIS / RPC Averaged Latency Should be below 50 milliseconds May indicate hardware problems, but network is often the culprit ● Network Interface / Bytes Total/sec Watch for this counter to approach maximum network bandwidth

CPU sizing

Microsoft’s recommendation Server roleMinimumRecommendedMaximum Mailbox1 CPU core4 CPU cores8 CPU cores Client Access1 CPU core4 CPU cores Hub Transport1 CPU core4 CPU cores8 CPU cores Unified Messaging 1 CPU core4 CPU cores Combined function 1 CPU core4 CPU cores Edge Transport1 CPU core2 CPU cores4 CPU cores

Megacycles per second Number of MHz that are required for a particular server Take an average CPU usage during the busiest part of the day Megacycles per mailbox = (Avg CPU * Speed of processors in MHz * Number of processors) / Number of mailboxes

Excessive CPU usage? Average processor usage stays above 70 – 80% during the busiest parts of the day

Memory sizing

RAM is the key to improving performance in Exchange Exchange 2003 ● 4GB of RAM per server ● User /3GB /USERVA=3030 in BOOT.INI file ● Large environments ● 2GB – 4GB of RAM for front-end servers and bridgehead servers For tuning information… ● See KB How to Optimize Memory Usage in Exchange Server 2003

Exchange 2003 and caching Exchange 2003 Extensible Storage Engine maximum cache ● 1.2GB of cache ● 576MB or 896MB by default 500 users on an optimized E2K3 server ● 2.4MB of cache per user 1000 users on an optimized E2K3 server ● 1.2MB of cache per user 2000 users on an optimized E2K3 server ●.6MB of cache per user

Exchange 2007 memory sizing Server roleMinimumRecommendedMaximum Hub Transport2GB1GB per CPU core (2GB minimum) 16GB Client Access2GB1GB per CPU core (2GB minimum) 8GB Unified Messaging 2GB1GB per CPU core (2GB minimum) 4GB Edge Transport2GB1GB per CPU core (2GB minimum) 16GB

Mailbox server roles Minimum of 2GB of RAM ● Minimum of 3GB of RAM if LCR is used ● Recommend 4GB of RAM Recommend 2GB + 5MB per mailbox for heavy users Can size memory based on number of storage groups, too. ● Add 2GB for each four storage groups ● Take whichever value is higher BOOT.INI optimization is not necessary 32GB maximum practical amount

Cache is essential If you follow recommendations for heavy users, each user will ALWAYS have 5MB of cache available Sufficient memory is essential to get expected disk performance Less available cache = More frequent disk I/O

Disk sizing

Introducing IOPS IOPS = Disk I/O operations per second ● Pronounced eye-ops Typical I/O capacity ● 10,000 RPM SATA drive = 70 IOPS ● 10,000 RPM fiber channel disk = 100 IOPS ● 15,000 RPM fiber channel disk = 120 IOPS ● 15,000 RPM SAS drive = 170 IOPS

Exchange 2003 IOPS Estimates User typeDatabase volume IOPS Light.5 Average.75 Heavy1.0 Large1.5

Exchange 2003 diminished cache performance MailboxesEstimated IOPS Calculated IOPS Required Actual IOPS Required Why? Less cache per mailbox

Exchange 2007 IOPS Estimates User typeDatabase volume IOPS Light.14 Average.20 Heavy.27 Large.41 *Assumes you are following Microsoft’s memory recommendations for Exchange 2007

Factors that affect IOPS Antivirus software Backups Outlook in cached mode LCR (estimates are 150% of database IOPS) Full text indexing (10% overhead for E2K7) Forms processing, work flow systems, or unusual messaging spikes Online maintenance Other server roles on same hardware (such as Hub Transport) Paging Connectivity / protocol logging Messaging records management

Transaction Logs and IOPS Microsoft’s estimates are for databases only Transaction logs may generate 10 – 25% additional I/O

Viewing Disk Transfers/sec

You can help! Use the maximum amount of practical memory for Exchange mailbox servers Sizing disk on right sector ● Use DiskPart.exe ● See KB Configure caching controllers for 75% write / 25% read

Signs of a disk bottleneck Physical disk’s Avg. Disk sec/Transfer >.02 on a sustained basis Physical disk’s Disk Transfers/sec staying at a sustained level

Sustained I/O activity

Tools you can use Performance monitor Exchange Best Practices Analyzer Performance Tuning Analyzer Exchange Server JetStress Exchange Server Load Generator Exchange Server Stress and Performance Exchange Troubleshooting Assistant User Monitor Microsoft Operations Manager

Free eBook The Shortcut Guide to Exchange Server 2007 Storage Systems ● m/SGES2K7SS.htm m/SGES2K7SS.htm

Questions? Thanks for attending!

Book giveaway and notice Please give me a piece of paper with your name for drawing Include your address or give me a business card if you want: ● 20% discount code for Directory Update software ● Notification when Mastering Exchange Server 2007 is available

Your Feedback is Important Please fill out a session evaluation form and either put them in the basket near the exit or drop them off at the conference registration desk. You could win one of 10 subscriptions to TechNet Plus Direct: The essential resource for IT Professionals. Winners will be drawn and names will be posted Tuesday morning from Monday evals, Wednesday morning from Tuesday evals, and during closing session from Wendesday evals. Include your badge number on your session eval so we can figure out the winners! Thank you!