Re: Defrag very very slow?
- From: "Eric Tam [MSFT]" <ericta@xxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 21 Jan 2006 09:47:13 -0500
Hi Michael,
One thing to make sure of when doing a defrag is that the command window we
are running the command in is always the active window, otherwise it is
possible the process pauses. If the screensaver pops up or we open another
window or perform any other action on the server, click back on the command
window and hit the spacebar or Enter. If this is not the case, I would
suggest making a copy of the database and moving it to another server and
rerun the defrag and let it run - if there's disk activity, memory usage,
etc. then continue to let it run, even if there doesn't appear to be any
progress on the screen.
The following article will help you run eseutil on a server without having
to install Exchange:
244525 How to run Eseutil on a computer without Exchange Server
http://support.microsoft.com/default.aspx?scid=kb;EN-US;244525
Hope this helps!
--
Eric Tam, MCSE, MCSA
Microsoft Exchange Support
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Michael Salem" <msnews@xxxxxxxxxx> wrote in message
news:MPG.1e3af2e9b55204dc98969b@xxxxxxxxxxxxxxxxxxxxxxx
> Exchange Server standard stopped working with errors about the database
> exceeding 16GB in size. This is a known issue, and not what I'm asking
> about.
>
> I ran ESEUTIL /d /p (this is a defragment, storing the defragmented file
> in a specified location instead of overwriting the original; it is not a
> true repair like /p). There is plenty of space on the disc for an extra
> copy of the database.
>
> The process started; after a couple of hours I had two dots (about 4%)
> and the new priv1.edb was about 1 GB (aS shown on a directory listing of
> the destination drive). After 6 more hours it had not moved on at all -
> I killed the process. I tried this twice; in each case the process
> stopped
>
> ESEUTIL /ms runs (in about 6 minutes), and produces what looks like sane
> output.
>
> The diagnostic ESEUTIL /G had made has made no visible progress (no
> dots) after about an hour.
>
> isinteg -test alltests has run tests 1-6 with no errors reported, and is
> hanging at 18% on test 7 (folder).
>
> How long should these processes take on an adequately fast machine (I
> don't have the specifications to hand)? I believe the drives are a RAID
> 5 SCSI array. The machine generally seems to be working OK. I understood
> that ESEUTIL should typically process about 4GB/hour.
>
> Best wishes,
> --
> Michael Salem
.
- Follow-Ups:
- Re: Defrag very very slow?
- From: Michael Salem
- Re: Defrag very very slow?
- References:
- Defrag very very slow?
- From: Michael Salem
- Defrag very very slow?
- Prev by Date: Defrag very very slow?
- Next by Date: Exchange 2003 Public folders problem
- Previous by thread: Defrag very very slow?
- Next by thread: Re: Defrag very very slow?
- Index(es):
Relevant Pages
|