Performance Monitor - Exchange 2003

Introduction to Exchange 2003 Bottlenecks

When you install Exchange 2003, not only does it expand the schema but it also adds specific exchange performance counters.  Incidentally, you also see more services, for example Microsoft Exchange System Attendant.

As you look for bottlenecks, think how you could improve the service as cheaply as possible, for example move mailboxes to another server.

Exchange Performance Topics

• Tactics to Detect Bottlenecks
• Monitor Queues
• Other Exchange Counters
• Solutions to Exchange bottlenecks
• Summary of Exchange Performance Monitoring

 ♦

Tactics to Detect Bottlenecks

Firstly remember best practice and monitor the Windows Server 2003 'big four' counters, memory, processor, disk and network.  Next look for specific Exchange bottlenecks in these areas:

• MTA (Message Transfer Agent)
• SMTP
• Internet Mail Service
• Directory Service

The more you understand the way Exchange 2003 works, the more you can identify then predict where bottlenecks occur.  Performance monitor will help you not only improve responsiveness, but also show you how the Exchange components route the mail messages.

Monitor Queues

The key to detecting Exchange 2003 bottlenecks is to find, then measure queues.  Guy's rule of thumb is a queue bigger than 2 is evidence of a bottleneck.

MSExchangeMTA - Work Queue Length

This is the most important counter because it gives the total of all queues.

For more precise queue monitoring check

• SMTP Server -Local Queue Length
• SMTP Server Messages received /sec and  delivered /sec
• MSExchangeMTA Connections - Queue Length
• MSExchangeIS - Send and Receive queues size
• MSExchangeIS Mailbox -Messages Sent/min Messages Delivered/min
• MSExchangeIS User Count

Solutions to Exchange 2003 Bottlenecks

• Increase memory, add another stick of RAM.
• More disks, with more disk controllers.
• Put Exchange on its own dedicated server.
• Add a second or third server so that each site has a local Exchange server.
• Deploy front-end / back-end servers.  The front-end servers handle the connections and authentication, the back-end store the actual mailboxes.
• Lateral thinking and root cause analysis.  Too much spam, get a good filter, swamped with the SoBig virus, better virus checker.

Guy Recommends:  The Orion Network Performance Monitor (NPM) 9.5

Orion's performance monitor is designed for detecting network outages.  This NPM will guide you through troubleshooting by indicating whether the root cause is a broken link, faulty equipment or resource overload.  Because it produces network-centric views, it is intuitive to navigate, and as result you can see easily what's working and what's not.

Perhaps Orion's best feature is the way it suggests solutions.  Moreover, if problems arise out of the blue, then you can configure Orion NPM 9.5 to notify members of your team what's changed and how to fix it.

If you are interested in testing a professional performance monitor on your network, then I recommend that you take advantage of Solarwinds' offer of a download a free trial of Orion's Network Performance Monitor.

Summary to Exchange Health Checks

Monitoring Exchange Servers is probably the most difficult of all monitoring tasks.  The secret is to start by examining the Windows Server 2003 'big 4' counters, Memory, Processor, Disk and Network.  Once you have checked that they are not causing the bottleneck, then seek the Exchange specific counters, for example, MSExchangeIS  and MSExchangeMTA.

More Help for Detecting Computer Bottlenecks

Home Copyright © 1999-2009 Computer Performance LTD All rights reserved

Please report a broken link, or an error.