Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

HELP! Corrupt Priv1.edb repair question 2

Status
Not open for further replies.

lb63640

MIS
May 12, 2004
554
US
When running ESEUTIL to repair a corrupt database like priv1.edb, after the stores are dismounted in ESM, is it also necessary to stop all Exchange services?

If the pub.edb isn't specified in any event log entry as being corrupt, is it necessary to also run ESEUTIL on it when you are taking care of the priv1.edb?

We don't have a good backup to restore from, so we have to go with ESEUTIL.
 
Hi lb63640,

I would follow this procedure:

1. Stop Exchange services

2. Copy (i.e. back-up) MDBdata folder content in a diffent location

3. Try first ESEUTIL -r

4. Just if -r option does not work, consider to use ESEUTIL -p
PLEASE NOTE IT IS RISKY. Info here:
5. Please find below a batch to perform. Please note that you should edit the batch where appropriate. e.g. k: (backup of data) and g: (tg:\priv.edb) temporary folder to your configuration.



@echo off
cls
REM Stop serv
net stop msexchangeimc /y
net stop msexchangeis /y
net stop msexchangemta /y
net stop msexchangeds /y
net stop msexchangesa /y
REM Backup
copy f:\exchsrvr\mdbdata\*.* k:\mdbdata\*.*
REM Run
eseutil /d /ispriv /tg:\priv.edb
REM restart services
net start msexchangesa /y
net start msexchangeds /y
net start msexchangemta /y
net start msexchangeis /y
net start msexchangeimc /


I hope you find this post helpful.

Regards,

Robert
MCSA 2003 messaging
 
Any time you perform a hard repair on one database, you must run it on the other database or delete the other, otherwise the database will be inconsistent and the IS will fail to start. You must also run the Isinteg with the -fix switch in order to prevent mailboxes from being corrupt. If you get an error -1011 when attempting to start the repaired IS, run Isinteg -patch.

Rather than running a script, use the services control panel to stop the IS and DS. You will be prompted to stop any dependent services.

When all else fails, READ THE DAMN BOOK!
 
Many thanks to icsboi and fuego007 for their very helpful posts! Issue is now resolved.

Fuego007, whaddaya mean read the book? I don't need no stinkin' book when I got Tek-Tips buddies who will shove me in the right direction during a nervous breakdown! (Actually, most manuals and documentation are sadly long-gone from this particular office site.)
 
lb63640, If you're going to be supporting Exchange 5.5 for some time to come, try to find copies of the following books: Exchange Server 5.5 Unleashed, written by Greg Todd, et al, and published by SAMS, and Microsoft Exchange Server In A Nutshell, by Mitch Tulloch, and published by O'Reilly. The Nutshell book is an excellent resource for troubleshooting, repairing, and maintaining Exchange 5.5. It also explains some of the differences between 5.5 and 5.0.

When all else fails, READ THE DAMN BOOK!
 
Thanks, fuego007! I'm going to track down those books.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top