Posts: 33
Joined: 2.Mar.2005
From: California
Status: offline
I've discovered (and you might see from my other posting here) that I have a bad database file for my exchange. Most likely, my priv1.edb is all wacko - which of course, has caused my exchange email to pretty much shut down and not let me mount the mailbox stores.
Anyhow...I've been attempting to run the eseutil /r <log file name> command and it's not working because of a dirty shutdown.
I found the database was in a dirty shutdown (vs. a clean shutdown) because I ran the eseutil /k priv1.edb and it told me.
Here's a little nibble from the results: File: priv1.STM ERROR: database was not shutdown cleanly (dirty shutdown)
Operation terminated with error -550 (JET_errDatabaseDirtyShutdown, Database was not shutdown cleanly. Recovery must first be run to properly complete database operations for the previous shutdown.) after 161.94 seconds.
So, I run the eseutil /r priv1.edb to see if I can do a soft recovery and I get:
Initiating RECOVERY mode... Logfile base name: priv1.edb Log files: <current directory> System files: <current directory> Operation terminated with error -1003 (JET_errInvalidParameter, Invalid API para meter) after 0.0 seconds.
So I find out my database is in a dirty shutdown state. I try to recover it, and it won't let me. What do you think I should do next - or maybe I'm missing a step? Btw, what would cause the dirty shutdown state in the first place?
Posts: 33
Joined: 2.Mar.2005
From: California
Status: offline
I just wanted to let everyone know my issue has been resolved and my email is back up and running fine.
I ended up getting free support from Microsoft since my company is a partner w/them. My resolution was:
Ran the eseutil /p frorm the BIN folder and repaired both the priv1.edb and pub1.edb files. Deleted the log and chk files. Ran a defrag on the stores . eseutil /d Ran isinteg (isinteg -s servername -fix -test alltests) frorm the bin folder. Mounted the stores.
I was weary about running the eseutil /p - since I've read horror stories about using /p - but it worked out fine for me.
Those are almost the steps I gave you in your other question. Glad you got everything back up and running.
And you were correct to be leary of ESEUTIL /P. What happens when you run this is that ESEUTIL is that each 4 KB page is checked for errors. If an error is found then it tries to correct it. If the error cannot be found then that page of the database is discarded (thus data loss). I have seen an entire 13 GB database be empty after running ESEUTIL /P. But I have also seen outcomes like yours. This is why a good backup plan is essential. And test these backups. The last thing you want in a crisis situation is to have to figure out how to restore a backup. There are several disaster recovery whitepages on the internet. As a matter of fact Microsoft has one that you can download.
Posts: 8194
Joined: 7.Jan.2004
From: California, USA
Status: offline
First, you do realize you're responding to a thread that's been inactive for 5 years?
The LOG and CHK files mentioned would be the ones associated with the particular mailbox store. If you are running Standard Edition, there is only one set. If you are running Enterprise Edition they are the ones associated with the Storage Group.
You do not ordinarily do anything with those files performing an offline defrag. If you also are experiencing a problem because of a dirty shutdown, I highly recommend you call Microsoft PSS to resolve your issues. They will do what they can to salvage your data. As mentioned in the thread, there are no guarantees and you can lose data.
_____________________________
Regards,
Dean T. Uemura Microsoft MVP - Exchange exchangeguy.blogspot.com uemurad@yahoo.com
Good Exchange server database backup always helps to solve critical situations in Exchange server. Although the built-in utilities allow the users to solve most of the errors of Exchange database corruption. However, it is necessary to understand the repair process of ESE utilities as it remove the damaged databases pages and users have to face data loss situations of important data.
This data loss problem can be avoided only by using a third party Exchange server recovery application such as this one:http://www.recover-computerdata.com/exchange-server-recovery.html
This application scans the damaged database file item by item and repairs the corrupted items. After repairing the database items it gives the option to save data in two formats. User can save the repaired data either in .PST or in .EDB file format. Recovered .edb file can be directly mounted on the MS Exchange Server. Software is compatible with all versions of MS Exchange Server i.e. 2010, 2007, 2003, 2000, and 5.5.
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [Microsoft Exchange 2003] >> General >> Dirty Shutdown & eseutil 
Dirty Shutdown & eseutil - 
RE: Dirty Shutdown & eseutil - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread
