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
- Exchange 2010 Performance Monitor
- 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)
- 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.
Here is a free tool to monitor your Exchange Server. Download and install the utility, then inspect your mail queues, monitor the Exchange server’s memory, confirm there is enough disk space and check the CPU utilization.
This is the real deal – there is no catch. SolarWinds provides this fully-functioning freebie, as part of their commitment to supporting the network management community.
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
- 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 SolarWinds’ Free Network Monitor
Thus utility makes it easy to check the health of a router or firewall. Check the real-time performance, and availability statistics, for any device on your network. Get started with an extensive collection of "out-of-the-box" monitors for popular network devices. Give Network Monitor a whirl – it’s free. Download your free Network Device Monitor
If you need more comprehensive network analysis software:
Download a free trial of NPM (Network Performance Monitor)
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.
If you like this page then please share it with your friends
More Help for Detecting Computer Bottlenecks