Microsoft Exchange 2003 - Monitoring Memory Performance

Introduction to Exchange 2003 Server - Monitoring Memory Performance

The good news is that Exchange 2003 server does a first class job of monitoring memory automatically.  Improving upon the default is like playing a computer at chess, the best experts can win, but ordinary mortals will be beaten.  However, because memory usage is so often the server bottleneck, it's well worth analyzing available bytes and paging.

Topics for Monitoring Memory Performance in Exchange 2003 Server

• Memory - Number one Exchange Bottleneck
• Performance Monitor Guidelines
• Solutions to Memory problems
• Cluster - Memory
• See Also  /3GB and USERVA = 3030

 ♠

Memory - Number one Exchange Bottleneck

From time immemorial, memory has been the first place to look for a bottleneck on a mail server.  This Exchange service, which consumes the most memory, has various names, Store.exe, Information Store, MSExchangeIS.

As you monitor your Exchange 2003 server, here are key questions to ask.

1. Does my server have enough RAM?  If not, what can I do?
2. How can I make the best use of available memory?
3. What are the basic memory counters?  Should I bother with additional process and MSExchangeIS counters?
4. What are the performance figures for other servers?

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.

Free Download of SolarWinds Exchange Monitor

Performance Monitor Guidelines

I have selected critical performance objects and counters to help you analyze memory usage on Exchange 2003 server.  Whilst I provide critical values, always keep in mind the broader picture, for example, is this just a spike or is it continuous high value?

My advice is to try a short test Performance Log for say 10 minutes.  Sampling at 30 second intervals to begin with.  As a result of feedback from this pilot study, remove counters that yielded inconclusive data and re-record the log for between 2 and 8 hrs, but at 5 minute intervals.  For more guidance on getting started check creating a performance log

Solutions to Memory problems

Exchange 2003 has the best ever virtual memory manager.  In particular, it reduces memory fragmentation and increases availability, as a result Exchange 2003 can support more users than ever.  Here are some rough figures to illustrate my point, Exchange 5.5 - 500 users, Exchange 2000 - 1,000, Exchange 2003 - 1,500.

1. Up to a point, memory problems are straightforward to solve, just add another stick of RAM.  Once you get above 1GB of RAM then consider tuning boot.ini.  Here is where you can configure the /3GB switch.
2. If, for what ever reason, you do not wish to add more RAM then its time to think laterally.
3. Can you offload service onto another server?  For example keep Exchange on the monitored server, but move SQL, Active Directory or other competing programs to another server.
4. Could it be time for another Exchange server?  Either an additional back-end server, or a front-end server for OWA clients.

Guy Recommends:  A Free Trial of the Orion Network Performance Monitor (NPM) v10

Solarwinds' Orion performance monitor will help you discover what's happening on your network.  Also this utility will guide you through troubleshooting; the dashboard will indicate whether the root cause is a broken link, faulty equipment or resource overload.  Because it produces network-centric views, the NPM is intuitive to navigate, and you can export the results to Microsoft Visio.

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 v10 to notify members of your team what's changed and how to fix it.

If you are interested in troubleshooting, and creating network maps, then I recommend that you take advantage of Solarwinds' offer and download a free trial of Orion's Network Performance Monitor.

Cluster Memory

Virtual Servers in Clusters may suffer from memory fragmentation.  You may get conformation of a problem by finding Monitor Event ID 9582 in the Application Log (Event Viewer).

Once again, monitor counters under MSExchangeIS to confirm or deny problems with cluster memory.

Guy Recommends:  A Free Trial of the Orion Network Configuration Monitor (NCM) v6

Config management of routers, switches and firewalls is fun with NCM (Network Configuration Manager.  Furthermore, it can help to achieve your compliance policy, for example, pinpoint devices not backed up and discover access infringements or even weak passwords.  This Solarwinds NCM suite can not only detect violations, but also upload scripts to correct the problem.

Most computer problems arise from configuration changes.  Thus it makes sense to get a proper monitoring system so that you can double-check that that all the settings confirm to your security policy.

Download your free trial of Orion's Network Configuration Monitor.

Summary - Memory Monitoring

Exchange server 2003 is greedy for memory.  Performance monitoring will not only check for bottlenecks but also help you understand how memory management works.  Get started and create log and check your data against my guidelines for critical values.

See Also

• Free Tool to Monitor Your Exchange Server
• Performance Monitoring - Overview
• Memory Monitoring
• Disk Monitoring
• Processor Monitoring
• Network Monitoring
• Syslog Analyzer - Free Utility
• ExBPA - Best Practice Analyzer
• /3GB and USERVA = 3030
• Resource Monitoring
• Queue and Message Tracking

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

Please report a broken link, or an error.