Eseutil R command is used for recovery purposes of an Exchange Server database. The /R switch of eseutil enables you to recover data from corrupt Exchange database. Use of this command lets you replay transaction log files or rolls them forward to retrieve a database to a consistent state or help you bring a previous copy of database updated.
Note - Also, you can use special switches- /is and /ds that use the Registry to automatically set the log file path and system file path respectively to perform recovery of particular Exchange store(s).
Usually, when you come across corruption or damage in Exchange Server, you get the following error messages :
Eseutil R mode is utilized when a user needs to perform soft recovery of your Exchange Database(s) Information Store. However, before using eseutil R you first need to check the consistency of EDB databases. To check the Information Store consistency, you can make use of eseutil /G switch.
If any of the EDB files are found in inconsistent state, then you need to carry out soft recovery. During the soft recovery uncommitted logs are committed to the information store. Let us see how to perform soft recovery on priv.edb and pub.edb files:
After performing soft recovery on priv.edb, execute the following steps to perform soft recovery on pub.edb file:
Note: /ispriv and ispub are optional; therefore, if you do not want to use it, specify the location of log files. For example, if you do not use ispriv or ispub then the syntax will look as <Drive>:\ program files\microsoft \exchsrvr\bin> eseutil /r /Path_Of_Log_Files
Eseutil R command allows you to perform soft recovery and bring the priv.edb and pub.edb files in consistent state. But, after you perform soft recovery using Eseutil R command, you need to check the consistency state of database again. In usual soft recovery situation, an external event stops Exchange database abruptly but the database and log files remain integral. In this case, when the database is mounted again, Exchange reads the checkpoint file and starts replaying the transaction log that is listed as the checkpoint log. If no checkpoint file is found, replay initiates the previous log file available in the transaction log folder for the storage group.
Exchange adds the completed transactions in the log files to the database files that were either not written or undo in the database. Although, the above-mentioned method must help you in bringing your database into a consistent state but at times this command-line method fails to help you in retrieving your database in consistent state, you can take help of Exchange Server Recovery software to perform flawless Exchange Server Recovery tool and restore your vital data efficiently.