How can I recover Exchange server database when log file is Missing (Full Version)

All Forums >> [Microsoft Office 365] >> Exchange Online



Message


alexhall -> How can I recover Exchange server database when log file is Missing (28.Aug.2014 12:40:17 AM)

Hi

I received some log file error message and I unable to access my Exchange server database please help me to resolve this issue.
Error Message is

# -515 (0xfffffdfd)[:(]




jay.vyas84 -> RE: How can I recover Exchange server database when log file is Missing (6.Nov.2014 5:28:21 AM)

Hi Alex, you would need to understand what log files are required to bring the database to a clean shutdown state. To do this you would need to run eseutil /mh database.edb. The output should list logs required. Now check the transaction log files folder to check if you have the required log files. If yes, move these transaction log files into a new folder and nagivate cmd to the new folder and run eseutil /r eoo (where e00 is the transaction log sequence. the first three letters in the transaction log file). Mostly E00 is the last transaction log and to check the sequence number, you would need to run eseutil /ml e00.log.

If all log files are present the eseutil /r would run successfully bringing the database to a clean shutdown state. If logs file are missing and you are running exchange 2007, 10 or 13, you can run eseutil /r /a e00 to trigger a lossy recovery. If you are running exchange 2003, the only option you would have would be run do a hard repair by running eseutil /p database.edb.

Also, refer http://technet.microsoft.com/en-us/library/bb267001(v=exchg.80).aspx

Hope this helps.




ronniepaul -> RE: How can I recover Exchange server database when log file is Missing (2.Dec.2014 4:32:59 AM)

I completely agree with jay.vyas84 member, first you need to check clean state of the database using Eseutil /mh command lines

[image]http://repairexchange2010databasedirtyshutdown.weebly.com/uploads/2/6/3/4/26345231/2187424_orig.png[/image]

After using this command if you are getting dirty state of the database then you need to check transaction log file statement. Run Eseutil/ml command

[image]http://repairexchange2010databasedirtyshutdown.weebly.com/uploads/2/6/3/4/26345231/6929241_orig.jpg[/image]

If the log file is in unhealthy state then you need to perform both recovery tasks - soft & hard. You need transaction log files for the soft recovery task but as earlier you mention that you have received few log file error messages which related to the missing log files then in my opinion you need to perform hard recovery task using this command - Eseutil/p

[image]http://repairexchange2010databasedirtyshutdown.weebly.com/uploads/2/6/3/4/26345231/7814639_orig.png[/image]




Edwin009 -> RE: How can I recover Exchange server database when log file is Missing (7.May2020 12:43:35 PM)

Hypothetical situation: A backup of the Exchange database (EDB) file is available, but there are no transaction logs. How do we bring the database back to a functional state? Will the database be restored with all the changes made to it?

The most basic concept to understand is that by the time the Exchange database is mounted in the Server, it is in a dirty state the reason being the number of transactions that will take place in the database (i.e. sending or receiving messages, changes in the state of the email like read or unread, deleting or moving messages from a folder, etc). Therefore, if the backup is done while the database is mounted on the Server, it will definitely be in a dirty state (despite the type of backup). The requirement of log files for recovery depends on how the database is being backed up.

If the backup is made while the database is online or a shadow copy is created using an application that's not compatible with Exchange, then along with the possibility of backup being in a dirty state, it may also be corrupt. If the database is copied without bringing it into an inactive state, then some of the transactions must be in process with the memory and not yet written to the database. Therefore, the backup created might have an inconsistent state.

If it is in a dirty state and log files are available, then uncommitted transactions can be rolled up and all changes done to the database will be reflected. However, if no log files are available, then the best option is to go through the repair process using the ESE utility /p switch. The ESEUTIL command can help you repair the Exchange Server database caused by a dirty shutdown.

If the backup is created using an Exchange-supported backup application while the database is online, then it will definitely be in a dirty state but there is a lower chance that it will be corrupt. In this case, the backup can be restored and all uncommitted transactions will be replayed against it in order to bring the database back into a functional state. For this, it's mandatory that log files in the sequence are available to roll back the database.

To ensure that backup is not inconsistent, dismount the database before backing it up (i.e. create an offline backup). When the database is brought into an offline state, there are no uncommitted transactions and thus it is possible to recover Exchange database with missing log files. However, this option has a downside, too. First of all, you have to dismount the database, which means downtime for long hours. Also, transaction logs generated after backup creation will not be available, which means you may not get the most updated database backup in the operational state.

The requirement of log files in order to recover an Exchange database depends on what type of backup is created. If the backup is available but it is in a dirty state, then to get the most updated database back, it is important to have all log files in a healthy state. In a scenario where the database is in a dirty shutdown state, log files are missing, and you are not willing to go through the repair process, then you may want to look for software.




Page: [1]