Exchange 2007 Event ID 510 Performance warning message


Background: Windows Server 2008 Standard, Exchange Server 2007.

I have been getting warning messages from Exchange server when full backup was running.

ID= 510; Src= ESE; User= ; Catg= Performance ; D/T= 07/19/2014 19:05:35; EventDesc= MSExchangeIS (6788) First Storage Group: A request to write to the file "E:\ExchangeSvr\Mailbox Database.edb" at offset 2958442496 (0x00000000b0564000) for 8192 (0x00002000) bytes succeeded, but took an abnormally long time (61 seconds) to be serviced by the OS. In addition, 21 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 86100 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

Full backup starts at 7PM on a external hard disk. And the error message appeared at 7PM as soon as the backup started.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Adam FarageEnterprise ArchCommented:
More about the actual error here:

As it says in the technet article above, the Event ID 508 simply means the operation it is attempting completed but took a long time to complete. If this is occurring due to the backups, it is most likely due to an issue with the disk subsystem hosting the mailbox databases and not having enough available I/O. I would not worry about it, but it will occur because running the backup (ESEBACKUP.DLL in Exchange 2007) and Exchange 2007 regular traffic (e.g: reading / writing transactions) is IO intensive, and it seems the disks that are hosting Exchange are most likely undersized.

If you are concerned, I would consider adding additional spindles to the array that hosts these databases. That will provide additional IO and most likely resolve these errors you are seeing, that only happen when a backup is ran.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.