Sizing Guide Exchange Server 2003 - Fujitsu

More documents

Recommendations

Info

White Paper Sizing Guide Exchange Server 2003 Version: 4.2, July 2006 Performance analysis Windows and applications such as Exchange Server provide performance counters for all relevant components. These performance counters can be viewed, monitored and recorded through a standardized interface with the performance monitor that is available in all Windows versions – also known as system monitor in some Windows versions. The performance monitor can be found under the name »Performance« in the start menu under »Administrative Tools«. It can also be started using the short command »perfmon«. Performance counters are grouped in an object-specific manner, some of them also exist in various instances when an object is available several times. For example, there is a performance counter, »%Processor Time«, for the object »Processor«, with one instance per CPU for a multi-processor system. Not all performance counters are already available in Windows, and many applications, such as Exchange Server, come with their own performance counters, which integrate in the operating system and can be queried through the performance monitor. The performance data can either be monitored on screen or, better, written in a file and analyzed offline. Not only can performance counters of the local system be evaluated but also of remote servers, which necessitate appropriate access rights. How to use the performance monitor is described in detail in Windows help or in Microsoft articles in the Internet, and there is also an explanation of each individual performance counter under »Explain«. Please note that the performance monitor is also a Windows application that needs computing time. It is possible with an extreme server overload for the performance monitor itself not to be able to determine and show any performance data; in this case the relevant values are then 0 or blank. To obtain an overview of the efficiency of an Exchange Mailbox Server it is sufficient to observe a number of performance counters from the categories: Processor Memory Logical Disk MSExchangeIS SMTP Server In detail there are the following performance counters: \\\Processor(_Total)\% Processor Time \\\System\Processor Queue Length \\\Memory\Available MBytes \\\Memory\Free System Page Table Entries \\\Memory\Pages/sec \\\LogicalDisk(:)\Avg. Disk Queue Length \\\LogicalDisk(:)\Avg. Disk sec/Read \\\LogicalDisk(:)\Avg. Disk sec/Write \\\LogicalDisk(:)\Disk Reads/sec \\\LogicalDisk(:)\Disk Writes//sec \\\MSExchangeIS Mailbox(_Total)\Send Queue Size \\\MSExchangeIS\RPC Averaged Latency \\\MSExchangeIS\RPC Requests \\\MSExchangeIS\VM Total Large Free Block Bytes \\\SMTP Server(_Total)\Local Queue Length \\\SMTP Server(_Total)\Remote Queue Length Depending on the configuration, the Exchange Server which should be monitored has to be selected (it is also possible for several Exchange Servers to be monitored at the same time). With the logical disk counters you also need to select the logical drive(s) : relevant to the Exchange databases and log files. © Fujitsu Technology Solutions, 2009 Page 40 (69)
White Paper Sizing Guide Exchange Server 2003 Version: 4.2, July 2006 On their own, the figures and graphs provided by the performance monitor of course say nothing about the efficiency and health of an Exchange Server. For this purpose a number of rules and thresholds are necessary, which the administrator should be aware of for each of these performance counters. Processor Processor(_Total)\% Processor Time To also be able to manage load peaks, the average CPU usage should not be greater than 80% for a longer period of time. System\Processor Queue Length Adequate processor performance exists when the counter Processor Queue Length has an average value that is smaller than the number of logical processors. If a bottleneck is evident here, solution options exist: Increase the processor performance through additional or faster processors, or relocate services or mailboxes to other Exchange Servers. Memory Memory\Available MBytes The free memory still available should always be greater than 50 MB, and by all means greater than 4 MB, as Windows otherwise implements drastic reductions in the resident working sets of the processes. If a bottleneck is evident here, the upgrading of the main memory should be taken into consideration (see also chapter Main memory). Memory\Free System Page Table Entries To ensure that the operating system remains runnable, the Free System Page Table Entries should not go below 3,500. A check should be made here as to whether the boot.ini-switch /USERVA=3030 has also been set with the set boot.ini-switch /3GB (see also chapter Main memory). © Fujitsu Technology Solutions, 2009 Page 41 (69)
Page 1 and 2: Sizing Guide Exchange Server 2003 A
Page 3 and 4: White Paper Sizing Guide Exchange S
Page 39: White Paper Sizing Guide Exchange S
Page 69: White Paper Sizing Guide Exchange S

Sizing Guide Exchange Server 2003 - Fujitsu

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?