<div>
The space left behind is &quot;white space&quot;. &nbsp;The database itself won't reduce in size unless you run an eseutil /d to defrag the database.<br />
<br />
<a href="http://blogs.technet.com/b/exchange/archive/2004/06/18/159413.aspx" rel="ugc">http://blogs.technet.com/b/exchange/archive/2004/06/18/159413.aspx</a><br />
<br />
<a href="http://www.computerperformance.co.uk/exchange2010/exchange_2010_eseutil.htm" rel="ugc">http://www.computerperformance.co.uk/exchange2010/exchange_2010_eseutil.htm</a><br />
<br />
The things to keep in mind are that the database must be offline when you do this, the utility will process about 5-10 gig an hour, and you will need at lease 2.5 times free disk space when performing this operation for the temp database, and the final defragmented one.
</div>


The space left behind is "white space".  The database itself won't reduce in size unless you run an eseutil /d to defrag the database.

http://blogs.technet.com/b/exchange/archive/2004/06/18/159413.aspx [http://blogs.technet.com/b/exchange/archive/2004/06/18/159413.aspx]

http://www.computerperformance.co.uk/exchange2010/exchange_2010_eseutil.htm [http://www.computerperformance.co.uk/exchange2010/exchange_2010_eseutil.htm]

The things to keep in mind are that the database must be offline when you do this, the utility will process about 5-10 gig an hour, and you will need at lease 2.5 times free disk space when performing this operation for the temp database, and the final defragmented one.

<div>
create a new mailbox database and move the users in that database there, then delete the old database<br />
no need to disconnect users by dismounting the database for a defrag
</div>


create a new mailbox database and move the users in that database there, then delete the old database
no need to disconnect users by dismounting the database for a defrag

<div>
Good point Seth. &nbsp;Jose, that is the best way to go with less impact on your users.
</div>


Good point Seth.  Jose, that is the best way to go with less impact on your users.

<div>
Hi<br />
I have try the defrag before activing exchange archive and no result<br />
But now the defrag work &nbsp;well.<br />
I have dismount the necessary DB and revovered 250GB <br />
<br />
Thank you
</div>


Hi
I have try the defrag before activing exchange archive and no result
But now the defrag work  well.
I have dismount the necessary DB and revovered 250GB

Thank you

<div>
<div class="content wysiwyg-content">
Hi<br />
I activated the automatic archiving of Exchange 2010 SP3.<br />
The emails are moved to the archive database, but the mailbox EDB file is not reduced.<br />
Can you help me?<br />
<br />
Thank you
</div>
</div>


Hi
I activated the automatic archiving of Exchange 2010 SP3.
The emails are moved to the archive database, but the mailbox EDB file is not reduced.
Can you help me?

Thank you

EDB file and achive file exchange 2010

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Within Internet message handling services (MHS), a message transfer agent or mail transfer agent (MTA) or mail relay is software that transfers electronic mail messages from one computer to another using a client–server application architecture. A MTA implements both the client (sending) and server (receiving) portions of the Simple Mail Transfer Protocol (SMTP). The terms mail server, mail exchanger, and MX host may also refer to a computer performing the MTA function. The Domain Name System (DNS) associates a mail server to a domain with mail exchanger (MX) resource records containing the domain name of a host providing MTA services.