Repair Exchange 2013, 2016 Database using Eseutil or Isinteg

Repair Exchange 2013, 2016 Database using Eseutil or Isinteg

Each and every professional user has to face the misery of database corruption once or in frequent basis. However, there are some tracts available to rescue it with tools provided by Microsoft. Whenever EDB gets corrupt, there are mainly two options available to get the database back to the normal state or in the healthy state.

The two available ways are restoration or repairing the database. The restoring is a process which is based upon database backup, you can utilize this option while you have efficient backup whether you have to go through the second option available as repair. Frequently, Microsoft built-in repair applications – Eseutil and Isinteg are using to repair EDB.

Well, both tracts have their own set of advantages and disadvantages. The restoration tract is the easiest way to accomplish the tasks however, it’s not worthy if you don’t have updated database backup. The repairing tract is a little bit good with the built-in repair utilities – Eseutil and Isinteg. But should keep in mind, it is auxiliary for mere minimal corruptions.

The Eseutil assist in recovering the database with the assistance of two procedures – soft recovery and hard recovery.

Before execution of repairing EDB by utilizing Eseutil command, keep in mind the following given points:

  • The first and the mandatory point is, you should take care of your database. So, take a valid backup of current EDB database with its log files and save it at a safe location. The taken backup database will help you out, in case your actual database get corrupted while execution of repairing with Eseutil command.
  • Be assured of adequate space on the disk or drive to execute a successful data recovery. Since repaired database obtain free storage space up to 20%.
  • If this requirement cannot fulfill; then ensure that windows command line should also include a command to redirect the repair Exchange Database file on other location.
  • Calibrate the free space in your disk by searching your application log for Event ID 1221. Alternatively, utilize Eseutil MS utility for the current calculation.
  • Check that the.STM and.EDB files exist in the same directory or not.
  • Eseutil commands merely execute on online database, therefore, the requirement for dismounting the database during EDB repairing of 2010/ 2013/ 2016 is almost nil.

Well, the articulation cannot accomplish without knowing moreover about errors. So, here I’m going to put some more facts and variable of errors occurs in MS Exchange.

Exchange 2013, 2016 Database Repair through Eseutil an Isinteg is used for the given MS Exchange errors.

  • Errors occur in Provisioned Folder: When inside of folder structure gets an error for special or diverse mailboxes. Those folders are known by the name of Provisioned Folder.
  • Errors obtain in Search Folder: Albeit Search folder are utilizing to detect and fix the exists corrupt file. However, there are instances when Search Folders are identified with errors.
  • Error happens in Specific Folders: The demonstrated content in specific folders gets allied with errors which cause wrong results in View Folders.
  • If the particular folder is incapable to come back with the correct.

These errors may corrupt EDB, and can also get corrupt due to diverse other factors too. These factors are improper system shutdown, malfunction, virus invasion, software or hardware failure, may Jet Engine failure too.

The above-given errors can be fixed utilizing Eseutil and Isinteg. However, various versions of MS Exchange are repaired differently. So, I’m going to give you an idea of repairing MS Exchange 2013, 2016 database only.

Tract to repair MS EDB 2013, 2016

The Eseutil and Isinteg command execute in three parts. The Eseutil scans, repair and defrags low level of corruption in EDB and Isinteg overcome Information store Integrity. Both of these commands execute on Exchange in offline mode. Hereby, you should keep in mind before running the commands:

  • When there are minimal numbers of users or no users for Exchange
  • You don’t have any crucial tasks to accomplish

Three process of Eseutil and Isinteg commands execution.

  1. Do command to Eseutil/p command – to do database repair for page-level & table-level repair
  2. Run Eseutil/d command – to Recreate Indexes and defragments the EDB
  3. Perform Isinteg command – to mend EDB at the application level

 Tract to repair EDB 2010 with Eseutil

 Go through with the given below steps to execute repairing of Exchange 2010 database.

  • Firstly switched off- the MS Exchange server
  • Then, open command Prompt on that system where Exchange server installed- //Eseutil/

Repairing with command Eseutil/P:

When there is no chance left to restore EDB through the backup. You will have to utilize the Eseutil/p command.

Eseutil/p command resolves corruption in EDB files by removing the irremediable EDB file pages. Go through the following syntax to repair Exchange Database utilize the given command:

eseutil /p <DBFileName.edb>

The Eseutil/p command can resolve the individual database tables, but this MS Exchange utility cannot make links between databases tables. The link can join through the Isinteg MS Exchange utility.

Defragmentation process with Eseutil/d

The defragmentation is a process which decreases the quantum of the Exchange database by removing the white spaces exists in an Exchange database. You can execute defragmentation through the steps given:

  • Firstly, go to the system manager
  • Do right click on the Info Store
  • Then, click on the info store
  • Then, Switch off the server
  • And fend user to access their accounts
  • When the server goes offline, embed the following command:

eseutil /d <DBname>

  • Then, Next step will be the creation of a New Database
  • Finally, move entire mailboxes from the old EDB to the newly created EDB

NOTE: The offline Exchange Defragmentation is not suggested as a steady patronage option. Because it’s different from online defragmentation as the latter runs every night and doesn’t allow recovery of white space.

Fix Gaping Holes with the assistance of Isinteg

The Isinteg command transacts with rational corruption inside structure of EDB. The Isinteg command assists in removing all corruption elements.

But the problem arises when MS Exchange utilities are incapable to resolve the corruption in EDB.

Calibrate corruption in the EDB with Eseutil/mh command

It is mandatory to calibrate that EDB 2013, 2016 for any activity. Afterward, utilizing Eseutil or Isinteg to resolving the error in corrupt EDB.

Check the EDB results may results not worthy for you or you may get an unexpected solution for the error.

Every professional user are aware of MS Exchange utilities Eseutil and Isinteg commands, may they also know the limitation of these commands. There could be some problems where the MS Exchange applications fail to execute, considerably in repairing harshly corrupt EDB.

It’s recommended that MS Exchange shouldn’t be assistive in massive corruptions instantly, else these steps may result as a disintegration in business communications. Technical Experts recommend an alternative software to resolve massive corruptions using Shoviv Exchange database recovery software. This is proficient software to resolves massive corruption. It supports MS server 2016, 2013, 2010 and entire older versions too.

Wrapping Up:

Hope, you liked the articulation based on the crucial lifeline of communications. Every exchange is the lifeline of a business, it should be running 24*7. This articulation will help you out from every type of EDB’s error if you try with the suggested step.

Note: We have another option named Exchange Recovery Manager tool to repair Exchange 2016, 2013 database. It has a free Trial version as well.

Write your comment Here

Scroll Up