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.
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:
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.
Guy Recommends:
The SolarWinds Exchange Monitor
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 product for free, 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
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.
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
Learn
the secrets of which counters to monitor. Master performance monitor
logging, develop your skills with structured exercises and examples. Print
out a copy to read, while you design logs and alerts to detect network bottlenecks.
*
Custom Search
Guy Recommends: Orion's NPM - Network Performance Monitor
Orion's performance monitor is designed for detecting network outages. NPM makes it easy to see what's working, and what needs your attention.
This utility guides you through creating network maps. It also helps troubleshooting by indicating whether the root cause is faulty equipment, or resource overload.
Learn
the secrets of which counters to monitor. Master performance monitor
logging, develop your skills with structured exercises and examples. Print
out a copy to read, while you design logs and alerts to detect network bottlenecks.
