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 TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Restore after crash
- Thread starter Joliet
- Start date
You will have a little bit of work ahead of you.
First off, I find it easiest to due Exchange maintenance if you have first added the path to the Exchsvr\Bin directory to the path statement in your environmental variables. This lets you just call the EESUTIL program by name without path from within the MDBDATA directory.
Stop the Information Store Service in the Services snap in.
Now you will first want to check to see if log files are needed.
ESEUTIL /MH Priv1.edb
Look at the resulting report for "Logs needed" also look for State as Clean or Dirty. this indicates if you need to do a soft recovery to try and merge the log info into the database. If the database reports clean, skip to the defrag otherwise....
Do a soft recovery:
ESEUTIL /r E00
Note, if your E00.log file is missing, rename the most recent log file to E00.log. That is E zero zero.log
If soft recovery works skip to the defrag otherwise:
Do a hard repair:
ESEUTIL /P Priv1.edb
Note, the repair can cause data loss as data from the logs won't be incorporated. Use this as a last resort.
Now do the defrag:
ESEUTIL /D Priv1.edb
Following a successful offline defrag you will want to start the info store service and mount the database, then dismount it. Now you want to run ISINTEG.
ISINTEG -s servername -fix -test alltests
Run ISINTEG until it either comes up with no warning and errors or until it reports the same errors consistantly.
I hope you find this post helpful. Please let me know if it was.
Regards,
Mark
First off, I find it easiest to due Exchange maintenance if you have first added the path to the Exchsvr\Bin directory to the path statement in your environmental variables. This lets you just call the EESUTIL program by name without path from within the MDBDATA directory.
Stop the Information Store Service in the Services snap in.
Now you will first want to check to see if log files are needed.
ESEUTIL /MH Priv1.edb
Look at the resulting report for "Logs needed" also look for State as Clean or Dirty. this indicates if you need to do a soft recovery to try and merge the log info into the database. If the database reports clean, skip to the defrag otherwise....
Do a soft recovery:
ESEUTIL /r E00
Note, if your E00.log file is missing, rename the most recent log file to E00.log. That is E zero zero.log
If soft recovery works skip to the defrag otherwise:
Do a hard repair:
ESEUTIL /P Priv1.edb
Note, the repair can cause data loss as data from the logs won't be incorporated. Use this as a last resort.
Now do the defrag:
ESEUTIL /D Priv1.edb
Following a successful offline defrag you will want to start the info store service and mount the database, then dismount it. Now you want to run ISINTEG.
ISINTEG -s servername -fix -test alltests
Run ISINTEG until it either comes up with no warning and errors or until it reports the same errors consistantly.
I hope you find this post helpful. Please let me know if it was.
Regards,
Mark
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question