Dealing with an oversized Exchange database (.EDB) file is always a complex process and a proper care require to be taken to fix the issue. In fact, if as the EDB file grows out of control and reach beyond its specified volume rapidly, the possibility of Server running out of space too increases drastically. The important point to note is that as more data gets collected in the respective EDB file, its size automatically starts growing but even if you remove or delete any data is removed the file doesn’t compress at all. In fact, these free space are taken over by white spaces afterward. So, it is very important to deal with such issues immediately. There are different solutions to deal with such circumstances:
- You can create New Mailbox Database and export entire data to the new Mailbox
- Carry out Offline Defrag to shrink and reduce the size of the EDB file
- Move the location of Mailbox Database
Now, in the alternates just mentioned above, if you perform any sort of mailbox migration then you got be very cautious. Performing any sort of migration is too a complex procedure and involves high risk of losing the data contained in the EDB file. Adding to that, a large transaction log is generated and there is a high possibility of consuming enough time for the entire procedure to get accomplished. Nevertheless, you can defrag the mailboxes and reduce the EDB file size.
Run Eseutil to Defrag EDB Mailboxes via Exchange Management Shell
You got to keep a close look on the size of the respective EDB file. If the size of a EDB file keeps growing abnormally and you desire to shrink the file, then there are some vital pre-requisites that need to be taken proper care, such as:
- The Exchange server database must be dismounted before you initiate the defrag process. Also, during the defragging procedure, do remember that users won’t be able to contact their emails.
- During this entire defrag process, a new file gets created. Consequently, proper storage space must exist on drive as the old file in addition with new file and temporary file as generated by Eseutil all exist on system.
- Just in case, if proper storage space doesn’t exist, you could very well specify different location while executing Eseutil command.
1.Run the Exchange Management Shell and after that perform the following command in order to successfully dismount Mailbox database:
“C:\ Windows\ system32>cd D:\ Mailbox\ ‘database name’”
“D:\ Mailbox\ ‘database name’> Dismount-Database ‘database name’”
2.Run Eseutil to defrag the EDB file successfully
“D:\ Mailbox\’database name’>eseutil /d ‘database name’.edb /t\\ testserver \defrag\temp.edb”
3.Execute the following command to mount the database:
“D:\ Mailbox\ ‘database name’> mount- database ‘database name’”
After this, make use of a Exchange Management Console to dismount database. You just require to select the Mailbox, then right click on it and choose the Dismount Database option. After the operation is accomplished, a task completion information box will appear. Now examine the size of a database and the current white spaces on the selected mailbox database. You could easily notice the compressed size of a EDB file.
Besides this, you could also alter the size specifications for the database. In fact, you could split the EDB file and further prevent big data loss situations. To do so, you require to follow the following steps:
1.In Register Editor, search out for the path as mentioned below:
2.If “Database Size Limit in GB” DWORD exists under “Private-[database GUID]” so change the value to GB (gigabytes).
3.Restart the Exchange Information Store
4.In the Event Viewer, check for “Event ID 1216” to have the right idea of the current size
By following this simple process, you can very well rise data storage capacity of a EDB file which in turn further decreases the instances of corruption of Exchange database files.
However, the solutions explained above cannot be used to deal with corrupt EDB file. In situations where EDB files involves corruption, then you could very take help of a third party EDB to PST Converter.