Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Standard view
Full view
of .
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1
3 Exchange Server 2003 Scheduled Maintenance Tasks

3 Exchange Server 2003 Scheduled Maintenance Tasks

Ratings: (0)|Views: 396|Likes:
Published by api-3852474

More info:

Published by: api-3852474 on Oct 19, 2008
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less





Exchange Server 2003 Scheduled Maintenance Tasks
Exchange Server 2003 Operations Guide
Exchange Server 2003 Scheduled Maintenance Tasks

By performing scheduled monitoring of your Microsoft\u00ae Exchange servers, you can collect the data required for
trend analysis and capacity planning. The information that you gather from scheduled monitoring will help you
characterize system performance over time. You can use this information to plan resources before a critical
need comes up, document tasks and processes that are common for your Exchange organization, and
troubleshoot your servers. Performing the following scheduled maintenance tasks ensures that your Exchange
servers run smoothly and efficiently:

\u2022Generating reports and identifying trends
\u2022Reviewing protocol logs
\u2022Monitoring Microsoft Office Outlook\u00ae Web Access servers
\u2022Managing mailboxes
\u2022Managing the BadMail folder
\u2022Managing the postmaster mailbox
\u2022Conducting weekly status meetings

Generating Reports and I dentifying Trends

To ensure that Microsoft Exchange Server 2003 runs efficiently and with minimal downtime, you must gather enough information to establish a baseline for the performance of your server. By gathering the appropriate information, you can proactively manage your Exchange Server 2003 messaging system and perform trend analysis and capacity planning. You must create a baseline when you first deploy your server and then re- create the baseline any time a change in hardware or workload occurs, such as a significant change in the number of users. For more information about the factors that affect performance and for recommendations about how to optimize your Exchange Server 2003 environment, see the Exchange Server 2003 Performance

and Scalability Guide(http: / / go.microsoft.com/ fwlink/ ?LinkId= 28660). This guide is a companion to the
Exchange Server 2003 High Availability Guide (http: / / go.microsoft.com/ fwlink/ ?linkid= 30251). As you plan
your Exchange 2003 deployment, review both guides to help you design and optimize your environment.
This section gives you guidelines for the following tasks:
\u2022Monitoring and measuring tasksProvide procedures for system monitoring and system measurement.
http://www.microsoft.com/technet/prodtechnol/exchange/g...Guide/41bddd59-d365-4f86-b644-fa1b1efcb2db.mspx?pf=true (1 of 11)25/01/2005 10:01:17
Exchange Server 2003 Scheduled Maintenance Tasks
\u2022Capacity planningEstablish baselines for each service and monitor all levels of system operations.
\u2022Capturing and reporting performance dataRecord and log system activity over time, chart the activity
in real time, and display information that is in log files.
\u2022Analyzing trendsCapture data and analyze the reports that you create by using that data.
Guidelines for Monitoring and Measurement
At a minimum, you must create procedures for the following monitoring and measurement tasks:
\u2022System monitoringThese procedures must include information about server resources that must be
monitored, including memory, processor usage, hard disk space and disk performance, and network

performance. Additionally, Exchange-specific performance indicators, such as Exchange store performance,
message delivery rates, and message queue problems must be included. Each of these procedures must
specify the frequency of monitoring tasks, the baseline or expected data to be captured, and the appropriate
escalation procedures for managing problems as they occur.

\u2022System measurementThese procedures work with system monitoring procedures and must include
standards for the types of information measured, the measurement sampling rate, the equations to use when
you analyze data, the formats to store the data in, and the formats to use for reporting.
Guidelines for Capacity Planning

Capacity planning is the allocation and monitoring of system resources to ensure that optimal system
performance is maintained as the system load increases. To provide capacity planning, you must establish
baselines for each service, and then continually monitor all levels of system operations. For example, make
sure that you plan carefully before significantly increasing the number of users supported on a server that is
running Exchange Server 2003; otherwise, the increased user load may decrease performance and overload
both hard disk resources and other system resources. You can use the following capacity planning tools:

\u2022Capacity Planning and Topology CalculatorThe Capacity Planning and Topology Calculator helps you
determine the size of the servers you need for your Exchange 2000 Server or Exchange Server 2003 topology.
\u2022Exchange Server Load Simulator (LoadSim.exe) 2003You can simulate the load of MAPI clients
against Exchange by running LoadSim tests on client computers. These tests send messaging requests to the
Exchange server, causing a load on the server.
\u2022Exchange Stress and Performance (Esp.exe)The Exchange Stress and Performance tool is a highly
scalable stress and performance tool for Exchange Server. It simulates large numbers of client sessions by
concurrently accessing one or more protocol services.
\u2022Jetstress (Jetstress.exe)Jetstress is a tool in Exchange Server to help administrators verify the
performance and stability of the disk subsystem before putting their Exchange server into production.
Important :
Because some of these tools create accounts that have non-secure passwords, these tools are intended for use
in test environments, not in production environments.
http://www.microsoft.com/technet/prodtechnol/exchange/g...Guide/41bddd59-d365-4f86-b644-fa1b1efcb2db.mspx?pf=true (2 of 11)25/01/2005 10:01:17
Exchange Server 2003 Scheduled Maintenance Tasks
For more information about capacity planning, see the Planning an Exchange Server 2003 Messaging System
Guide(http: / / go.microsoft.com/ fwlink/ ?LinkId= 21766).
Guidelines for Capturing and Reporting Performance Data
Use Performance Monitor (Perfmon.msc) to provide information about performance objects and related
counters. The Performance Monitor console contains two snap-ins\u2014Performance Log and Alerts and System
Monitor. To provide the required information, do the following tasks:
\u2022Record and log system activity over time by using Performance Logs and Alerts. You collect data to analyze
performance and usage. To use Performance Monitor to generate reports, you must do the following:
\u2022Configure Performance Logs and Alerts to collect data for the recommended counters at set intervals, such
as every 10 to 15 minutes.
\u2022Capture performance data.
\u2022Retain logs over extended periods of time by storing data in an archive with performance log files on the
hard disk or in a database such as Microsoft Access or Microsoft SQL Server\u2122. If you store the data in a
database, you can use the reporting features of those programs to create complex reports that you can use
to assess overall performance, do trend analysis, and do capacity planning.
\u2022Chart activity in real time and display information that is in log files by using System Monitor. System Monitor
is a Microsoft Management Console (MMC) snap-in that you can use to monitor many subsystems and
software. It provides a common infrastructure for reporting data based on performance counters. For more
information about System Monitor, see Windows\u00ae Help. You can use System Monitor to do the following

\u2022View server activity when server performance is decreased.
\u2022Analyze processor activity and queues, which is useful in isolating problems with specific components.
\u2022Display logs of captured performance data viewed as reports, graphs, or histograms.

For more information about the tools you can use to verify the performance of your Exchange Server 2003
environment, see "Exchange Performance Tools" in Appendix A of the Exchange Server 2003 Performance and
Scalability Guide(http: / / go.microsoft.com/ fwlink/ ?LinkId= 28660).
Guidelines for Analyzing Trends

By capturing data and analyzing the reports you create by using that data, you can find patterns and predict
future trends. This trend analysis allows you to be proactive in determining how to manage your Exchange
servers in the future. For example, by analyzing the current usage on your Exchange server, you can predict
when normal growth, such as mailbox growth, will require that you upgrade your storage. For more
information about setting baselines and analyzing trends, see the Troubleshooting Exchange Server 2003

Performance guide (http: / / go.microsoft.com/ fwlink/ ?LinkId= 22811).
Top of page
http://www.microsoft.com/technet/prodtechnol/exchange/g...Guide/41bddd59-d365-4f86-b644-fa1b1efcb2db.mspx?pf=true (3 of 11)25/01/2005 10:01:17

Activity (5)

You've already reviewed this. Edit your review.
1 hundred reads
1 thousand reads
prashaachar liked this
dgsampey liked this
imboise liked this

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->