It’s too common anxiety for all administrator of crashing Exchange Server. And they want to settle the problem of Exchange Server Crash as easily as possible. In this session you like the solution of Exchange Server Crashing I’m going to tell you right now.
Probably we know the Exchange database is a warehouse of information. Vast quantum and number of user mailboxes inclusive emails, contacts, notes and more consist within Exchange EDB files and the responsibility to keep them safe lies with the database administrator. A single emergent activity could lead to loss all of critical data and huge losses for any organization. Thus, suitable backups are maintained to low the risks as much as possible and assure the server can be brought back to its working steadily.
It’s too common anxiety for all administrator of crashing Exchange Server. And they want to settle the problem of Exchange Server Crash as easily as possible. In this session you like the solution of Exchange Server Crash I’m going to tell you right now.
As available I’m going to tell about two numbers of Exchange server recovery options to the users, which are Eseutil Soft Recovery and Eseutil Hard Recovery. Firstly, should aware of both recovery options:
Let’s find What’s the definition and what is the difference between?
The procedure of replaying transaction log files when a database is re-mounted on Server after confrontation of emergent stop. And they are rerun against an offline copy of the database.
As I’ve mentioned, This recovery performs against offline database. The recovery has to be processed manually using ESEutil tool.
Hard recovery must be completed after restoring from online backup. Hard recovery transaction log file run process that seem similar as soft recovery, but there are some exigent odds. In hard recovery, these differences make it different from Soft recovery:
Given info must be applied to the database while logging file replay.
The checkpoint file ignored. Restore.env is used instead of the checkpoint file to accomplish from which log file recovery can start.
Exchange Server 5.5 users may be familiar with the Restore in Progress registry key. Restore.env replaces the functionality of that key in Exchange 2000 Server. You can see the contents of the Restore.env file by commanding to run Eseutil /cm.
If database has been restored to a different path than that from which it was backed up, log file replay succeeds, ignoring the database paths listed in the log files.
Restored transaction log files rerun first from a streaky folder designated by the user before restoration. Log files from the normal transaction log folder may also be rerun.
Hard recovery doesn’t fail whether other databases in the storage group have missed.
In short we perceive that Soft recovery plan helps to recover the server through the offline database. While, Hard recovery plan make differ itself by restoration online database.
Now time is come to know how to perform Soft recovery & hard recovery in exchange server.
First, I’ll tell you about Soft recovery and then hard recovery or repair.
The morphology will use for Eseutil.exe soft recovery as given below:
Soft recovery :
To do Soft recovery execute, you must named the last file in the replay sequence Enn.log. However, that file has already been closed and numbered; you must rename the log file before execution for getting best result of soft recovery.
If the recent Enn. Log has been damaged or abraded, you should ignore it and should rename the previous log file in the sequence of Enn.log. And then start execution.
To do Soft recovery execute, we will have requirement of log files. Start with the similar name like E001, E002, E003 if you won’t have with same name you will have to rename log file.
To replay Soft recovery command it’s important to execute the command from the folder where log file reside, and the logs files to be restored within significant path.
I will be switch in the command to fix the streaming error during command execution.
After the performance we should perform eseutil/mh to check the database is in clean shutdown state.
After that process we should try to mount the database.
Still you couldn’t affix your problem and couldn’t mount the database, you have to try the another option the Hard repair or hard recovery.
Before performing hard recovery command, check that you have enough space in the server for the database. During performance of hard recovery because it creates temporary database.
eseutil /p command for hard repair.
After that you can verify the database clean shutdown state by running the command
But in performing hard recovery, you may lose some data from corrupted or damaged file such as corrupt emails, calendar items and some other data during the operation. However to avoid such critical situation, there are some alternative solutions available to affix that too. One I personally tried is Shoviv exchange recovery manager. It is an ideal solution to get around in such circumstances in order to repair corrupt database, recover them and restore all necessary items into either live server or easily accessible PST format. It has free trial and having excellent technical support team available.