Offer Offer

News We Recently Launched AD Migrator and AD Reporter.

What To Do If Exchange EDB File Too Big?

  author
Written By Chirag Arora  
Anuraag Singh
Approved By Anuraag Singh 
Published On June 27th, 2024
Reading Time 8 Minutes Reading

Microsoft introduced the Exchange Server in 1993. EDB files came into existence, with the introduction of Exchange server. The most common issue raised by the many users is Exchange EDB file too big and requires compression. In this blog,solution to to reduce edb file size exchange 2003, 2007, 2010 & 2013  has been discussed and explained.

What Is An EDB File?

EDB stands for Exchange Database file. It is the main repository of Exchange Server database for mailbox data. It includes all data components like email, messages, attachments, folders, etc. These files are formatted using the b-tree structure which provides quick access to many pages at once. Each EDB file has a corresponding STM file that contains the actual SMTP messages.

Why Exchange EDB file Too big?

The Exchange EDB files will automatically grow in size as the data within the EDB files will increases. However, the EDB files will never compress if the data is removed from them.

Suppose the size of EDB file is 15 GB and we delete 5 GB mailbox or move it to any other database, the size of EDB file will remain 15 GB. However, 5GB white space will be created in the database and that space will be available for the new data to be written without increasing the file size. You can follow the below steps to reduce edb file size exchange 2003, 2007, 2010 & 2013.

Solution: How to Fix Exchange EDB File Too Big?

If your query is .edb File size has grown too large. My server is almost out of space. You can try following methods to reclaim the space.

  • Create a new Mailbox database and move the data from Old Mailbox to New Mailbox.
  • Shrink the Database file by performing Offline defrag.
  • Move the location of the Mailbox Database.

There are some risks in the process of Mailbox migration.It will generate a large transaction log and can take several days to complete the process. In this blog, we will explain the steps to defrag the database by using Eseutil and to move the location of a Mailbox database.

Defrag the Exchange Mailbox Database by using Eseutil

Determining free White Space

You can determine the size of the mailbox and available white space by executing following command in Exchange Management Shell.

Exchange Management Shell

For example the size of the database named as DB2 is 776.1 MB and it has 330.9 MB white space. You can reclaim that white space by shrinking the file using Eseutil to defrag the mailbox database of Exchange 2003 , 2007.

Prerequisites

  • In order to defrag Exchange Mailbox database by using Eseutil, the database should be dismount at the time of defragment. It means users cannot access their email when you are defragging it.
  • A new file is created during the defrag process and the old file, new file and a temporary file that is generated by Eseutil will exists. So you need some disk space for these file to perform defragmentation. If you don’t have free disk space then you can specify a different temporary location while running Eseutil.

Procedure

    • You can run following command on Exchange Management Shell to navigate and dismount the Mailbox database. Since the Mailbox database should be temporarily Dismount before defragging the database.

Dismount the Mailbox Database

    • You can also dismount the database by Exchange Management Console. For that, select the Mailbox you want to move, Right click on it and then click on Dismount Database.

Exchange Management Console

    • Now run the Eseutil to defrag the EDB file of Exchange 2003 , 2007.

Eseutil

    • Mount the database by running following command.

Mount the Database

  • Now you can check the database size and available white space of selected mailbox database. You can see the results that file size is small and the white space is gone.
    As the Eseutil is completed, run the full backup of the database.

Move the Database by Using Exchange Management Console

Procedure:

    • Open the Exchange Management Console, in Organization Configuration select Mailbox of Exchange 2010.
    • Select the Mailbox you want to move, Right click on it and then click on Move Database Path.

Open the Exchange Management Console

    • As you click on Move Database path, Move Database Path window will appear where you can enter the new path for the data and log files. After changing the path of EDB files, click on Move which will help you to reduce edb file size Exchange 2010.

Move Database path

    • As you click on Move, Microsoft Exchange 2010 window will appear informing you that database must be temporarily dismounted to perform the Move Database operation. You need to click on Yes to continue.

Microsoft Exchange window

    • The move operation will take some time depending on the size of the Mailbox. When the Move operation will complete, you can see the completion information. Now, click on finish to close the Wizard.

Click on Finish

Note: User can use manual method to move the EDB files but these methods are not the complete solution. They are not helpful if there is any corruption in the EDB file. We need a third-party tool in the case of corruption of the Exchange database file.

Use Best Third-Party Software

SysTools Exchange Server Recovery Software is one of the best tools that recover corrupted EDB files and repair Exchange mailbox from corruption with no data loss in a hassle freeway. It provides Quick and Advance scan option that recovers & fix Exchange database corruption and repair EDB file. Depending on the level of corrupted Exchange EDB file users can select the scan mode option to remove corruption from Exchange database file.

Download Now Purchase Now

This tool easily loads any size of .edb file and provides various export options which allow users to export the multiple Exchange database file and mailboxes in a hassle free-way.  It supports various Exchange mailboxes such as: users, archive, shared, legacy, disconnected and data items: mails, notes, journals, tasks, calendars, contacts.

The utility is capable to extract mailbox  from EDB file Exchange 2016, 2013 and export directly to the Live Exchange Server mailboxes, Office 365 and multiple file formats (PST, EML, HTML, MSG, PDF, MBOX). This software support both private and pubic EDB & STM file and users can export these files simultaneously to the selected export option in a simplified manner.

Move Exchange 2013 Database using EAC

EAC (Exchange Admin Center ) is a web based/online management console for Exchange 2013. It supports to migrate mailbox easily & other services like setting up policies for OWA, an organization of public folders etc. Migration will help users to reduce edb file size Exchange 2013 for the mailboxes that are too large in size.For this you need to perform following steps:

  • Open Exchange Admin Center

Fix EDB is too big error via EAC

  • Choose Mailbox Tab & Select the desired mailbox
  • Right Click & Select Export to choose a recipient for sending notification for task completion.
  • Click Next >> Finish

Conclusion

We will recommend you to use advanced software that easily exports any size of Exchange database file and recover your EDB files from corruption. This tool is a complete solution that has great efficiency to resolve database corruption Exchange 2010/2013/2016 with full data security. If your Exchange EDB file too big, you can load and convert your Exchange database files to PST and also recover your data that has been lost due to corruption. You can download EDB to PST converter tool free version and after verifying the software you can purchase the full version of the software from its official website.

Frequently Asked Questions

Why even after file deletion my EDB file is too big to function?
This is due to the underlying B+Tree architecture the edb file. So, it performs a permanent capture of space on your hard disk. Meaning that even if you delete the file content EDB keeps its default size.

Is there any way to limit EDB file expansion before it becomes unmanageable?
Yes, admins can alter the default grown quota of the user mailboxes. Doing this ensure that the EDB files in expand in smaller increments instead of large chunks. Therefore avoiding any sudden surges in file size.

When should i start worrying that my EDB files have become too big?
That depends entirely on your specific use case. As organizations operate in different environments, so there is no single definition of a big EDB file. Moreover, hardware efficiency can play a huge role too. So when administrators notice a drop in response time from their server, it is a strong indication that the EDB file is nearing its limit.

Can I prevent EDB Files from becoming too big?
Yes as the admin it is your responsibility to perform regular maintenance of the server. Moreover, it doesn’t hurt to implement the necessary retention policies. But above all continuous monitoring monitor is the best way to prevent EDB files from becoming too large.

  author

By Chirag Arora

Chirag Arora is a seasoned professional who wears multiple hats in the digital realm. As a Digital Marketing Manager, he orchestrates successful online campaigns, optimizing brand visibility and engagement. Additionally, Chirag brings meticulous attention to detail to his role as a Content Proofreader, ensuring that every piece of content shines with accuracy and clarity.