<div>
1) Time to start thinking about a transition to Exchange 2010 at a minimum as Windows 2003 has been out of support for over a year, Exchange 2003 has been out of support for over two years now, and Exchange 2007 will no longer be supported after April 2017.<br />
<br />
2) Do you know how much white space is in the database? &nbsp;Review the application log 1221 event IDs to see if it's even worth it to defrag the database.<br />
<br />
3) Make sure you have at least enough free disk space as the existing size of the database as the defrag process creates a copy of the database. Here are some references to defrag...<br />
&nbsp; &nbsp; &nbsp;- <a href="https://support.microsoft.com/en-us/kb/328804" rel="ugc nofollow">https://support.microsoft.com/en-us/kb/328804</a><br />
&nbsp; &nbsp; &nbsp;- <a href="https://support.microsoft.com/en-us/kb/192185" rel="ugc nofollow">https://support.microsoft.com/en-us/kb/192185</a><br />
&nbsp; &nbsp; &nbsp;- <a href="https://technet.microsoft.com/en-us/library/aa995748(v=exchg.65).aspx" rel="ugc">https://technet.microsoft.com/en-us/library/aa995748(v=exchg.65).aspx</a>
</div>


<div>
Yes, the transition to Exchange 2016 is in the pipeline. But it will take another three months to complete.<br />
<br />
Currently Exchange database is on SAN and LUN is mapped to Exchange server. I can create one more LUN with similar space. Hope then we can defrag the database.<br />
<br />
<br />
&quot;The database &quot;First Storage Group\Mailbox Store &nbsp;has 35 megabytes of free space after online defragmentation has terminated.&quot; is the last message for event 1221.<br />
<br />
Please advice
</div>


<div>
If it has only 35 megs of free space it is useless to Defrag <br />
<br />
Moreover defrag is not really necessary, just create a new blank database / storage group and move all mailbox to it. You will have a new db defragged and no downtime to speak off
</div>


<div>
Hello,<br />
<br />
this is the Best article for following Eseutil tool in exchange 2003.<br />
<br />
<a href="http://www.petenetlive.com/KB/Article/0000814" rel="ugc">http://www.petenetlive.com/KB/Article/0000814</a><br />
<br />
recommended several users for the same with successfull feedback<br />
<br />
Thanks,<br />
Andy
</div>


<div>
With 35 MB free in the database, it is not worth running a defrag against it.<br />
<br />
Why do you feel you need to defrag the database? &nbsp;What is the reasoning behind asking the question on EE?<br />
<br />
What version of Exchange 2003 are you running? &nbsp;Based on the size of the existing database, you have Exchange 2003 Enterprise Edition.<br />
<br />
My advice to you is if you are running out of disk space where the current database resides is to take Akhater's suggestion. &nbsp;And because you seem to have enough space availabile on your SAN to present to the Exchange 2003 server, I also recommend creating a new database, moving the mailboxes to it, and then removing the old database. &nbsp;Alternatively, maybe you should reconsider your Exchange transition timeline by moving the date closer (of course depending on your need and ability to do so).<br />
<br />
When you finally make the decision to move to Exchange 2010 and then ultimately to Exchange 2016, keep in mind that database sizes can grow up to 50% when moving from Exchange 2003 to Exchange 2010 and potentially another 20% when moving to Exchange 2016.
</div>


<div>
Hi,<br />
<br />
I guess the below link is usefull to you, but if there is only 35 MB free space no need to run the defragmentation.<br />
<br />
<a href="https://www.petri.com/defragment_exchange_2000_2003_server_databases" rel="ugc">https://www.petri.com/defragment_exchange_2000_2003_server_databases</a><br />
<br />
regards,
</div>


<div>
created SAN space as additional 300GB and now how would &nbsp;I change the database location<br />
<br />
logged in exchange as domain administrator
</div>


<div>
This link should provide you guidance to move the database and logs to another drive...<br />
<br />
<a href="https://www.petri.com/move_exchange_stores_to_a_different_disk" rel="ugc">https://www.petri.com/move_exchange_stores_to_a_different_disk</a>
</div>


<div>
Thanks Todd for the post.<br />
<br />
I will be carrying out this activity tomorrow.<br />
<br />
But before that I would like to know about the following :<br />
<br />
In the link while I was going through it is written that &quot;You must grant the following default permissions to the new Mdbdata directory that contains the log files and database files:<br />
<br />
Administrators: Full Control Authenticated Users: Read and Execute, List Folder Contents, Read Creator Owner: None Server Operators: Modify, Read and Execute, List Folder Contents, Read, Write System: Full Control &quot;<br />
<br />
I have logged in as domain administrator so do I need to give this permissions exclusively (like in my case teh location is F:. In case I create a directory called &quot;MDBDATA&quot;, this directory will have all the permissions, right?<br />
<br />
Also approximately how much time will it take to change the location (the information store is 107gb)<br />
<br />
Is the &quot;Point Registry to new database path&quot; is mandatory
</div>


<div>
Hi Todd,<br />
<br />
Million thans, I tried to move the log files whihc gave 47GB free and database not moved as I thought w will move the database later.<br />
<br />
However we will speed up for the transition from Exchange 2003 to Exchange 2016<br />
<br />
Your post has really helped, thanks again.
</div>


<div>
<div class="content wysiwyg-content">
My Exchange server Information store database size is now 103GB and I need to defragment the same using eseutil<br />
<br />
Please suggest the steps of eseutil so that size can be minimized.
</div>
</div>


My Exchange server Information store database size is now 103GB and I need to defragment the same using eseutil

Please suggest the steps of eseutil so that size can be minimized.

Exchange server (2003) Information Store

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.