DEFINITIVE GUIDE TO EXCHANGE SERVER 2010 MIGRATIONCHAPTER FIVE EXCHANGE 2010 KEEPING UP APPEARANCES
CHAPTER 5: EXCHANGE 2010: KEEPING UP APPEARANCES Exchange 2010 HOME KEEPING UP FOUR PILLARS OF EXCHANGE 2010 DESIGN APPEARANCES PERFORMANCE An improperly configured Exchange 2010 infrastructureISSUES, TWEAKSAND MITIGATION will cause performance issues from the get-go. Following design and management best practices will help keep yourEXCHANGE 2010 environment trouble-free. MANAGEMENTBEST PRACTICES BY ANDY GROGAN WHEN DEVELOPING Exchange Server how to troubleshoot them and, of 2007 and Exchange 2010, Microsoft course, ways to avoid them in the focused on performance.But no mat- first place through fastidious man- ter how much forethought the manu- agement practices. facturer places on performance, varying configurations that occur after installing the server will FOUR PILLARS undoubtedly affect how well it runs. OF EXCHANGE 2010 DESIGN This chapter takes a look at how Outlook users can experience gen- to configure your Exchange 2010 eral performance problems for a architecture, specifically the mail- variety of reasons, some of which box server role, from the outset to indicate basic design issues in key avoid performance issues down the areas of Exchange 2010. Proper road. Well also look at some com- architectural design after installa- mon performance problems tion can alleviate many issues. Exchange 2010 admins encounter, There are four pillars of Exchange DEFINITIVE GUIDE TO EXCHANGE SERVER 2010 MIGRATION • SEARCHEXCHANGE.COM 2
CHAPTER 5: EXCHANGE 2010: KEEPING UP APPEARANCES Server 2010 design to which you server memory (or any other server should pay close attention (see role, for that matter) or if you’ve im- Figure 1). A small misstep in one properly allocated storage, you’ll run of these four segments can greatly into some problems very quickly. affect the overall performance of Let’s take a look at two different Exchange 2010 under load. server configurations as an example. HOME Memory and storage (pillars 2 Company A consists of 5,000 users and 3) are keys to Exchange Server. spread across two Exchange 2010 FOUR PILLARS If you have improperly sized mailbox servers. Each instance of Exchange OF EXCHANGE 2010 DESIGN PERFORMANCEISSUES, TWEAKSAND MITIGATIONEXCHANGE 2010 MANAGEMENTBEST PRACTICES FIGURE 1: Four pillars of Exchange Server design DEFINITIVE GUIDE TO EXCHANGE SERVER 2010 MIGRATION • SEARCHEXCHANGE.COM 3
CHAPTER 5: EXCHANGE 2010: KEEPING UP APPEARANCES TABLE 1: Improperly Configured Exchange 2010 Versus a Correct Configuration Improper Exchange Correct Exchange 2010 Configuration 2010 Configuration HOME CPU 1 physical processor × 2 cores 2 physical processors × 4 cores RAM 16 GB (based on a base system 23 GB (based on a base system FOUR PILLARS configuration of 8 GB and 3 MB configuration of 8 GB and 6 MB OF EXCHANGE database cache per user for database cache per user for 2010 DESIGN 2,500 mailboxes for 100 mes- 2,500 mailboxes and 100 mes- sages/day) sages sent and received/day). To add scalability, opt for 32 GB. PERFORMANCEISSUES, TWEAKSAND MITIGATION Storage RAID 1 to 2.5 SATA 7.2 RPM RAID 1 to 2.5 SAS 10K RPM transaction logs disks disksEXCHANGE 2010 Storage database RAID 5 (no hot spare) to 2.5 RAID 1 to 2.5 SAS 10K RPM MANAGEMENT SATA 7.2 RPM disks disksBEST PRACTICES runs the mailbox server, client receives 100 messages per user access server and hub transport per day, you should allow 6 MB server roles. The average mailbox per mailbox on top of the 8 GB user sends and receives about 100 required for all server roles. 75 KB messages a day. The compa- ny does not use database availabili- I The RAID configuration for the ty groups. In this example, Company database drive is not optimal for A is running Exchange on two the amount of mailboxes and servers, as shown on the left-hand message traffic. side of Table 1. It is highly likely that this configu- I This system wasn’t designed to ration will experience Outlook per- scale, so any daily expansion with- formance issues for the following in the system compounds per- reasons: formance issues. This point is paramount. It’s not uncommon to I The memory configuration is install Exchange and have it work below the recommended mini- without issue for three months mum for the database cache. For only to have things go wrong in an organization that sends and that fourth month, for instance. DEFINITIVE GUIDE TO EXCHANGE SERVER 2010 MIGRATION • SEARCHEXCHANGE.COM 4
CHAPTER 5: EXCHANGE 2010: KEEPING UP APPEARANCES TABLE 2: Tools to Help Properly Size Exchange 2010 Server Roles I Microsoft Exchange 2010 Mailbox Server Role Calculator A tool to correctly size storage and memory HOME I HP Sizer for Microsoft Exchange Server 2007 Server sizing and configuration tool for Exchange 2007 on HP servers FOUR PILLARS I Dell’s Exchange 2010 Advisor OF EXCHANGE Server sizing tool for Exchange 2010 on Dell servers 2010 DESIGN When this happens, review sizing list in its entirety, slow response PERFORMANCEISSUES, TWEAKS configurations that were set dur- times in Microsoft Outlook andAND MITIGATION ing the initial installation. Outlook Web App are the two most common user complaints. A well-designed Exchange 2010 Outlook and OWA issues generallyEXCHANGE 2010 configuration for the same company stem from an underlying hardware MANAGEMENTBEST PRACTICES might look similar to that on the configuration or sizing problem such right-hand side of Table 1 on page 4. as choosing the wrong disk subsys- Before building your Exchange tem RAID level or improperly sizing 2010 infrastructure, I recommend the amount of RAM/CPU cores to that you review a number of re- the designated user. However, it sources to help you scale and trou- may take some work to pinpoint the bleshoot your environment. Table 2 exact source. In a number of circum- above outlines some valuable tools stances, user load may have grown from Microsoft and from third-party beyond the expectations of the orig- vendors as well as reference materi- inal design, which places significant als on sizing each of the five demand on hardware resources. Exchange 2010 server roles. When a performance issue arises, Outlook users will generally receive an error message stating, “Micro- PERFORMANCE ISSUES, soft Outlook is requesting data from TWEAKS AND MITIGATION the server.” A slow, unresponsive or Configuration problems can not only frozen Outlook interface typically affect the performance of your accompanies the message. Often, Exchange infrastructure but also administrators don’t know there’s a trickle down to the user. And while problem until OWA users report it. the list of possible Exchange 2010 And the more users you have performance problems is too long to reporting this problem, the more DEFINITIVE GUIDE TO EXCHANGE SERVER 2010 MIGRATION • SEARCHEXCHANGE.COM 5
CHAPTER 5: EXCHANGE 2010: KEEPING UP APPEARANCES likely an underlying infrastructure cy. So, for example, if Outlook is configuration is to blame. freezing and users receive a number To troubleshoot this problem, of failures in the Req/Fail column have the user hold down the CTRL and high values in the Avg Resp col- key and navigate to the Outlook icon umn, this suggests a wider network- in the Windows notification area. ing issue, specifically with Exchange HOME Select Connection Status from the servers and domain controllers. context menu to open a connectivity In this situation and to avoid suf- FOUR PILLARS diagnostics window. fering from network latency in the OF EXCHANGE If, for example, a user complains future, ensure that Exchange servers 2010 DESIGN that Outlook froze when he opened have fast, reliable links to domain the Global Address List and then controllers and to the client network. failed to display the address list, the Don’t use Auto-Negotiation at the PERFORMANCEISSUES, TWEAKS output in this diagnostics window server or switch-port level on net-AND MITIGATION can offer a clue as to why. In this work interface cards; as a minimum, particular instance, the Req/Fail each adapter should be hard-set at section of Directory Type requests 100 MB full duplex or faster. OnEXCHANGE 2010 shows one failure, which suggests large networks, it is good practice to MANAGEMENTBEST PRACTICES that Exchange Server is having diffi- separate server traffic from client culty communicating with one of its traffic using virtual LANs (VLANs). domain controllers. If you suspect there’s a problem with your domain controllers or global catalog, you EXCHANGE 2010 MANAGE- can use Microsoft’s Dcdiag tool to MENT BEST PRACTICES pinpoint Active Directory issues. When managing Exchange servers, You can also use the connectivity you should love and care for them status box to troubleshoot other net- as if they were your own children. work-based problems such as laten- (Continued on page 8) Looking for Help? BEFORE BUILDING YOUR Exchange 2010 environment, review these resources to help properly scale your infrastructure or troubleshoot problems. I Understanding Processor Configurations and Exchange Performance I Understanding Memory Configurations and Exchange Performance I Understanding Server Role Ratios and Exchange Performance I Understanding the Mailbox Database Cache DEFINITIVE GUIDE TO EXCHANGE SERVER 2010 MIGRATION • SEARCHEXCHANGE.COM 6
CHAPTER 5: EXCHANGE 2010: KEEPING UP APPEARANCESTABLE 3: Exchange Server 2010 Management and UpkeepProcess Frequency Description RequirementInspect physical Daily Review the physical state of the kit Mandatoryhardware that comprises your Exchange serversCheck backups Daily Check the status of backups MandatoryReview all Twice Review the contents of the system, Once isevent logs a day application and security logs on each mandatory; Exchange server twice is optionalReview disk Daily Check available space on transaction logs, Mandatoryspace databases and system LUNsReview transac- Daily Ensure that the number of transaction logs Mandatorytion log growth being produced is in line with daily metricReview transport Twice Check the volume of mail within the trans- Mandatoryqueues a day port queues and review any anomaliesRun Exchange Best Twice a Review configuration information and MandatoryPractices Analyzer month recommendationsReview server mail- Daily Ensure that mailbox servers aren’t over- Mandatorybox distribution loaded with over-capacity mailboxesReview DAG Twice Check the number of logs in the copy and Mandatoryreplication status a day peplay queues (DAG configurations only)Run PerfMon Monthly Run performance monitoring using Ex- Optional change Management Console for two hours a month to view usage trendsMaintain a Daily Log all current configuration settings to a Mandatoryconfiguration log digital log, (i.e.,configuration management)Log all changes via As Log, evaluate, plan, test and implement Mandatorya change-control required all changes to ExchangeprocessPenetration testing Twice Have a third party test the overall Varies according a year viability and security of your Exchange to industry infrastructure DEFINITIVE GUIDE TO EXCHANGE SERVER 2010 MIGRATION • SEARCHEXCHANGE.COM 7
RESOURCES FROM OUR SPONSOR• Exchange 2010: Performance Enhancement• Hosting vs. In-House Implementation of Exchange 2010: It’s Decision Time• Presentation Transcript: Exchange 2010 Roadmap Series - Transition and MigrationAbout Dell, Inc. and Intel:Dell and Intel have worked together for years to bring you end-to-end solutions that improvebusiness productivity, increase performance and reduce your total cost of ownership (TCO)across the enterprise.