Hello
I am currently on SCOM 2007 R2 CU6 and Window Server Operating System MP version 6.0.6989.0 (I cannot use the latest version of the MP as we still have some Windows 2000 Servers we need to support, yes I know :( )
Any way the issue is, I have never found the Logical Disk performance counter data very reliable from SCOM.
For example, I have a Windows 2008 R2 Server and when looking at a local Logical Disk (which holds an SQL temp DB on a busy SQL Server) and look at the performance counter
The SCOM collection rule is called "Collection Rule for Average Disk Seconds per Transfer"
The actual Windows Perfmon counter is called "Avg. Disk Bytes/Transfer"
if you look at the description of the above Perfmon counter it is described as
"Avg. Disk Bytes/Transfer is the average number of bytes transferred to or from the disk during write or read operations."
The problem I have is as follows:
The resulting SCOM performance chart over several days (which has a scale ox 1x) states the value never reach 3 (e.g. maximum wa s 2.7 say). I cannot believe the a drive holding the tempDB databases for a busy SQL Server does not transfer more then 2.7 "bytes" of data at a given to to its tempDB databases!
Indeed when I look at Permon on the Server and looks at this counter over say 20 minutes or so, the figure is often in the 10,000 or 30,000 bytes etc. It does fall back to 0 (zero) momentarily but mostly it is in the 1000s, or 10,000s etc.
Therefore when my boss says show me the "Avg. Disk Bytes/Transfer" and SCOM says it has not exceeded 2.7 over the last business week (i.e. the chart never peak above this value on the chart with scale 1x) he naturally does not believe it!!
Any advice please regarding the above. Is it the fact if the counter ever falls to zero it messes up the SCOM report charts?
Thanks
AAnotherUser
AAnotherUser__