We are getting "Foundation Agents" alerts at a similar time each night - they are event ID 1180 "OS Information Agent: The Logical Disk Performance Instance, 'D:' is failed with Disk Busy Time of 97 percent. [SNMP TRAP: 19008 in CPQWINOS.MIB]"It happens on nights when our backup does not run, virus scanning is not doing a full scan at this time - the only thing that I can see running is that ESE is starting to do an online defrag of the drives.My questions are: what would this alert suggest - a drive failing? This is on a new server with new 10,000RPM SAS drives in a RAID5 array, so I would have thought they would have plenty of performance.Should I just change the threshold of the Logical Disk Time alerts in Foundations Agents? If so - where can I do this - I have looked in all the HP Insight Manager type spots and cannot find anywhere to configure alerts (these alerts were set up by someone else).Cheers,Kim

Can you give us some more info here? How many mailboxes & Information Sores are hosted on this server? How big are the mailboxes / Information Stores on average? Do your users ever complain that outlook is slow or sometimes looks like it cannot find the server? How many 10k SAS disks of what size do you have in the Raid 5 array? Yes, since having a failed disk in a RAID5 array seriously degrades the performance of the array, this is a definite possibility - though unlikely since HP management agents normally log an error in event log if a disk fails or displays erratic behaviour.

Just one information store - the priv1.db is 13gb. There are about 35 users.Outlook does not seem slow (no 'cannot find server' errors). There are five 75gb disks in the RAID5 array, and no management agents have come up with any notifications to suggest a failed disk.So in a nutshell, the server seems to be running well from what I can tell (memory/cpu utilisation is very low) - its just this error occurring between 2am and 3am every day - the only thing I can see that runs at this time is the ESE utility doing an online defrag. No other errors appear in the eventlog around this time.Thanks for the reply, hope this info helps.Cheers,Kim

Ok, that is pretty small and I would say you definitely wont have a performance problem with those specs. Something worth noting though is if you running Exchange Std Edition, you are coming close to the 16GB database limitation, you may need to increase this in the near future, fortunately, MS have incorporated the option of expaning the size in Ex SP2, you can now go to a max of 75GB. It does require you to implement a registry hack though. Check out: Database Size Limit Configuration and Management I suggest you try running an offline defrag of your database using eseutil /d. You should also run all the usual disk utilities, chkdsk & defrag to make sure the file system is optimal. Let me know how you get on.

I have finally had a bit more time to look into this error more - still have not resolved it.I have installed diskeeper to do a complete defrag of all our hard disks. Currently diskeeper is reporting all the drives as being in good order (defragmented).I have also run an integrity check on the priv1.edb file - as well as a full offline defrag. Our database limit has also been extended to 75gb. I have not run chkdsk yet - however I am worried if I do that we run the risk of loosing any files? (I have been stung before with my machine at home - chkdks caused me to lose some files). What are the risks with running it?Cheers,Kim

So long as you take the necessary precautions, you should have no problem. Before running the chkdsk, I would stop the I/S service, copy the EDB, STM and Log files onto another partition / machine on the network (for backup) then run chkdsk. Should chkdsk delete any files then all you need to do is bring the EDB's, STM and Logs back onto the server. Just another thought, If possible try changing the schedules of your maintenance tasks to run at different times/dates if at all possible, also check to make sure the correct exclustions are set on your AV software. See kb823166

I'm in a similar boat, except on a SQL server. Exact same type of error, "Logical Disk Time Performance Failed" on an HP Proliant ML350 with dual Xeons, 8 G ram, 15k drives with 4 in RAID DDG and 2 mirrored for the log files, OS on anothe 2 mirrored drives. I tried updating firmware with no joy. Queries run fine, no db corruption, every HP hw diagnostic checks out fine. Nobody at HP seems to have a real clue as to its cause or meaning.

It may very well be that you have reached your threshold point that you have set in the Insight Agent Logical Disk settings. This will send notifications Warning or Critical (depending on what value youset) when that threshold is crossed. Check your insight agennt System Management Homepage "Home -> performance -> logical disks". See if yourthe Disk Busy Time% has exceeded yourCritical or Warning threshold indicator settings. Adjust as necessary.