Sunday, 14 May 2017
5/14/2017 09:54:00 pm 0

How to recover Exchange Database with log files

Developed by Microsoft, Exchange Server is one of the most widely used mail as well as a calendaring server. This popular messaging platform offers scheduling, emails, and tools for both messaging service and custom collaboration applications. With hands on this renowned application, a user can manage as well as create all communication effortlessly, be it in on the mobile device or at the workplace.
In the Exchange Server, one thing that plays a vital role is Transaction Log Files. It manages the complete changes record that are made in the Exchange Server. All the information i.e. to be inserted into mailbox database is first written in the Exchange Server database. If in case, any detail is missing from the log file, it results in an operation failure issue. And, as a result, a user cannot access mailbox database from EDB files. In short, log files are essential for proper functioning of the Exchange Database.
Let’s now look at how log files help in Exchange Database Recovery - 
How to Recover Exchange Database with Log Files
Prior to executing the Exchange mailbox database recovery, a user needs to examine whether the state of the database is healthy or is in a dirty shutdown. To run this, the user needs to use the following Eseutil/mh command:
c:\program files\exchsrvr\bin>eseutil\mh “drive: \program files\exchsrvr\mdbdata\priv1.edb”

Two Approaches to Recover Exchange Database
•    Soft Recovery
•    Hard Recovery
Soft Recovery
Soft Recovery is the procedure of replaying the transaction log files in a scenario when the database is re-mounted on the server that is suffering from an unanticipated halt.
During this circumstance, the soft recovery process is auto-executed by the Exchange Server through the entire pending transaction log file just by reading the checkpoint file. If in case, this auto process does not work, Eseutil commands are being used.
ESEUTIL / r enn/ L [path to log files] / s[ path to checkpoint file] /d [ Path to database file]/ i
Here r stands for recovery mode, enn for log file name prefix, /l specify path to log file, and /d specify the path to database file (it does not includes the name of the file itself). 
Steps are as follows:
•    Execute Eseutil /mh command.
•    Now, check the health of the database
•    If the state is clean shutdown, then from Transaction logs folder location, migrate all the log files and mount the stores; In case it is in a dirty shutdown state, ensure whether Logs required log files is available or not.
•    Next, check whether the required log files are in a clean state or not. To confirm this, execute Eseutil /ml “Path of the log files\log prefix”.
•    Now, if log files are healthy, use Eseutil /r <Log Prefix> /l “Path of the log files” /d “Path of the database” command and execute soft recovery— eseutil/r.
•    On successful completion of all the commands, mount the stores.

If in case, an error is generated—“Operation terminated with error -1216 (JET_errAttachedDatabaseMismatch, An outstanding database attachment has been detected at the start or end of recovery, but the database is missing or does not match attachment info) after n seconds”.  Then just run soft recovery using “/i” switch. This action will override the EDB-STM mismatch and resolve the error. ¬¬

Hard Recovery

Hard Recovery procedure uses online backup to replay log files. If, in any circumstance, the “Last Backup Set” option is set on, then the recovery process can be executed automatically. In this recovery process, there is no need of a checkpoint file as database recovery is performed using restore.env file. Adding more, in the scenario, when “Last Backup Set” option is not enabled, hard recovery is to be executed manually using Eseutil command.

Syntax to execute Hard Recovery:
C:\Program Files\ Exchsrvr\bin.eseutil /cc “ C:\Temp\First Storage Group “_

Here, C:\Program Files\ Exchsrvr\bin.eseutil / indicated Eseutil installed location, C:\Temp\First Storage Group “_ indicates restore.env folder location.

Note: This recovery process will only work on the restored databases from the valid backup. No other Exchange server EDB files can be recovered using it.

Steps are as follows:
•    Go to C:\Temp
•    Check the log restore location
•    Now, open the folder and check for the Restore.env location
•    Now,  use the copy of Restore.env location as well as logs to execute Hard Recovery
•    Go to command prompt
•    Run the Hard recovery from Bin folder using Eseutil /cc “Path of the restore.env containing folder” command
•    After a successful completion, the Restore.env folder will be empty
•    Now, stores are ready to mount

Inevitably, with hands on this manual process, an individual can recover Exchange Database with log files. However, this recovery process is a bit lengthy and is not free from manual intervention. Therefore, it becomes prone to risks. To overcome this, a third-party recovery solution would serve the purpose as it is fully automated and free from manual interference.

Based on experienced and skilled professionals, if a suggestion is to be made then, Stellar Phoenix Mailbox Exchange Recovery is a sure-shot. It is tried, tested, and an approved software solution.

About Stellar Phoenix Mailbox Exchange Recovery
Stellar Phoenix Mailbox Exchange Recovery is an ultimate utility designed to repair corrupt Exchange Server Database Files. This professional solution works in almost all scenarios of data loss, be it corruption, crash, damage, etc. With hands on this software, an individual can quickly repair EDB Files as well as mailbox content such as Calendars, Journals, Contacts, Emails, Attachments, Tasks, To Do List, and much more.

The overall functionality of this EDB Files Recovery tool is simple; three intuitive steps—Select, Scan, and Save. It is fast, easy, reliable, and secure. This do-it-yourself software is highly demands its impressive option sets, improved features, and amazing look & feel. Adding more, it offers you with the flexibility to save the recovered data into varying formats such as HTML, PST, RTF, EML, MSG, and PDF.

This ultimate Mailbox Exchange Recovery software supports PUB.EDB files repairing, Windows 10, 8.1, 8, 7, Vista and Windows Server 12 and 8. Additionally, it is compatible with the MS Exchange Server 2016, 2013, 2010, 2007, 2003, and 2000.

The Way Forward
Nowadays, Exchange is one of the most popular mail servers. This Server is used at a gigantic scale for scheduling, tools, emails, etc. Thereby, it is necessary to ensure proper functioning of the same for increased productivity as well as management. However, just like other utilities, it is also prone to getting corrupt or damaged. Here, Exchange Recovery becomes imperative.


Post a comment