Performance Documentation

 <  Day Day Up  >  

Performance documentation helps monitor the health and status of the Exchange environment. It is a continuous process that begins by aligning the goals, existing policies, and service level agreements of the organization. When these areas are clearly defined and detailed, baseline performance values can be established, using tools such as the System Monitor, Microsoft Operations Manager (MOM), or third-party tools (such as PerfMon or BMC Patrol). These tools capture baseline performance- related metrics that can include indicators such as how much memory is being used, average processor use, and more. They also can illustrate how the Exchange Server 2003 environment is performing under various workloads.

After the baseline performance values are documented, performance-related information gathered by the monitoring solution should be analyzed periodically. Pattern and trend analysis reports need to be examined at least on a weekly basis. This analysis can uncover current and potential bottlenecks and proactively ensure that the system operates as efficiently and effectively as possible. These reports can range from routine reports generated by the monitoring solution to complex technical reports that provide detail to engineering staff.

Routine Reporting

Although built-in system monitoring tools log performance data that can be used in reports in conjunction with products such as Microsoft Excel, it is recommended that administrators use products such as MOM for monitoring and reporting functionality. MOM can manage and monitor the Exchange systems and provide preconfigured graphical reports with customizable levels of detail. MOM also provides the framework to generate customized reports that meet the needs of the organization.

Management-Level Reporting

Routine reporting typically provides a significant amount of technical information. Although helpful for the administrator, it can be too much information for management. Management-level performance reporting should be concise and direct. Stakeholders do not require the specifics of performance data, but it's important to take those specifics and show trends, patterns, and any potential problem areas. This extremely useful and factual information provides insight to management so that decisions can be made to determine proactive solutions for keeping systems operating in top- notch condition.

For instance, during routine reporting, administrators identify and report to management that Exchange Server processor use is on the rise. What does this mean? This information by itself does not give management any specifics on what the problem is. However, if the administrator presents graphical reports that indicate that if the current trends on Exchange Server processor use continue at the rate of a 5% increase per month, an additional processor will be required in 10 months or less. Management can then take this report, follow the issue more closely over the next few months, and determine whether to allocate funds to purchase additional processors. If the decision is made to buy more processors, management has more time to negotiate quantity, processing power, and cost instead of having to pay higher costs for the processors on short notice.

Technical Reporting

Technical performance information reporting is much more detailed than management-level reporting. It goes beyond the routine reporting to provide specific details on many different components and facets of the system. For example, specific counter values might be given to determine disk subsystem use. This type of information is useful in monitoring the health of the entire Exchange environment. Trend and pattern analysis should also be included in the technical reporting process to not only reflect the current status, but to allow comparison to historical information and determine how to plan for future requirements.

 <  Day Day Up  >  


Microsoft Exchange Server 2003 Unleashed
Microsoft Exchange Server 2003 Unleashed (2nd Edition)
ISBN: 0672328070
EAN: 2147483647
Year: 2003
Pages: 393
Authors: Rand Morimoto

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net