Folks,I am running the eseutil /p command due to having discovered a corrupt .edb database on exchange 2003. Database is 31gb in size. I ran the command at 21:15 (GMT). It has been stuck at deleting unicode fixup table for a cpuple of hours bar at 01:00 where it grew by a few dots. Going by the app log it lost ten pages of bad data an at 01:00 the database engine lost one or more bad columns of data in one record. I reckoned eseutil /p would do 7-8gb of data every hour but looks like I am wrong?

How did you discover it was corrupt? Do you have a good backup you can restore instead? that is the preferred way to solve this. eseutil/p typically means a loss of some data during the repair process. Not sure why its taking so long however.