Repair Exchange 2016, 2013, 2010 Database Via Eseutil or Isinteg
In this blog, we are going to explain a manual solution to repair Exchange 2016, 2013, 2010 Database using Eseutil & Isinteg Utility. Before preceding this, first we will discuss various permissions that required to repair the database.
Microsoft Exchange is being widely used in large-scale organizations for sharing data and vast communication. It can store a huge amount of data in Exchange EDB file, which is sometimes called Exchange mailbox. EDB database file includes emails, calendars, task, journals, notes and so on.
Once the database becomes large, then there would be more chances of data corruption. In order to detect and fix corruption by performing the New-MailboxRepairRequest cmdlet in Exchange 2016.
Few Points to Remember – MS Exchange Corruption
Here are few points to remember while using Eseutil command. Although, before you start to repair files, take care of the following points:
- First, you should make a copy of the original database and log files and save it somewhere safe. This copy should be located in a working directory, the reason being if things go wrong while repairing an actual database, this copy will be used as an original document.
- Make sure that the disk space is ample to do a recovery. Repaired database acquires a free storage space, thus at least 20% of database size must be available. In any case, there is not enough disk space, the Windows command line should switch to redirect all the repaired files on different location.
- Confirm that both Exchange database files (.edb and .stm) are present in the same directory.
- It works with an online database, so there is no need for dismounting the databases for repairing Exchange 2010, 2013, 2016 Database using Eseutil.
Repair Exchange 2016, 2013, 2010 Database Using Eseutil -Ultimate Solution
To overcome all such limitations, one is advised to opt for a reliable and trustworthy solution that is Exchange Mailbox Recovery Tool. With this utility, the user can recover & repair EDB file and mailboxes from low and high-level corruption without any hassle.
In addition, the recovery manager for Exchange database software is designed with a user-friendly interface which makes it easy for end-users to work with it. Both technical, as well as non-technical users, can operate this software without any complications.
When user recovers and repair Exchange mailbox as well as Exchange database file from corruption, then they can export the recovered Exchange database mailboxes directly to the Live Exchange Server mailboxes, Office 365, and PST, MBOX, MSG, EML, HTML PDF file format in a simplified way.
Some Possible Corruption Types in Exchange EDB
New-MailboxRepairRequest cmdlet in Exchange can be used in the following conditions for those are mentioned below:
In the Provisioned folder, the error may occur in a folder structure within the mailboxes.
Search folder issue may be able to detect and resolve all the corrupted files. However, some of the errors took place in the search folders.
Under folder view, errors are associated with the displayed content in specific folders. View folders have become fail for returning the correct results.
Aggregate counts on the desired folder that are not able to return the true values. Errors can display the number of items and their size inside a folder.
Grant All Permissions Before Execution
Before implementing New-MailboxRepairRequest command in Exchange 2016, there are multiple permissions that required to repair Exchange database. There would be several parameters such as StoreMailbox, Corruption Type, Database and etc., which are not permitted to access if they are not counted the permissions. Further, a new command works online with MS Exchange database, even it does not request to dismount the database while executing these fixing errors.
Different Ways to Repair Exchange 2010, 2013, 2016 Database (Eseutil / Professional Solution)
However, Exchange DB may become damaged due to certain reasons like improper system shutdown, program malfunction, virus attack, hardware failure, database engine failure, etc., yet there are multiple solutions provided by Microsoft for Exchange 2013 Database Repair like Eseutil. Every version of Microsoft Exchange has its own way to repair DB.
Exchange 2016, 2013, 2010 Database Repair Using Eseutil
There are two types of utilities, named eseutil.exe and isinteg.exe, to recover data. Moreover, ESEUTIL is used to scan, repair, and defrag the low level of database whereas ISINTEG being used to overcome Information Store integrity. These applications require Exchange database in an offline mode. Run Eseutil and Isinteg command as stated below:
a) Repair Exchange 2016 / 2013 / 2010 Database Eseutil /p
This command helps to scan .edb mailbox and repair file if it finds any type of issue. Execute the below command:
b) Eseutil Defrag Database: Eseutil /d
Eseutil /p removes highly corrupt or damaged pages instead of repairing them, which may create few white spaces. All these empty spaces or unused storage can be deleted using eseutil /d which defragment an Exchange DB.
c) Exchange ISINTEG Utility
Isinteg tool is complementary to Eseutil and it can be used to retrieve the database and repair the structure and integrity of Exchange DB when Eseutil finished the process.
Repair Exchange 2013, 2016 Database Eseutil
Let us discuss the following procedure of New-MailboxRepairRequest by using these below examples:
a) Need to detect & repair all Folder Views for Bob’s Mailbox
b) Find and report SearchFolder and ProvisionedFolder corruption issue to Joe Mailbox. The below new-mailboxrepairrequest Exchange 2016 script does not repair the specified DB.
c) Detect and repair the AggregateCounts for all users mailbox on the Exchange database. For Example-DB01.
d) Detect and restore various corruption types for Eli Mailbox and archive all redundant items.
e) Creates variable to identify Eli’s mailbox. Later on, this variable is used to specify all the values for StoreMailbox and Database parameters to create the request. It will also help to detect and correct all types of existing corruption issues.
Challenges Faced While Using Manual Approach
In case, the above-stated methods may still not resolve the corruption issue. Some of the most common problems include:
- An Inbuilt utility cannot perform the Exchange 2013, 2016 Database repair if the corruption level is very high.
- Sometimes, the database is in the .stm file which is placed at a different location than the .db file. Then, using the Eseutil utility becomes a futile attempt.
- The database may not have enough disk space which hampers mounting of the repaired database.
Time to Conclude
In this write-up, we have discussed some pre-requisites and different ways to repair Exchange 2016, 2013, 2010 database using eseutil and isinteg tools and commands. But, sometimes the manual methods do not provide accurate results thus, users can go for a reliable and secure automated solution mentioned in the above segment.