0 Exchange 2010 database repair

Exchange server database repair.
PN: Ramifications of running the eseutil /p  or  edbutil /d /r command.


1. Make sure the databases are dismounted in ESM.
2. Before running the Hard Repair, I would suggest you to make a copy of :

1. priv1.edb
2. priv1.stm
3. pub1.edb
4. pub1.stm

From a command prompt, run eseutil in the repair mode syntax should be:

Eseutil /p "c:\program files\exchsrvr\mdbdata\priv1.edb" 

• Using ESEUTIL /p is a last resort utility that is only run ,when databases will not mount due to inconsistancy.
• ESEUTIL /p deletes any data needed (corrupt data or incomplete transactions) to bring the database to a consistent state.
• ESEUTIL /p runs at about 3-5 Gig of data per hour.

 NOTE: Do not click in the command prompt screen, 
            it causes the ESEUTIL process to PAUSE. 
            Press the F5 key to resume.
            
3. Once that completes, run the same command against the pub1.edb file.
4. Run an offline defrag of both databases. The syntax should be:
              Eseutil /d "c:\program files\exchsrvr\mdbdata\priv1.edb"
            

• You must have at least 110% free space, relative to the database size to run ESEUTIL /D.
• If you do not designate a temp location using the t command, it defaults to the directory EXCHSRVR/BIN
• ESEUTIL /d runs at about 3 to 5 Gig per hour
• After running /d you must remove any log files in the MDBDATA folder before mounting the database.
• How to Defragment with the Eseutil Utility (Eseutil.exe) 

5. Once that completes, run the same command against the pub1.edb file. 
6. Disable the SMTP service prior to mounting the databases to prevent new email from coming in to the databases. 
    Mount the databases with the repaired/defraged database. 
    Logon to make sure you can access one of the mailboxes, but will want to then immediately dismount both of the stores 
7. You will then need to run an isinteg to fix any corruption at the store level. 
    The syntax should be: 
Isinteg -s servername -fix -test alltests 

- ISINTEG Must be run after ESEUTIL /P or ESEUTIL /d to remove logical corruption caused by deletions 
- ISINTEG -FIX runs at about 2 to 10 minutes per Gig of data 
- Select the database to run the utility against. (The database must be dismounted)
- ISINTEG will create a log file named ISINTEG.PRI in the MDBDATA folder (open with Notepad)
 - Note the number of FIXES we get after each run of ISINTEG -FIX. We will need to run this till we get 0 fixes.
 - This may take 3 or more times.
 - Also note the number of errors we get after each run of ISINTEG -FIX
 - Once we get 0 FIXES note the number of errors. 
 - Description of the Isinteg Utility http://support.microsoft.com/?id=182081

Source : LINK