?
Solved

Exchange 2007 Log replay problems

Posted on 2009-04-23
5
Medium Priority
?
2,026 Views
Last Modified: 2012-05-06
Hi,

We are having an issue while trying to replay log files into a restored database file. I have restored a database and associated log files from backup (using ARCserve r12 exchange agent) into a recovery storage group. I run an eseutil /mh on the database file and it shows as dirty shutdown and required log file of 0x685a-0x686c. These log files are present in a separate folder called _restoredLogs. I run the following command from the _restoredLogs directory eseutil /r E00 /i /d "d:\...\mailbox database.edb". This command completes successfully however when I query the database file again with an eseutil /mh it is still showing as dirty shutdown. I have managed to get another copy of the database running by using the /p option however have lost some data (as was expected). Does anyone know of a way to get the /r option to replay the logs properly?
0
Comment
Question by:PulseAdmin
  • 3
  • 2
5 Comments
 
LVL 13

Expert Comment

by:consultkhan
ID: 24230849
you should typically run esuutil /r without specifying E00 or any other switches.This should be run from the directory where log files are copied by the backup programme.The system will automatically play those log files which are ok.

You could also check if there is any log file corruption by running eseutil /ml against the log files,and remove any found corrupt.If you do remove any log files,rename the last log file to E00.

thanks,
consultkhan
0
 

Author Comment

by:PulseAdmin
ID: 24237948
Hi Consultkhan,

I tried running the eseutil /r command however this didn't work. Result as follows:

E:\Microsoft Exchange Server\Testing Storage Group\Logging\_restoredLogs>eseutil /r

Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 08.01
Copyright (C) Microsoft Corporation. All Rights Reserved.

Usage Error: Missing logfile base name specification.

Operation terminated with error -1003 (JET_errInvalidParameter, Invalid API parameter) after 0.47 seconds.

I have also run the eseutil /ml on all of the required log files. The test completed successfully on all of the log files. One thing I did notice though is that the database field in the log files is pointing to the original database location not the restored database location. Is this a problem?

Below is the output from the eseutil /r command when I run with the E00 and /d switches:

E:\Microsoft Exchange Server\Testing Storage Group\Logging\_restoredLogs>eseutil
 /r E00 /d "d:\Program Files\Microsoft\Exchange Server\Mailbox\Testing Storage G
roup\Mailbox Database.edb"

Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 08.01
Copyright (C) Microsoft Corporation. All Rights Reserved.

Initiating RECOVERY mode...
    Logfile base name: E00
            Log files: <current directory>
         System files: <current directory>
   Database Directory: d:\Program Files\Microsoft\Exchange Server\Mailbox\Testin
g Storage Group\Mailbox Database.edb

Performing soft recovery...
                      Restore Status (% complete)

          0    10   20   30   40   50   60   70   80   90  100
          |-----|-----|-----|-----|-----|-----|-----|-----|----|-----|
          .........................................................................



Operation completed successfully in 35.907 seconds.

Any ideas?
0
 
LVL 13

Expert Comment

by:consultkhan
ID: 24241178
log files is pointing to the original database location not the restored database location. Is this a problem?
NO.Its not a problem.
pls also run isinteg with fixall opiton.

thanks,
consultkhan
0
 

Author Comment

by:PulseAdmin
ID: 24246553
Hi Consultkhan,

Unfortunately you can't run isinteg on a dirty shutdown database.
0
 

Accepted Solution

by:
PulseAdmin earned 0 total points
ID: 24246734
I have managed to get the log files to replay into the database. I had to do the following to get it to work.

1. I created a clone of the Exchange Server and Domain Controller on a separate Network
2. Restored the database and Log files to the original location on the cloned Exchange Server.
3. Ran eseutil /r E00 from the log file directory.

After this the database was clean shutdown. Not sure why the files had to be in the exact location that they were backed up from for the repair to work??
0

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

As much as Microsoft wants to kill off PST file support, just as they tried to do with public folders, there are still times when it is useful or downright necessary to export Exchange mailboxes to PST files. Thankfully, it is still possible to e…
Exchange administrators are always vigilant about Exchange crashes and disasters that are possible any time. It is quite essential to identify the symptoms of a possible Exchange issue and be prepared with a proper recovery plan. There are multiple…
In this video we show how to create a mailbox database in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Servers >> Data…
how to add IIS SMTP to handle application/Scanner relays into office 365.
Suggested Courses
Course of the Month16 days, 17 hours left to enroll

864 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question