We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.


Starting May 1st, 2018, we will no longer offer the ArchiveOne family of products. This includes all editions of ArchiveOne, ArchiveOne for Files, Max Compression, and Access Security Manager. If you currently hold a maintenance and support contract, you will continue to receive our award-winning support until your contract expires, or until May 1st, 2019, whichever occurs first. The license for ArchiveOne is perpetual; therefore the software may continue to be used independently without any updates or support indefinitely.

How to Accurately Measure Database Whitespace in Microsoft Exchange 2010

  • Last updated on

This article refers to the Barracuda ArchiveOne Enterprise or Express, and Microsoft Exchange Server 2010.

In Exchange 2010, Microsoft found that database space was not being reclaimed in several scenarios where items are hard deleted once the item is purged from the store. This includes archiving scenarios where items are bulk deleted based on date, and stubbing scenarios where email attachments are deleted.

Exchange 2010 attempts to clean up the row for a deleted item within a couple of minutes of the item being hard deleted. However, cleanup fails if another process has open references to the item. Outstanding references on deleted messages are particularly common in journaling mailboxes, or when third-party archival software is used. The vast majority of customers who experienced this behavior have associated it with one of the aforementioned scenarios. However, technically any client can hold an open reference and prevent an item from being cleaned up.

For details on getting an accurate whitespace figure and Microsoft's recommendations for reclaiming whitespace, refer to the Microsoft Exchange Team Blog article Database Maintenance in Exchange 2010.

After you have followed Microsoft's recommendations to resolve this issue, verify that whitespace is reclaimed as expected.

Last updated on