Read time 3 minutes
Database management in Exchange Server is a serious concern for Exchange administrators. Space freed up after the deletion of data remains unclaimed, which creates the need for the admins to manually claim and use this space to store future data. Microsoft provides an in-built Eseutil utility which helps in defragmentation of Exchange Server database. Defragmenting Exchange database means that the white space is recovered. When you perform this, the database shrinks, which makes more storage space available to enter the new data.
Common Causes of Defragmentation Failures in Exchange Server
- Database corruption: Your Exchange database may be inaccessible or corrupted due to network or other issues.
- File saved locally: EDB or database file you’re working on is saved on your local storage.
- Not enough storage space: There is not enough space available on the destination to accommodate the data you’re migrating.
- Improper database dismount: The Database you’re working on wasn’t properly dismounted during the backup or migration process.
How to Defragment your Exchange Database?
EDB file defragmentation is done when the database is in an offline state, and no one can access it. Therefore, it is also termed as offline defragmentation of EDB files. Before you begin the defragmentation, make sure you have sufficient disk storage available to handle a temporary file that gets created during the defragmentation process. The standard command for defragging an EDB file is
Sometimes, while performing defragmentation, you might encounter failure, and the process may get stopped. Even the temporary created file Priv1.edb gets lost after renaming. These symptoms indicate that your mailbox or the EDB file is facing corruption. To repair EDB files, open the command prompt as Administrator and run the following command:
Eseutil /P {“database_complete_path”}
The above command only works with minor issues, if the command fails to fix the problem, you will get an error like this:
Until the error is resolved you will not be able to perform any operation on the EDB file, such as access emails or defragment Exchange EDB file. Users, dealing with this situation, come across these error messages due to damaged Exchange Server database. The database corruption might be a consequence of dirty system shutdown error , virus invasion, over-sized EDB file, etc.
How to Fix a Corrupt Exchange Database?
You cannot handle severe database corruption with Microsoft’s Eseutil – free command line tool. To safely remove the damage without losing your data, use Exchange data recovery tool to repair a corrupt Exchange database.
Kernel for Exchange Server seems a suitable option when it comes to resolving database corruption. It repairs EDB files created with Exchange Server 5.0, 5.5, 2000, 2003, and all later versions. Moreover, with the integration of the advanced algorithms, the tool scans the entire database and makes it accessible and healthy.
Top features of this advanced Exchange Server recovery software:
- Recover complete mailboxes, including deleted items from corrupt EDB files.
- Repair and migrate EDB to Live Exchange, Exchange Online, Outlook, etc.
- Built-in search feature to find and save particular emails.
- User-friendly interface with fast operational speed.
- Save entire mailbox data or recover specific items with filters.
The tool also provides a free evaluation version that allows you to use the software before purchasing the Full version. The demo version will recover the Exchange Server items but with a limit of only 25 items per folder only.
Conclusion
The article describes the corruption issues in EDB file faced by the Exchange administrators while performing the offline defragmentation of the EDB file. It explains the use of the eseutil command to perform the EDB file repair, but this can be complex for a non-technical user. For a simple and straightforward process, use a professional Exchange recovery tool.
Frequently Asked Questions
Ans. Run the following command in the Exchange Management Shell to check the state of the Exchange database:
eseutil /mh “C:\Path\To\Database.edb”
As a result, the command will show if the database is in Dirty Shutdown or Clean Shutdown state.
Ans. Here are three practices you can follow to avoid issues after defragmentation:
1. Take regular and full database backups before beginning the process.
2. Make sure there is 110 to 120 % space of the database size in the destination.
3. Avoid sudden or abrupt shutdowns and other interruptions in the process.
