Each mailbox store and public folder store of Microsoft Exchange Server is associated with two key files: EDB (Exchange database file) and STM (Streaming file).
Each mailbox store and public folder store of Microsoft Exchange Server is associated with two key files: EDB (Exchange database file) and STM (Streaming file). An EDB file consists tables, folders, and indexes for all the MAPI messages, messaging data, and message attachments, while STM is the file that comprises Internet content. One of the common problems that an Exchange Server administrator might encounter is unexpected growth in the size of these files. For no apparent reason, the user may find an incredible increase in its database files. If not taken care of, such problems can lead to database corruption and finally, necessitate the need of exchange recovery solutions.
Further is a realistic problem that shows similar type of probable issue. Suppose an Exchange Server EDB file is X GB and the STM file (of same mailbox store) is Y GB in size. After some time, the administrator observes a sudden and large increase in their size, for say the EDB grows to 4X GB and STM to 2Y GB.
Cause
Below is the list of possible causes that can result Exchange Server database files to grow in an unexpected manner:
The administrator adds certain number of new mailboxes and user accounts to the existing mailbox store that adds to files sizes.
Exchange computer is infected from a virus or worm that is sending e-mails without users intervention.
Users of Exchange server have sent or received a large amount of data
A relay or probably, SMTP traffic relay has been used by mail server
Exchange computer is affected from hardware-related issues
An antivirus, backup, or any third-party utility is being used that is causing harm to database integrity
Solution
Based on the existing issue, you can solve the depicted problem by the following measures:
Disable the undesired relay operations
Uninstall and remove the doubted third-party and backup software from Exchange computer
Disable antivirus scanning for Exchange specific folders and files
Diagnose and troubleshoot hardware-related concerns. Hardware causes often damage database stability
Defrag and verify the database integrity. If found corrupted, restore from backup or repair using Eseutil commands
The safest and effective solution for edb recovery is to use a third-party utility. An Exchange Recovery tool can scan the corrupted Exchange database safely and repair it without causing any harm.
Stellar Phoenix Mailbox Exchange Recovery is a professional utility that repairs corrupted Exchange database and restores mailboxes in separate *.pst files. Supporting MS Exchange Server 2007, 2003, 2000, and 5.5, this edb recovery tool also recovers deleted mailboxes and STM data.
