The idea of repairing Exchange database using ESEutil is an old technique and honestly, there are very less number of administrators who prefer it. As versions of Exchange Server have improved, the ways to maintain database, move mailboxes, recovering and repairing DBs have also changed. Now instead of preferring the veteran command line utility for resolving page-level corruption of EDB file, Exchange Management Shell commands are used.
Some Reasons Why ESEutil is a Failure!
Although ESEutil have been a part of Exchange Server management tools from version 5.5 to 2013, still there are some reasons why it is a last resort to bring inaccessible database into functional state.
Reason #1) To use ESEutil for any job (recover, repair, defragmentation etc), the EDB file has to be dismounted from Server.
Reason #2) Repair process with ESEutil /p switch has to be followed by defragmentation with /d switch and application level repair with ISInteg.
Reason #3) ESEutil is meant to handle physical database corruption that occurs at page level. Damage to DB at application level cannot be handled with it.
Reason #1) To use ESEutil for any job (recover, repair, defragmentation etc), the EDB file has to be dismounted from Server.
Reason #2) Repair process with ESEutil /p switch has to be followed by defragmentation with /d switch and application level repair with ISInteg.
Reason #3) ESEutil is meant to handle physical database corruption that occurs at page level. Damage to DB at application level cannot be handled with it.
New-MailboxRepairRequest Cmdlet: How Helpful It Is?
With Exchange 2010 and 2013, New-MailboxRepairRequest PowerShell command was introduced that gave a platform to repair mailbox, database, or entire Server DB. This cmdlet helps to detect and repair corruption issues when the DB is mounted on Server. If an entire database is selected for repair process, the only mailbox that will be inaccessible at user’s end would be the one that is currently processed. Simply, an answer for how to repair Exchange 2013 database and that too free of cost!
In order to avoid any performance issues, a limit is being assigned for number of requests per Server that can be placed at a time for processing. When a database-repair request is made, only one request can be created and for a mailbox, a maximum of 100 requests for mailbox–level repair can be made. This limitation is for simple Server.
Note: Status of mailbox repair process can be checked in Event log and if repair process fails, an event 10049 will be registered.
In order to avoid any performance issues, a limit is being assigned for number of requests per Server that can be placed at a time for processing. When a database-repair request is made, only one request can be created and for a mailbox, a maximum of 100 requests for mailbox–level repair can be made. This limitation is for simple Server.
Note: Status of mailbox repair process can be checked in Event log and if repair process fails, an event 10049 will be registered.
Recovery over Repair: What do you Prefer?
Using ESEutil and New-MailboxRequest cmdlet for bringing Exchange mailboxes or databases to functional state have their own advantage. According to the requirement of administrator and size of organization, any of the modes can be chosen to repair EDB data.
However, over the time, many third party solutions have been introduced that gives a platform to recover database instead of repairing it. Example: Recovering EDB to PST. There are number of benefits of choosing Recovery over Repair:
Benefit #1: Recovering user-mailboxes into PST helps to resume work flow while planned or unplanned downtime within organization.
Benefit #2: User-mailboxes and public folders saved in PST can be exported to different Server. This way, scenarios like Server failure can be handled.
Benefit #3: Any number of databases (EDB files) can be recovered. This also helps in maintaining brick-level backup of mailboxes.
As a suggestion, a name that can be trusted for recovering Exchange EDB database to PST is Exchange EDB to PST Converter software. This solution can be invested to recover EDB to PST, EML, MBOX, MSG, and PDF files.
However, over the time, many third party solutions have been introduced that gives a platform to recover database instead of repairing it. Example: Recovering EDB to PST. There are number of benefits of choosing Recovery over Repair:
Benefit #1: Recovering user-mailboxes into PST helps to resume work flow while planned or unplanned downtime within organization.
Benefit #2: User-mailboxes and public folders saved in PST can be exported to different Server. This way, scenarios like Server failure can be handled.
Benefit #3: Any number of databases (EDB files) can be recovered. This also helps in maintaining brick-level backup of mailboxes.
As a suggestion, a name that can be trusted for recovering Exchange EDB database to PST is Exchange EDB to PST Converter software. This solution can be invested to recover EDB to PST, EML, MBOX, MSG, and PDF files.