Missing some local drive utilization stats
We've had an issue that's been affecting a few of our Windows 2k3 servers for a while now. It wasn't a major issue, so I was hoping the upgrade from 7 to 8 might resolve the issue, but we upgraded a few days ago and the problem is still present.
We have 4 particular servers with normal C:\ drives for the OS and a rather large E:\ for data. On 1 of the 4 servers, we can see drive utilization for both the C: and E: drives. On the other 3, we only see the C: statistics. I have tried removing and re-adding the "Partition Details of the Device (%)" monitor for the servers, but it still comes back with only the C: drive details, and the E: drive does not even show up as a monitor.
I am really hoping to find a way to fix this without having to lose any historical data collected for the servers in question. I understand I won't get any past data on the E: drive, but CPU and RAM utilization is pretty important to keep for troubleshooting and trending for the app that runs on them.
We first noticed this issue a couple minor revisions ago, and are now running the new v8 build 8002 code. We have just under 600 servers being monitored currently, and while I haven't checked each of them for this issue, we are only seeing it on these three particular systems which all have a very similar function. I would put more blame onto what's running on them if it wasn't for the fourth one working perfectly. The four servers are nearly identical as far as OS, applications, and configurations.
We have 4 particular servers with normal C:\ drives for the OS and a rather large E:\ for data. On 1 of the 4 servers, we can see drive utilization for both the C: and E: drives. On the other 3, we only see the C: statistics. I have tried removing and re-adding the "Partition Details of the Device (%)" monitor for the servers, but it still comes back with only the C: drive details, and the E: drive does not even show up as a monitor.
I am really hoping to find a way to fix this without having to lose any historical data collected for the servers in question. I understand I won't get any past data on the E: drive, but CPU and RAM utilization is pretty important to keep for troubleshooting and trending for the app that runs on them.
We first noticed this issue a couple minor revisions ago, and are now running the new v8 build 8002 code. We have just under 600 servers being monitored currently, and while I haven't checked each of them for this issue, we are only seeing it on these three particular systems which all have a very similar function. I would put more blame onto what's running on them if it wasn't for the fourth one working perfectly. The four servers are nearly identical as far as OS, applications, and configurations.