Hey everyone, I'm new, and I'm going to bother you with a problem that occured just earlier...
My Exchange IS won't mount because the current logfile is apparently corrupt (JET says it's missing but I'm seeing it). Problem is, I went on vacation and my last backup is two weeks old. Now IIRC when you got a corrupt EDB, restoring an old backup and playing the logfiles should prevent any dataloss right? But in my case, it seems that it's the logfiles themselves and not the EDB that's gone wrong.
So my question is: Should I attempt a restore in place of my current database, or should I just go with a repair? I'd prefer to avoid the latter, but I can't risk losing all messages from the last two weeks of work!
Can you guys help me? Thanks
< Message edited by djalil -- 27.Dec.2007 12:57:55 PM >
Posts: 3004
Joined: 9.May2007
From: India
Status: offline
hi mate,
Whenever my database is in corrupt stage i.e. log file or database. My normal step; 1) soft recovery 2) restore from backup 3) hard repair.
I won't suggest you to go with hard repair unless and until we require to do it. Major disadvantage of hard repair is you can't expect 100% of data back after the process because it will delete entire page. So this should be your final step and should understand the ramification.
What about soft recovery, i guess you tried it already does it giving any error message in the applicaiton log. If you have corrupt log files or log file is missing please go with last good known backup.
Yes you're right, I ended up restoring the two weeks backup and replaying the logs. I'm checking the mailboxes and they seem fine and up to date to the time of the crash.
As you said I tried soft recovery first (eseutil /r e00) but all I got was a "528 0xFFFFFDF0 JET_errMissingLogFile current log file missing".
Anyway, backup restore + eseutil /cc solved my problem. I hope I didn't lose anything important in the process...
HI I have a simler problem but the problem that the Eseutil /cc did not work also and i got an error message stating
Microsoft(R) Exchange Server Database Utilities Version 6.5 Copyright (C) Microsoft Corporation. All Rights Reserved. Initiating RECOVERY mode... Logfile base name: e00 Log files: <current directory> System files: <current directory> Performing soft recovery...
Operation terminated with error -528 (JET_errMissingLogFile, Current log file missing) after 1.0 seconds.
Why did this error happend NOTE that my EDB file is in a partition and the logs are ain a nother partiton
EventLog stat Event Type: Error Event Source: ESE Event Category: Logging/Recovery Event ID: 455 Date: 1/3/2008 Time: 6:05:08 PM User: N/A Computer: MAIL Description: eseutil (5324) Error -1811 (0xfffff8ed) occurred while opening logfile G:\Program Files\Exchsrvr\bin\e00.log. For more information, click http://www.microsoft.com/contentredirect.asp.
Posts: 3004
Joined: 9.May2007
From: India
Status: offline
hi,
Whenever we are talking about online back restore procedure, a very important you need to understand is all the log file should be in sequence if you miss any log file you can't restore the database.
Let say i have restored my database, once i restore my database, the first step i use to do is i will check my database information i.e eseutil /mh eseutil /mh : it will read the head information and you can see that the status "Dirty Shutdown" and below that there is one thing "Logs Required" : 03-05 (this will indicate the number of log file inorder to make the database as clean shutdown.
So now i got my database status and logs required (in online restore case : all the required logs will be stored in temp folder)
Now the next thing is that i need to confirm whether the required log file is in sequence or not, here either you can check it manually going through manually or else by specific command. i.e eseutil /ml "C:\temp\e00" The above command will check the log file are good and are in sequence if everything is good and ok
then you need to perform eseutil /cc command.
I guess this should clarify about the online restore procedure
HI This Happend in my LAB I ran a Backup for the Exchange info store, but I notice something that is when I do the backup, the backup did not flush the Log files I have the EDB file in a Partition and the logs in a nother partition, and what I know that the backup will flush the Logs when it finish. and I restore that backup I do and I face this problem I remove all the Old logs and do the restore again. but this did not help too
Ismail.mohammed: even if I run the commands eseutil /mh I will have the dirty shutdown. and I have to run the command eseutil /r e00 to make it in a clean shutdown, but I am facing that the log are missing I will try what you say
hi again these are the result running the eseutil /mh
Microsoft(R) Exchange Server Database Utilities Version 6.5 Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating FILE DUMP mode... Database: I:\My Computer\G\Exchange2003data\priv1.edb File Type: Database Format ulMagic: 0x89abcdef Engine ulMagic: 0x89abcdef Format ulVersion: 0x620,11 Engine ulVersion: 0x620,11 Created ulVersion: 0x620,11 DB Signature: Create time:09/21/2007 02:43:40 Rand:16571598 Computer: cbDbPage: 4096 dbtime: 1038852 (0xfda04) State: Dirty Shutdown Log Required: 17-17 (0x11-0x11) Streaming File: Yes Shadowed: Yes Last Objid: 1227 Scrub Dbtime: 0 (0x0) Scrub Date: 00/00/1900 00:00:00 Repair Count: 4 Repair Date: 09/21/2007 02:36:50 Old Repair Count: 4 Last Consistent: (0x11,1DBA,16A) 12/19/2007 06:03:39 Last Attach: (0x11,1DC3,81) 01/03/2008 15:00:50 Last Detach: (0x0,0,0) 00/00/1900 00:00:00 Dbid: 2 Log Signature: Create time:08/10/2007 21:33:18 Rand:10528633 Computer: OS Version: (5.2.3790 SP 2)
Operation completed successfully in 3.15 seconds.
Would you please tell me more about what does Log Required: 17-17 (0x11-0x11) mean, does this mean that there is 17 log file should present to be able to mont this data base
Running the command Eseutil /ml for the log file result are:
Verifying log files... Base name: e00 Log file: G:\Program Files\Exchsrvr\MDBDATA\E00.log - OK No damaged log files were found. Operation completed successfully in 1.12 seconds.
its telling that the logs are OK I run the command Eesutil /r e00 /l %Log File Path% /s %System File Path% and the result was Initiating RECOVERY mode... Logfile base name: e00 Log files: G:\Program Files\Exchsrvr\MDBDATA System files: G:\Program Files\Exchsrvr\MDBDATA Performing soft recovery... Operation completed successfully in 2.3 seconds. I check the database header using the /mh but it still in dirty shutdown
Microsoft(R) Exchange Server Database Utilities Version 6.5 Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating FILE DUMP mode... Database: I:\My Computer\G\Exchange2003data\priv1.edb File Type: Database Format ulMagic: 0x89abcdef Engine ulMagic: 0x89abcdef Format ulVersion: 0x620,11 Engine ulVersion: 0x620,11 Created ulVersion: 0x620,11 DB Signature: Create time:09/21/2007 02:43:40 Rand:16571598 Computer: cbDbPage: 4096 dbtime: 1038852 (0xfda04) State: Dirty Shutdown Log Required: 17-17 (0x11-0x11) Streaming File: Yes Shadowed: Yes Last Objid: 1227 Scrub Dbtime: 0 (0x0) Scrub Date: 00/00/1900 00:00:00 Repair Count: 4 Repair Date: 09/21/2007 02:36:50 Old Repair Count: 4 Last Consistent: (0x11,1DBA,16A) 12/19/2007 06:03:39 Last Attach: (0x11,1DC3,81) 01/03/2008 15:00:50 Last Detach: (0x0,0,0) 00/00/1900 00:00:00 Dbid: 2 Log Signature: Create time:08/10/2007 21:33:18 Rand:10528633 Computer: OS Version: (5.2.3790 SP 2)
Running the command Eseutil /cc %Path that the restore use for temp% Restoring .... Restore to server: MAIL Target Instance: First Storage Group Operation terminated with error -939523486 (Existing log file has bad signature. ) after 0.231 seconds.
So, the probem present and for more information how this happend I run a NORMAL backup for the database after the backup finished and as I notice that the logs are did not flushed, I run a restore and I had this problem the exchange was working fine and no problem at all
Lets tell you something strange the Logs are really missing as I notice the number sequance they were E0000035.log E0000060.log But where are they cause the exchange was running perfect before the restore I mean that there were no problem I do as Microsoft says in :http://support.microsoft.com/kb/823016 and the exchange work again, but alot of Emails are missing, even some Emails before the backup are missing ????? what is going on and why eseutil is telling me when I run the switch /cc
Restoring .... Restore to server: MAIL Target Instance: First Storage Group Operation terminated with error -939523486 (Existing log file has bad signature. ) after 0.251 seconds.
Not Missing Log
< Message edited by farisnt -- 4.Jan.2008 5:01:50 PM >
Posts: 3004
Joined: 9.May2007
From: India
Status: offline
hi,
Log Required: 17-17 (0x11-0x11)
This means that you require 0x11 log file, you can try to run eseutil /ml on e00.log and check the lgeneration value, if you don't have this log file you can't mount the database
This situation occurs generally in case of serious damage to Exchange Server database, which can not be repaired by Eseutil. In these circumstances, you need to repair and restore the database using a good third party solutions. These solutions are available in the form of easy to use applications, known as EDB Repair software. These software apply efficient scanning algorithms on the corrupted EDB file to retrieve all of its damaged or corrupted objects such as emails, notes, contacts, tasks and so forth.
The root cause of missing data is ESE utilty. Actually, when a hard repair process is performed through the built-in utility, it discards the damaged database pages and user has to face the data loss situations. However, this data loss issue can be avoided by a recent and updated backup copy or a third party Exchange server recovery application like this:http://www.recover-computerdata.com/exchange-server-recovery.html
This tool handles all corruption situations efficiently and is compatible with all versions of Exchange Server. One of the best feature of this application is Rebuilding database i.e. damaged database is repaired effectively so that it could be mounted on the server directly.
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [Microsoft Exchange 2003] >> Information Stores >> Exchage disaster recovery question 
Exchage disaster recovery question - 
RE: Exchage disaster recovery question - 
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
