Re: ESE performance errors

From: SMS (SMS_at_discussions.microsoft.com)
Date: 02/03/05 

Date: Thu, 3 Feb 2005 12:29:08 -0800

Maintenace window and backup window do not overlap.

Direct Attached drives are partitioned as follows:

C: SYSTEM 12GB 60% free NTFS
D: DATA 123.65GB 60% free NTFS
E: LOGS 16.95GB 90% free NTFS

"Ben Winzenz [Exchange MVP]" wrote:

> How is your server architected? Are you using a NAS or DAS for disks? How
> many users does this server support? You may need to check your disk
> configuration to make sure it is optimal. The following articles may help.
> Regarding your maintenance window, make sure that it isn't overlapping the
> Backup window at all. Normally, during an online backup, maintenance will
> be stopped.
> http://support.microsoft.com/default.aspx?scid=kb;en-us;Q326294
> http://support.microsoft.com/default.aspx?scid=kb;en-us;Q317173
> http://groups-beta.google.com/group/microsoft.public.exchange.admin/browse_frm/thread/350183880bc0d6ab?hl=en&lr=&c2coff=1&rnum=1&prev=/groups%3Fq%3DEvent%2B509%2BESE%26hl%3Den%26btnG%3DGoogle%2BSearch
> use http://tinyurl.com/3wm4o if the above link wraps.
>
> --
> Ben Winzenz
> Exchange MVP
>
>
> "SMS" <SMS@discussions.microsoft.com> wrote in message
> news:CF3F7F0E-46A2-4F82-A3FD-06B8C4E2A489@microsoft.com...
> > My Exchange 2003 server is getting these messages early every morning.
> > Event
> > ID's 508, 509, & 510. All reference ESE. Changed the mailbox maintenance
> > window around to see if that was conflicting with our backup exec 9
> > backups
> > to no avail. There appears to be nothing wrong with the server's hardware.
> > It's a new HP Proliant. Can't seem to find anything within the knowledge
> > base
> > or search engines. Below is a snapshot. Let me know your thoughts / ideas.
> > Thanks!
> >
> > Information Store (2696) Third Storage Group: A request to read from the
> > file "D:\Program Files\Exchsrvr\MDBDATA\Resource Mailboxes.edb" at offset
> > 19542646784 (0x000000048cd52000) for 4096 (0x00001000) bytes succeeded,
> > but
> > took an abnormally long time (64 seconds) to be serviced by the OS. In
> > addition, 0 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 428 seconds ago. This problem is likely due to faulty hardware.
> > Please
> > contact your hardware vendor for further assistance diagnosing the
> > problem.
> >
>
>
>