<div>
If you archive a big portion of a PST file, the PST file does not change size. You must use Compact to shrink it.<br />
<br />
So then likewise for Exchange you would use Eseutil to shrink the Exchange DB. I do not think a simple move will shrink the DB, but I am not certain on the latter point.
</div>


<div>
Actually I am not asking about PST file but about mailbox size that I am moving from one DB to another DB.<br />
Actual mailbox size is shown as 1 MB. When I start moving it shows 10GB.<br />
<br />
From what I read:<br />
<br />
<a href="http://exchangeserverpro.com/defrag-exchange-2010-mailbox-database/" rel="ugc">http://exchangeserverpro.com/defrag-exchange-2010-mailbox-database/</a><br />
<br />
Author is from Exchange team as I remember...<br />
<br />
&nbsp; &nbsp;<b> Your options to reclaim that space are to either:<br />
&nbsp; &nbsp; Create a new mailbox database and move all the mailboxes to that database<br />
&nbsp; &nbsp; Perform an offline defrag of the existing database to shrink the file</b><br />
<br />
So I did option 1 <br />
<br />
May be I need to run backup to clear logs?
</div>


<div>
I was only using PST as a parallel example. I don't know if clearing the logs will help. I think I would try the offline shrink.
</div>


<div>
So for those who will encounter the same problem:<br />
<br />
1. Backup did not help<br />
2. Running eseutil /d did not help.<br />
<br />
Exchange keeps archived to pst items for some time on server (like deleted items) an will not release a space.<br />
<br />
2 experts<br />
Please read:<br />
<a href="http://stevehardie.com/2012/05/exchange-2010-purge-dumpster/" rel="ugc">http://stevehardie.com/2012/05/exchange-2010-purge-dumpster/</a>
</div>


<div>
Did the article you posted help you?
</div>


<div>
If I recall correctly that was no different in Exchange 2007. And you should keep the dumpster in mind all the time when working with Exchange mailboxes in future. Sorry noone told you earlier.
</div>


<div>
What version of Exchange are you running? Also do you have the most upto date SPversion and RU/CU's installed?<br />
<br />
Mailboxes show the actual size. It is the databases they will not shrink. And i do not suggest using ESEUTIL to accomplish this. It is never a good idea to &quot;shrink&quot; anything when it comes to storage. <br />
<br />
Can you try this process with one mailbox and even though it says 10GB if you let it run how long does this take and does it represent 10GB on the new database after completion?<br />
<br />
I would start there.<br />
<br />
Will.
</div>


<div>
Hi Will<br />
<br />
The problem solved.<br />
Did you read my last post?
</div>


<div>
I accept my own solution as I spent a day and found the answer.<br />
That becomes a usual practice.....
</div>


<div>
<div class="content wysiwyg-content">
I archived all user's mailboxes to PST files.<br />
When I run Get-MailboxDatabase &quot;DB1&quot; | Get-MailboxStatistics | Sort totalitemsize -desc | ft displayname, totalitemsize, itemcount<br />
I can see that all mailboxes are about 1 MB size.<br />
<br />
I want to move all of them to new DB2 and them remove old DB1 instead of using &nbsp;eseutil to shrink DB1.<br />
When I started &quot;local move request&quot; it shows me that every mailbox is around 10GB size as it was before archiving.<br />
<br />
Suggestions?<br />
<br />
Thank you.
</div>
</div>


I archived all user's mailboxes to PST files.
When I run Get-MailboxDatabase "DB1" | Get-MailboxStatistics | Sort totalitemsize -desc | ft displayname, totalitemsize, itemcount
I can see that all mailboxes are about 1 MB size.

I want to move all of them to new DB2 and them remove old DB1 instead of using  eseutil to shrink DB1.
When I started "local move request" it shows me that every mailbox is around 10GB size as it was before archiving.

Suggestions?

Thank you.

Mailbox size after archiving to PST

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.