Microsoft Exchange 2007 各個角色伺服器的效能監控資訊

Microsoft Exchange 2007 各個角色伺服器的效能監控資訊，請參考以下表格內容：

Client Access Server

=====

Counter	Expected values	Monitor duration
LogicalDisk(_Total)\Disk Reads/sec Indicates that a paging situation may exist because data was read from disk instead of memory.	Should be less than 50 at all times. Disk Writes/sec + Disk Reads/sec = <>	2 Hr
LogicalDisk(_Total)\Disk Writes/sec Indicates that a paging situation may exist because data was written to disk instead of being stored in memory.	Should be less than 50 at all times. Disk Writes/sec + Disk Reads/sec = <>	2 Hr
MSExchange OWA\Average Response Time Shows the average time (in milliseconds) that elapsed between the beginning and end of an OEH or ASPX request. Used to determine the latency that a client is experiencing.	Should be less than 100 ms at all times. Higher values may indicate high user load or higher than normal CPU time.	4 Hr
MSExchange OWA\Average Search Time Shows the average time that elapsed while waiting for a search to complete.	Should be less than 31,000 ms at all times.	4 Hr
MSExchangeFDS:OAB(*)\Download Task Queued Shows a value of 1 if the task is queued for execution, otherwise shows 0.	Should be 0 at all times. Values greater than 0 indicate a failure to copy OAB data files from Mailbox servers.	1 Day
MSExchangeFDS:OAB(*)\Download Tasks Completed Shows the number of OAB download tasks completed since the File Distribution service started. The default value is every 480 minutes or 8 hours.	Should be less than or equal to 3 per day. Values greater than 3 per day indicate the schedule for the Client Access server to download updated OAB files is not a default schedule.	1 Day

Mailbox Server

=====

Counter	Expected values	Monitor duration
Performance counters for database disks LogicalDisk(*)\Avg. Disk sec/Read PhysicalDisk(*)\Avg. Disk sec/Read Shows the average time, in seconds, of a read of data from the disk. Note: When looking at disks using Perfmon.exe, an understanding of the underlying disk subsystem is key to determining which counters (physical disk or logical disk) to look at. Windows Clustering can use volume mount points to overcome the 26-drive limitation of the operating system, so drives may show up as numbers indicating physical disks rather than having drive letters.	Should be below 20 milliseconds (ms) at all times on average. For servers with more than 1,000 users, 20-ms disk times may not be fast enough to return responses to the client to accommodate user load. Check remote procedure call (RPC) averaged latencies to ensure these are within recommended values and adjust the disk subsystem for increased I/Os.	2 Hr
Performance counters for database disks LogicalDisk(*)\Avg. Disk sec/Write PhysicalDisk(*)\Avg. Disk sec/Write Shows the average time, in seconds, of a write of data to the disk. Note: When looking at disks using Perfmon.exe, an understanding of the underlying disk subsystem is key to determining which counters (physical disk or logical disk) to look at. The Cluster service can use volume mount points to overcome the 26-drive limitation of the operating system, so drives may show up as numbers indicating physical disks rather than having drive letters.	Should be below 100 ms at all times on average. If disk writes are high, it is possible that read latencies are also affected as a direct correlation with high write times.	2 Hr
Performance counters for log disks LogicalDisk(*)\Avg. Disk sec/Read Shows the average time, in seconds, of a read of data from the disk.	Should be below 20 ms on average.	2 Hr
Performance counters for log disks LogicalDisk(*)\Avg. Disk sec/Write Shows the average time, in seconds, of a write of data to the disk. Note: Processes such as sync replication can increase latencies for this counter.	Should be below 10 ms on average.	2 Hr
MSExchangeIS\RPC Requests Indicates the overall RPC requests that are currently executing within the information store process. The maximum value in Exchange 2007 is 500 RPC requests that can execute at any designated time before the information store starts rejecting any new connections from clients.	Should be below 70 at all times.	2 Hr
LogicalDisk(*)\Avg. Disk sec/Read Shows the average time, in seconds, of a read of data from the disk.	Should be below 10 ms on average. Spikes (maximum values) should not be higher than 50 ms.	2 Hr
LogicalDisk(*)\Avg. Disk sec/Write Shows the average time, in seconds, of a write of data to the disk.	Should be below 10 ms on average. Spikes (maximum values) should not be higher than 50 ms.	2 Hr
MSExchangeIS\RPC Requests Indicates the overall RPC requests that are currently executing within the information store process. The maximum value in Exchange 2007 is 500 RPC requests that can execute at any designated time before the information store starts rejecting any new connections from clients.	Should be below 70 at all times.	2 Hr
MSExchangeIS\RPC Averaged Latency Indicates the RPC latency, in milliseconds, averaged for all operations in the last 1,024 packets. For information about how clients are affected when overall server RPC averaged latencies increase, see RPC Client Throttling.	Should not be higher than 25 ms on average. To determine if certain protocols are causing overall RPC latencies, monitor MSExchangeIS Client (*)\RPC Average Latency to separate latencies based on client protocol. Cross-reference MSExchangeIS\RPC Client Backoff/sec to ensure higher latencies are not causing client throttling.	2 Hr
MSExchangeIS Mailbox(_Total)\Messages Queued for Submission Shows the current number of submitted messages that are not yet processed by the transport layer.	Should be below 50 at all times. Should not be sustained for more than 15 minutes. This may indicate that there are connectivity issues to the transport servers or that backpressure is occurring.	0.5 Hr
MSExchangeIS Public(_Total)\Messages Queued for Submission Shows the current number of submitted messages that are not yet processed by the transport layer.	Should be less than 20 at all times.	1 Hr
MSExchange Database(Information Store)\Version buckets allocated Shows the total number of version buckets allocated. The maximum default version is 16,384. If version buckets reach 70 percent of maximum, the server is at risk of running out of the version store.	Should be less than 12,000 at all times.	All Time
MSExchange Replication(*)\CopyQueueLength Shows the number of transaction log files waiting to be copied to the passive copy log file folder. A copy is not considered complete until it has been checked for corruption. Note: Both nodes of the cluster continuous replication (CCR) clusters should be monitored for this counter depending on the passive node.	Should be less than 10 at all times for CCR. Should be less than 1 at all times for local continuous replication (LCR).	1 Hr
MSExchange Replication(*)\ReplayQueueLength Shows the number of transaction log files waiting to be replayed into the passive copy. Note: Both nodes of the CCR clusters should be monitored for this counter depending on the passive node.	Indicates the current replay queue length. Higher values cause longer store mount times when a handoff, failover, or activation is performed.	1 Hr

HUB Transport Servers

=====

Counter	Expected values	Monitor duration
Logical/Physical Disk(*)\Avg. Disk sec/Read Shows the average time, in seconds, of a read of data from the disk.	Should be less than 20 milliseconds (ms) on average. Spikes (maximum values) should not be higher than 50 ms.	2 Hr
Logical/Physical Disk(*)\Avg. Disk sec/Write Shows the average time, in seconds, of a write of data to the disk.	Should be less than 20 ms on average. Spikes (maximum values) should not be higher than 50 ms.	2 Hr
\MSExchangeTransport Queues(_total)\Aggregate Delivery Queue Length (All Queues) Shows the number of messages queued for delivery in all queues.	Should be less than 3,000 and not more than 5,000.	0.5 Hr
\MSExchangeTransport Queues(_total)\Active Remote Delivery Queue Length Shows the number of messages in the active remote delivery queues.	Should be less than 250 at all times	0.5 Hr
\MSExchangeTransport Queues(_total)\Active Mailbox Delivery Queue Length Shows the number of messages in the active mailbox queues.	Should be less than 250 at all times.	0.5 Hr
\MSExchangeTransport Queues(_total)\Submission Queue Length Shows the number of messages in the submission queue.	Should not exceed 100. If sustained high values are occurring, investigate Active Directory and Mailbox servers for bottlenecks or performance-related issues.	0.5 Hr
\MSExchangeTransport Queues(_total)\Active Non-Smtp Delivery Queue Length Shows the number of messages in the Drop directory that is used by a Foreign connector.	Should be less than 250 at all times.	2 Hr
\MSExchangeTransport Queues(_total)\Retry Mailbox Delivery Queue Length Shows the number of messages in a retry state attempting to deliver a message to a remote mailbox.	Should be less than 100 at all times.	2 Hr
\MSExchangeTransport Queues(_total)\Retry Non-Smtp Delivery Queue Length Shows the number of messages in a retry state in the non-Simple Mail Transfer Protocol (SMTP) gateway delivery queues.	Should not exceed 100.	2 Hr
\MSExchangeTransport Queues(_total)\Retry Remote Delivery Queue Length Shows the number of messages in a retry state in the remote delivery queues.	Should not exceed 100. We recommend that you check the next hop to determine the causes for queuing.	2 Hr
\MSExchangeTransport Queues(_total)\Unreachable Queue Length Shows the number of messages in the Unreachable queue.	Should not exceed 100.	2 Hr
\MSExchangeTransport Queues(_total)\Largest Delivery Queue Length Shows the number of messages in the largest delivery queues.	Should be less than 200 for the Edge Transport and Hub Transport server roles.	2 Hr
\MSExchangeTransport Queues(_total)\Poison Queue Length Shows the number of messages in the poison message queue.	Should be 0 at all times.	2 Hr