Methods to Remove White Spaces in the Exchange database
Updated On - April 22, 2026
White spaces refer to the unused storage that is created by the deletion of old records in the Exchange database. When the user deletes the information from mailboxes, it doesn’t create free space for new data. Consider if the user removes 10 GB of data from the 50 GB Exchange database. However, after deleting the data, the user notices that the size remains the same as before.
However, the Exchange database still has 10 GB of data to store new data. Generally, ‘The Available new mailbox size’ is known as white space. This white space is not visible to the user, but can be fixed manually by removing the free space to be reused to store the new data. Now, we’ll know the steps to detect the white space.
- Reusable White Space that is automatically reused by Exchange & no immediate action is required.
- Fragmented White Space that is scattered, unused blocks within the database & can impact performance.
- Logical space available for reuse & physical space that is actual disk size [unchanged].
How to Detect White Space in the Exchange database?
It is necessary to detect and remove the white space regularly to enhance the performance of the server. PowerShell commands provide three ways to inspect the white space of Exchange Server. Run the following commands:
- Use this command to check the white space in a mailbox database:
Get-MailboxDatabase
-status | Select Name, ObjectServer, AvailableNewMailboxSpace 
- Use this command to check the white space in multiple mailboxes on a single server:
Get-MailboxDatabase -Status -Server
| Select-Object Server, Name, AvailableNewMailboxSpace 
- Use this command to check the white space in all mailboxes on all servers:
Get-MailboxDatabase -Status | Select-Object Server, Name, AvailableNewMailboxSpace
Top Methods to Remove White Spaces in the Exchange Server
Defragmentation is the only method to remove white space in Exchange database manually. This process can be performed in both online and offline modes, both of which are explained below in detail:
Method 1. Offline Defragmentation to Clear White Space in Exchange Database
Dismounting the Exchange database involves the process of offline defragmentation. This process helps to reduce the size of the database by replacing the older pages with new pages or deleting them altogether. While performing the Eseutil utility, ensure the availability of a large amount of free space for the prevention of data loss and corruption.
These are the steps of defragmentation of the Exchange database efficiently:
- Ensure the amount of white space is available in the Exchange database by following the command below in the Exchange Management Shell.
Get-MailboxDatabase < Database name > -Status | Format-List Name, DatabaseSize, AvailableNewMailboxSpace
- Run this command to dismount your Exchange database after checking the space in the database
Dismount-Database < database name >
- To defragment the database, follow this command:
Eseutil /d < database_name >
- Now, run this command to mount the defragmented, dismounted database
Mount-Database < database name >
- Finally, check the availability of white space in your database after defragmentation. In this manner, it can help users to reclaim white space in Exchange database.
Get-MailboxDatabase < Database name > -Status | Format-List Name, DatabaseSize, AvailableNewMailboxSpace
Method 2. Online defragmentation [Automatic Process]
The online defragmentation process is performed every night automatically on the Exchange server. It doesn’t reduce the database size but removes the deleted mailboxes and expired messages and maintains the optimal performance of the database.
It is well known that unused whitespace can cause storage, backup, and performance issues on the Exchange database and may corrupt and crash the database. Fragmentation consumes more time, restricts access during the process, and makes it complicated.
- Mailbox migration to new database:
In this, create a new mailbox database, move mailboxes to the new one, & delete the old database. - Databases rebuild strategy:
It is used in extreme cases where you need to export mailboxes, create a new database & then import the data back.
Fix Any Exchange Issue With the All-in-One Smart Option
There is a risk of data loss and database corruption in the defragmentation process. To overcome these risks, try the advanced and automatic Recoveryfix for Exchange Server Recovery software that handles the difficulties of recovering data and makes the process easier. This tool is also an effective method to resolve exchange-related issues like mounting exchange server error, dirty shutdown, recovering mailboxes, migrating to other platforms, etc.
Best Practices to Manage Exchange Database Size
Check out the best practices for easy management of the Exchange Database size:
- Regularly monitor database growth.
- Avoid unnecessary data accumulation.
- Try to schedule the maintenance tasks.
- Archive old mailboxes & use the mailbox quotas.
Guidelines to Avoid Excess White Space
Follow the provided guidelines to reduce the chances of excessive white spaces:
- Implement retention policies.
- Use journaling & archiving solutions.
- Avoid frequent large deletions without planning.
- Check storage usage regularly for extra prevention.
Remove White Spaces in the Exchange Database: Last Words
In the above sections, we have seen the different methods to clear white space in Exchange database. If you’re still facing the issue, then there is corruption in the EDB file. For fast, secure, and easy recovery of your Exchange database, use the suggested professional software. It scans and recovers mailboxes with all the data from offline and dismounted files affected by white space issues and saves them to your preferred destination with 100% data integrity.
FAQs
Q- Does white space slow down Exchange Server performance?
A- Yes. Excessive fragmentation within white space can impact database performance & backup processes.
Q- Can I reclaim white space in Exchange database without downtime?
A- Full reclamation requires offline methods, but mailbox migration offers minimal downtime alternatives.
Q- Is offline defragmentation necessary for all databases?
A- It should only be performed when there is significant unused space & storage pressure.
Q- Can white space automatically reduce over time?
A- Exchange only reuses white space internally. It does not shrink the database file automatically.
