The scope of this article is meant to provide additional tools that are already available on a windows machine in order to isolate possible performance issues related to:
Some times it is hard to say just by checking windows event logs or even our AppAssure Support Bundle AAinfo logs, so use this tool wisely and consider scheduling at least 12-24 hours Perfmon Collection Sessions during the peak hours for the Core or Agent Protected Machine in order to be able to pull a relevant sample for the analysis.
For more details regarding Windows Performance Monitor and how to use it to diagnose Server Performance Problems please open these articles:
Note: Suppose you have determined the value of Avg Disk Queue Length is indeed accurate and useful – how much is too much? As a general rule for hard disks, an Avg Disk Queue Length greater than 2 (per hard disk) for extended periods of time is considered undesirable. If you have a RAID system with 8 disks, you do not want an Avg Disk Queue Length greater than 16. Faster hard disks with quicker access times (and therefore I/O) will allow greater flexibility with these numbers. Avg Disk sec/read and Avg Disk sec/write should be under 10ms – over 20ms may indicate a bottleneck. If while Avg. Disk Queue Length is over 2 and % Disk Time is hovering at 60% or above, you may want to look into a possible I/O bottleneck.
The Resolution Steps were split into two sections, Collection of Data and Analysis of the Results.
7. You can also pull the Performance Collector Data, compress it and upload it into an FTP site in order to be able to process the data with Performance Analysis of Logs Tool (PAL) later.
The next link Performance Analysis of Logs (PAL) Tool will redirect you to the PAL tool project page where you can find the tool binaries.
The next link Two Minute Drill: Performance Analysis of Logs Tool (PAL) will have instructions on how to use PAL to review the performance logs.