RE: Exch2003 - fix dirty DB without deleting log files
- From: Rene Frenger <ReneFrenger@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 14 Apr 2008 04:46:03 -0700
It 's always better to restore from backup then do a repair.
eseutil /mh will show you what logfile it needs.
If it says 0-0, then it doesn't need any logfiles.
But also do a eseutil /mh on the stm file (if it is Exchange 2000 or 2003).
Normally you also have to do a defrag after the /p repair.
The logfiles are worthless after a repair and can be deleted.
Also make a full backup right after you did the repair.
--
Regards,
Rene Frenger
MCITP E2K7
MCP EX5.5, 2000, 2003
MCSE
"nicough@xxxxxxxxx" wrote:
Today I had a Mailbox database which wouldnt start:.
c1041739 "The database files in this store are inconsistent"
"eseutil /mh priv1.edb" showed that the DB was in a dirty shutdown
state.
Here's is what I did:
-Deleted my Information Store log files
-"eseutil /p" to REPAIR the database
-"isinteg -s SERVER -fix -test alltests"
-Mailbox store now starts ok.
1)
Given that the /P repair option is a last resort (and slow), is there
anything else I could have done to bring my store online.
2)
Since we are not restoring from backup, is it save to assume that all
information in the LOG files, also resides in the DATABASE, and
therefore it is ok to delete the log files? If not, then how can I
play back the log files into a dirty database?
Thanks
Nick
- References:
- Exch2003 - fix dirty DB without deleting log files
- From: nicough
- Exch2003 - fix dirty DB without deleting log files
- Prev by Date: Re: installing Microsoft Exchange Server ActiveSync Web Administra
- Next by Date: re: Public folder replication
- Previous by thread: Exch2003 - fix dirty DB without deleting log files
- Next by thread: Exchange 2003 Vs Outlook 2003
- Index(es):
Relevant Pages
|
Loading
