|
Guy recommends :
Find out which of your VMs are a waste of space and which VMs need more resources.
|
Microsoft Exchange 2003 - Monitoring Memory PerformanceIntroduction to Exchange 2003 Server - Monitoring Memory PerformanceThe 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
As you monitor your Exchange 2003 server, here are key questions to ask.
Guy Recommends a Free Tool: VM Console
|
||||||||||||||||||||||||||
Performance Object |
Critical Value |
| Memory \Available Bytes | Greater than 10 MB |
| Memory \Pages Sec | Not more than 50 \ Sec |
| Memory \Pool Nonpaged Bytes | Above 100MB indicates a problem |
| Memory \Free System Page | |
| Process \Store \ Virtual Bytes | Less than 2.5 GB (With /3GB) Less than 1.5 GB (no /3GB switch) |
| MSExchangeIS \ VM Largest Block size | More than : 150 MB ~ 150,000,000 bytes |
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.
Guy Recommends:
The SolarWinds Exchange MonitorHere 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
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.
Cluster Specific counters |
|
MSExchangeIS |
A healthy server has more than 200 MB free. Less than 10 MB you get Event ID 9582. |
MSExchangeIS |
Less than 3 indicates a problem. |
MSExchangeIS |
Less then 32 MB. Suggest restart Node on Cluster. Failover first. |
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.
*
Custom Search
|
SolarWinds Exchange Monitor
|
|
Home Copyright © 1999-2012 Computer Performance LTD All rights reserved Please report a broken link, or an error. | |