Resolve Exchange Database Compression

Person Name

Data Recovery Tackled the Issue of Compressed Exchange Server that Corrupted Sensitive Data


The sensitive data from an operational unit of reputed aviation industry lost when the administrator tried to log on the exchange server of the concerned unit. The problem got worse when it was found that the data got corrupted due to compression issues in exchange server.


The client recently upgraded a pre-SP3 version of Exchange 2000 Server to Exchange 2000 Server SP3 and it was found that an attempt to open the compressed file failed. The file opening operation failed with error - 4005 (0xfffff05b). This failed attempt cleared that corruption resulted in Exchange 2000 information store that has been compressed by using NTFS compression. When the administrator tried to sort out such issue, the entire Exchange Server got failed with clueless story.


The loss of sensitive data made the client worried. The client approached the Data Recovery company to brief about the incident that occurred in their operational unit. Data Recovery Company was deeply concerned with the problem as they are going to deal with high level sensitive data. The company concluded that due to compression of Exchange Server the entire data in the server was lost.


After understanding the complete situation, Data Recovery officials inspected the Exchange server and found that the server got compressed due to which the entire classified data got collapsed. In general, when database files grow to larger than 128 MB, the database does not mount and the error messages are generated in the Application Log. The Exchange 2000 Server Service Pack 3 and Exchange Server 2003 prevent compressed databases larger than 128 MB from mounting.

The officials were told about the steps that were already taken by client’s administrator to get back the Exchange Server data. From the client’s end all the exchange databases were dismounted and the root folder of Exchange databases and log files were decompressed followed by defragmentation of the databases and remounting them.

The strategy tried by client group was found to be effective theoretically; however, it became unresponsive when it was applied. When officials ran for Exchange Server tool, it was found to be effective in restoring the entire Exchange Sever data. The software restored emails, attachments, contacts, calendars, tasks, deleted items, etc. from offline EDB files. The software restored MS Exchange EDB files and converted it to equivalent PST file format. The tool extracted EDB mailboxes to importable PST files. What really impressed the client was the facility of the tool to extract mail components with their original format intact. In fact, client also admired the tool’s feature of easy and effective migration of multiple mailboxes from offline EDB files to Live exchange Server and Office 365 without any requirement of additional resources.


Data Recovery provided client the perfect solution for exchange server database recovery. This solution impeccably recovered the entire data of the corrupt exchange servers and saved the entire Exchange Mailboxes & Public Folders from EDB file to PST files. Data Recovery officials recommended client to use the licensed version of for Exchange Server to restore Pub.edb file to PST file format consisting entire shared data from Public folder during such unfortunate incident.