Do you often encounter EDB files that are too large to handle? If so, then you could also be in danger of your Exchange server running short of storage space.
When excessive amounts of data pile up in an exchange database it can reach the file size limit and cause server crashes, outlook application collapses or even a sudden halt of the entire communication medium. Trying to remove data chunks may not help in this scenario since the compression of the EDB file will not take place in the correct way.
In this blog, we’ll discuss three different ways you can repair oversized EDB files without losing data.
- One way to handle oversized EDB files is to migrate data from the old mailboxes to new mailboxes after building a new mailbox database. However, mailbox migrations can be both time-consuming and complicated when you consider the excessive number of logs generated from the large volume of information.
- Another solution is known as the defragmentation technique. This is performed by running the “Eseutil” command in offline mode to track the size of the exchange database file and allow its compression. To defragment the EDB mailboxes using the Exchange management shell, you must dismount the database before starting the defragmentation process. However, users must have enough storage space available on their disk drives to execute the defragmentation.
It is important to note that no user, inside or outside the organisation, will be able to access these mailboxes while the process is ongoing. When the defragmentation is complete, new EDB files are created from scratch (despite continuing to remain on the systems of users).
- The third solution is to alter the location of the mailbox database by executing the following procedure. This procedure will increase the data storage capacity of the exchange database file:
Step 1 – In register editor, look for the following path
Step 2 – Firstly, change the storage limit to GB and then increase it by specifying a higher amount of available GB under the last field of the above path i.e. in the field “Private-<databaseGUID>”
Step 3 – Finally, restart the Exchange Information store and check the event viewer for Event ID 1216 to figure out the current size of the database.
The Final Verdict
The three methods discussed in this blog should help you to repair oversized .EDB files in a working Exchange database. Unfortunately, none of the methods will be successful if your exchange database turns out to be corrupt. However, many third party solutions, such as Lepide Exchange Recovery Manager, allow users to extract information; including mailbox folders, individual mailboxes, embedded attachments and email properties from even the most severely corrupted or damaged exchange databases without leaving any impact on data hierarchy.
Latest posts by Ajit Singh (see all)
- 3 Ways To Fix Oversized .EDB Files - November 23, 2016
- A quick overview of migrating from Exchange 2007 to Exchange 2016 - September 21, 2016
- Migrating to Exchange 2016 using the Exchange Admin Center - February 24, 2016