LogicalDisk BusyTime Failed (19008)

[Mitch James]

What is this error and how to I fix it?

[Rob Buxton]

Your disk is busy.
Find the application and stop it.

Typically you might get this during Backups, in which case it would be expected.

[Frank Neubert_1]

We are getting these alerts a lot as well.
Other than the obvious below, would added more disk space to this help. this is not the busiest server we have either, any ideas.


Event Name: LogicalDisk BusyTime Failed (19008)
Event originator: "server name"
Event Severity: Critical
Event received: 28-Sep-2005, 00:41:08

Event description: The LogicalDisk BusyTime performance property is set to critical.

Disk Instance: S:
Disk Busy percent: 100

[Rob Buxton]

I've started seeing this a lot more since I moved to PSP 7.40A.
I've got PMP on one of the Servers and this did not seem to back up the alert generated from the Agent.
I'm seeing more CPU threshold alerts as well, but I've not yet had time to assess these against PMP.
But they're equally suspicious as some of the Servers are our DR Servers, and they're hardly used.

[Francis Nickels]

We are seeing alot more threshold exceeded events, such as the one noted here, after installing the 7.4 agents.

Does anyone know if there is a way to configure how long the threshold should be exceeded for before triggering an event?

It was working fine for us with 7.2 & 7.3, now we are getting so many, what I call false alarms, that it is rendering the notifications useless.

[Hense, Klaus]

I have the same Problem after Install PSP 7.4!
I can´t find the reasons.
It must be a PSP 7.4 Problem....

[Rodolphe_1]

Francis Nickels :

"Does anyone know if there is a way to configure how long the threshold should be exceeded for before triggering an event?"

Same question : this error appears on our servers during the backup at night, but it could be interesting to know the "limit time" before event...

[Brian Kerr_1]

Just add another data point to this thread. We're seeing the same thing having gone to v7.40 on disks that were fine on v7.3. The MIB suggests that disc activity should be greater than the thresholds for 15 consecutive time periods, I suspect it may only be looking at 1 time period.

[Christopher Knight]

Has anyone found a solution to this?

I am having the same problem with 7.40b agents.

thanks,

[Megan Graye]

We have SIM agent 6.40.0.0 deployed and are getting this notification as well.