eseutil /p doesn't make it past the first scan, abruptly quits on dirty priv1.edb.

i've got a private store db that is dirty and needs to be repaired.  however, eseutil /p abruptly quits during the first scan pass.  the eseutil process uses up a considerable amount of ram (as shown in the task manager) prior to quiting.  the priv1.edb file size is 3.75Gb.  i've got 65Gb of free disk and 2Gb of ram to work with.  i'm just guessing that this might have something to do with ram and disk space.
stephenrbrownAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
BNettles73Connect With a Mentor Commented:


From first glance, I'd say you have plenty of disk space and 2GB should be enough ram. One of the best articles I've read about repairing exchange db's is here, "Repairing Exchange databases with ESEUTIL - when and how? " http://blogs.msdn.com/exchange/archive/2004/06/18/159413.aspx

Are you creating the temp db with the /t switch ... and are you trying to use the temp db over the network or keeping it local? Read through the article and let me know what you think.

You may want to copy the exchange db and log files to a safe place and then run an offline defrag with /d ....

That being said ... make sure you get a good backup before doing anything!
0
All Courses

From novice to tech pro — start learning today.