wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Exchange integrity check ======

https://www.stellarinfo.com/blog/how-to-use-eseutil-for-exchange-database-repair/

If you need to backup without integrity check, maybe your Exchange DB needs to be repaired ?

:!: Points to Remember Before Using EseUtil for Exchange Database Repair

**You must remember the following important points before using the EseUtil:**

  * EseUtil is not a fool-proof utility. It may fail and cause more damage or data loss based on the recovery method you choose and the level of database corruption.
  * It’s not necessary that you will be able to mount the database after recovery.
  * Depending on the size of database and the level of damage, your users will not be able to receive, send, or work with their mailboxes during the EseUtil database repair process. This could lead to several hours of downtime and may cause damage to the business.

**Prerequisites to Run EseUtil**

Before you run EseUtil to verify, modify, or repair Exchange databases, you must ensure the following prerequisites,

  * Backup Exchange database file
  * Administrator access or permissions
  * Free storage space (at least 1.2 times of database size)

===== Steps to Use EseUtil for Exchange Database Repair =====

**EseUtil** is located in the program files uexchange path
  C:\Program Files\Microsoft\Exchange Server\V15\Bin\ 
  
==== Step 1: Check Database State ====

To identify the database state, use the /MH switch. If the state is displayed as Clean Shutdown, there shouldn’t be any issues and the database can be easily mounted after moving all the log files to a different location.

However, if the database is in Dirty Shutdown state, the database won’t mount. This indicates an inconsistent or corrupt database. This may occur due to missing or deleted log files and when log files are not committed to the database.

The command to check database consistency or state is as follows,
<cli prompt='>'>
c:> eseutil /mh <database file name>
</cli>

==== Step 2: Check Logs ==== 

If your database is in Dirty Shutdown, you will see another line under it, which mentions the log file that is required. The next step is to check if the logs are healthy or if there is a problem with the logs. To do this, use the ML prefix with EseUtil and the log path that you can copy from the Log Required section of the report.

<cli prompt='>'>
c:> eseutil /ml "M:\mbx01\logs"
</cli>

==== Repair index ====

**IsInteg** tool for Index Repair. IsInteg is a repair only utility that understands relation between tables and records and turns them into folders and messages. The tool is located at the following location,

C:\Program Files\Exchsrvr\bin>

Then run the IsInteg test by using the following command,

<cli prompt='>'>
c:> Isinteg –s <server_name> -fix –test alltests
</cli>

You may repeat the command multiple times to get rid of errors. Once errors are fixed, you can mount the database.

Further, you can use **New-MailboxRepairRequest**, if you have Exchange Server 2010 with SP1 or later versions, before mounting the database on the server. One more thing, you cannot stop the process once it started. If you stop it anyway, it may cause even more damage to the database. However, if all goes well, you will be able to mount the database.
wiki

User Tools

Site Tools

Page Tools
