<div>
I moved all mailboxes out of &quot;New_Mailbox&quot;. I am performing windows server backup to remove temp log files in the exchange folders. After the backup is finished, I will going to defrag &quot;New_Mailbox&quot; (for my learning experience) to see how it works before deleting it.<br />
I will report back.
</div>


<div>
I have a situation where Outlook on network PCs fails to connect to Exchange server 2010 after mailbox move.<br />
However my phone can send/receive email and also I can access my email via Outlook Web Access to send/receive.<br />
Any idea?
</div>


<div>
I opened the Services.msc and noticed that the status of Microsoft Exchange RPC Client Access service was &quot;Empty&quot; instead of &quot;Started&quot;. I manually started it and now Outlook clients sees Exchange server.<br />
<br />
I am not sure what caused it, but one possibility is that Windows scheduled server backup at 5pm EST failed to run because a manual server backup that I started this morning (after remaining mailbox moves were finished) was still running past 5pm. &nbsp;Usually after mailbox move and windows server backup, my routine is to start SBS2011, but this time I did not do that because I was going to try &quot;Defrag&quot; on &quot;New_Mailbox&quot;.
</div>


<div>
I read and see &quot;Make sure you have free disk space equal to 110 percent of the end size of the database that you want to process (the end size being the current file size minus the size of the white space in the file)&quot;.<br />
However the partition that has Exchange database files have only 150GB free and the &quot;New_Mailbox&quot; size &nbsp;is over 230GB.<br />
What can I do?
</div>


<div>
If it is helpful ...<br />
New_Mailbox2.edb is 137GB and New_Mailbox3.edb is 85GB. 137GB+85GB=222GB<br />
New_Mailbox.edb (used to have all mailboxes that were moved to New_Mailbox2.edb and New_Mailbox3.edb) &nbsp;is 239GB. Therefore, most of 239GB should be &quot;white&quot; space.
</div>


<div>
I'm not clear on what you are saying, but the white space is space that was used but is now free again. it will not be added back to your overall storage quota but Exchange will reuse the space. So if you just moved all your mailboxes to a new DB and users haven't accessed their mailboxes and started deleting content then you will not have any whitespace on the new DB yet. So if you have 100GB mailboxdatabase with 1 mailbox that has 90GB of mail, then you will have 10GB free storage, but if that user deletes 80GB of mail content, you will now have 10GB free storage space and 80GB of whitespace. The only way to get the whitespace brought back in your storage is to run offline defrag, but if you keep it the way it is, the 80GB of whitespace will be reused by Exchange anyway, it just wont show as your free space.
</div>


<div>
@Timgreen<br />
'I'm not clear on what you are saying,&quot;--&gt; &nbsp;In the article @Jose Gabriel posted (ID: 42525688), I saw the following - &quot;Make sure you have free disk space equal to 110 percent of the end size of the database that you want to process (the end size being the current file size minus the size of the white space in the file&quot;.<br />
<br />
However my E drive where Exchange database files reside have only 150GB free and the &quot;New_Mailbox&quot; database file size &nbsp;is over 230GB.
</div>


<div>
I'm just talking about whitespace. white space is space that has been used but has been freed up again by the user deleting content or deleting mailboxes. the space will not be added to your storage again but exchange will use it for new content.
</div>


<div>
@Tim<br />
I am already aware of that.
</div>


<div>
what are you trying to do. I don't fully understand you statements about tour space.
</div>


<div>
<a href="https://filedb.experts-exchange.com/incoming/2018/04_w15/1296133/Free-Space.png" target="_blank" title="Free-Space.png (7 KB)"><img alt="Free-Space.png" class="file-block lazyload" style="max-width: 691px;" data-src="https://filedb.experts-exchange.com/incoming/2018/04_w15/1296133/Free-Space.png" /></a><a href="https://filedb.experts-exchange.com/incoming/2018/04_w15/1296134/Mailbox-size.png" target="_blank" title="size of &quot;new_mailbox.edb&quot; (3 KB)"><img alt="size of &quot;new_mailbox.edb&quot;" class="file-block lazyload" style="max-width: 691px;" data-src="https://filedb.experts-exchange.com/incoming/2018/04_w15/1296134/Mailbox-size.png" /></a>@Tim,<br />
&nbsp;<br />
&nbsp;Since I moved all mailboxes from &quot;New_Mailbox&quot; into &quot;New_Mailbox2&quot; &amp;&nbsp;&quot;New_Mailbox3&quot;, I no longer need to keep &quot;New_Mailbox&quot; database. However, before removing it from Exchange database, I wanted to try to defrag &quot;New_Mailbox&quot; for my own experience.<br />
However, as seen in screenshots, &quot;New_Mailbox&quot; database file size is 239GB and the E drive where exchange database resides has only 150GB free space. According to the article that @Jose Gabriel posted, if you want to defrag the exchange database, you are supposed to have free space on the hard drive that is greater than the exchange database size.<br />
<br />
Since I have 284GB free space in F drive, I think I will move &quot;New_Mailbox&quot; folder location to F drive from E Drive and then perform &quot;defrag&quot;.
</div>


Mailbox-size.png

Free-Space.png

<div>
I started moving &nbsp;&quot;New_Mailbox&quot; folder location to F drive from E Drive. Once finished, then I will begin &quot;defrag&quot;.<br />
I will report back.
</div>


<div>
<a href="https://filedb.experts-exchange.com/incoming/2018/04_w15/1296142/Mailbox-Folder-Location.PNG" target="_blank" title="Mailbox Folder Location (5 KB)"><img alt="Mailbox Folder Location" class="file-block lazyload" style="max-width: 417px;" data-src="https://filedb.experts-exchange.com/incoming/2018/04_w15/1296142/Mailbox-Folder-Location.PNG" /></a><a href="https://filedb.experts-exchange.com/incoming/2018/04_w15/1296143/Mailbox-in-E-Drive.png" target="_blank" title="Mailbox in E Drive (26 KB)"><img alt="Mailbox in E Drive" class="file-block lazyload" style="max-width: 800px;" data-src="https://filedb.experts-exchange.com/incoming/2018/04_w15/800_1296143/Mailbox-in-E-Drive.png" /></a><a href="https://filedb.experts-exchange.com/incoming/2018/04_w15/1296144/Mailbox-in-F-Drive-without-Log-files.png" target="_blank" title="Mailbox in F Drive without Log files (12 KB)"><img alt="Mailbox in F Drive without Log files" class="file-block lazyload" style="max-width: 698px;" data-src="https://filedb.experts-exchange.com/incoming/2018/04_w15/1296144/Mailbox-in-F-Drive-without-Log-files.png" /></a>I ran Mailbox Move in Exchange Management console, but it failed with an error and I forgot to save the screenshot.<br />
Anyway, as you see in the screenshots, I see &quot;New_Mailbox&quot; database and log files in the E drive which is original folder location and I also see &quot;New_Mailbox&quot; database file (without log files) in the F drive (new folder location).<br />
What do I do?
</div>


Mailbox-in-F-Drive-without-Log-files.png

Mailbox-Folder-Location.PNG

Mailbox-in-E-Drive.png

<div>
The 110% free disk space requirement is to create the TEMP database without whitespace. <br />
<br />
To get the defragemented Database size, <br />
&nbsp; &nbsp;&gt; &nbsp;run the cmdlet to find the availablenewmailboxspace. Subtract this from the actual DB file size. (Approximate size)<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Get-MailboxDatabase New_Mailbox -Status | fl AvailableNewMailboxSpace <br />
&nbsp; &nbsp;&gt; Event ID 1221 on Mailbox server (Approximate size)<br />
&nbsp; &nbsp;&gt; ESEUTIL /MS &nbsp;(Most precise value) <br />
<br />
Your defragmented database should be the size of the value that you got from above method(s). It usually be less than 2 GB, if no mailbox on the database.<br />
<br />
if your F drive has required free space, you can run the defrag (without retaining the original database)<br />
Alternate option, if it is Virtual server, add a disk from storage.<br />
&nbsp; If it is Physical server, then add a HDD, or USB drive to the server - make sure new drive is visible to OS.<br />
And then run Defrag.
</div>


<div>
Did you check the event logs to see if the original error (why the DB couldn't be moved) is available there? &nbsp;It would be a good idea to find out what that error was to diagnose further whether you can move it, or it needs to be repaired before moving, etc.<br />
<br />
Here's an article with steps you can also use to determine the status of the New_Mailbox database:<br />
<br />
<a href="https://blogs.technet.microsoft.com/heyscriptingguy/2012/12/14/use-powershell-to-check-the-status-of-exchange-databases/" rel="ugc">https://blogs.technet.microsoft.com/heyscriptingguy/2012/12/14/use-powershell-to-check-the-status-of-exchange-databases/</a><br />
<br />
If the database is in a Dirty Shutdown state, then you'll most likely have to repair it first before you can move it. That might be a problem again because of a lack of free disk space.
</div>


<div>
F drive where I wanted to move &quot;New_Mailbox&quot; had 284GB of free space and E:\exchagne\new_mailbox folder size is 231GB. So there should have been enough HD space to make the move. I just deleted New_Mailbox.edb from &nbsp;F:\exchagne\new_mailbox folder and I will re-try the move this evening again.<br />
When I look thru <br />
<br />
@Veerappan <br />
When I just ran &quot;Get-MailboxDatabase New_Mailbox -Status | fl AvailableNewMailboxSpace&quot;,<wbr /> it showed the followwing with no data.<br />
AvailableNewMailboxSpace : <br />
Should I have run it after mouting the database?<br />
<br />
<a href="https://filedb.experts-exchange.com/incoming/2018/04_w15/1296356/Exchange-Events.txt" target="_blank" class="file-inline" title="Exchange Events (4 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>Exchange-Events.txt</a><br />
@Hypercat<br />
&quot;Did you check the event logs&quot; --&gt; I will do a better job in writing down error message when I re-try mailbox database move this evening. But this is some of messages that I gathered from Event viewer aroudn the time that I was attemping mailbox database move last night.<br />
1. warnging/9042: Service MSExchangeMailboxAssistant<wbr />s. Managed Folder Mailbox Assistant for database New_Mailbox (8eb9e1ee-8532-4ff5-a64b-2<wbr />6fc5ed2932<wbr />9) is exiting a work cycle. No mailboxes were successfully processed. 4 mailboxes were skipped due to errors. There are 1 mailboxes in this database.<br />
<br />
Last night when I started moving mailbox database from E &nbsp;to F drive, entire server became un-responsive. I was concerned about it, so I tried to &nbsp;to bring up Task Manager, but that took a few minutes. All became normal after I got an error message about the job fail and then I restarted the server so that everything is refreshed. Is this typical that I experienced &quot;Freeze&quot; during mailbox database move? It was scary!
</div>


Exchange-Events.txt

<div>
It's hard to say what might have prompted the freeze, but since it was released when the job failed, my guess is that the freeze had to do with the server having a problem opening or reading the database. &nbsp;One thing I would recommend doing if you try to move it again would be to do it when the server resources would be more or less quiescent so you have the most resources possible available. &nbsp;<br />
<br />
Also, make sure you turn off any antivirus programs that might be scanning the database file as it's being moved! Normally antivirus programs will have automatic exemptions for database files (.edb, .mdb, etc.) but it depends on what type of antivirus you're using. Best practice is to disable all antivirus scanning temporarily just in case.
</div>


<div>
Considering what happened last night in terms of &quot;freeze&quot;, I have decide not to make another mailbox database move since it is a production server. Currently New_Mailbox is dismounted as a result of failed mailbox database move. Since all user mailboxes are in New_mailbox2.edb and New_mailbox3.edb, what I am going to do is to simply delete E:\Exchange\New_mailbox folder that has New_mailbox.edb, *.jrs, *.log files.<br />
I will keep them until the end of this week just in case. If I don't hear anything from users by Friday, I will erase it and forget about &quot;defrag&quot;.<br />
I just can't afford to mess with production server.<br />
I think I will restore this SBS2011 server (from Windows Server Backup) on a test server and try to move and defrag at a late time.<br />
<br />
Thanks for your help.
</div>


<div>
I think your decision is wise. &nbsp;I had not noticed that this was an SBS server and so that makes it even more wise. &nbsp;SBS servers usually don't have a lot of resources to spare in the first place, so you wouldn't want to try to do something like a mailbox move while users are trying to work.<br />
<br />
Good luck!
</div>


<div>
<a href="https://filedb.experts-exchange.com/incoming/2018/04_w15/1296512/Mailbox-Database-Removal-from-Exch-M.png" target="_blank" title="Mailbox Database Removal from Exch Mgmt Console (25 KB)"><img alt="Mailbox Database Removal from Exch Mgmt Console" class="file-block lazyload" style="max-width: 800px;" data-src="https://filedb.experts-exchange.com/incoming/2018/04_w15/800_1296512/Mailbox-Database-Removal-from-Exch-M.png" /></a>Thanks.<br />
Correction!<br />
When I said &quot;I am going to do is to simply delete E:\Exchange\New_mailbox folder&quot;, I should have said &quot;I will open Exchange Management Console, select &quot;New_Mailbox&quot; and click [Remove].
</div>


Mailbox Database Removal from Exch Mgmt Console

Mailbox-Database-Removal-from-Exch-M.png

<div>
Yes, you should have said that but I knew that Exchange would prevent you from deleting the mailbox database unless it had already been removed from the EMC. &nbsp;You do know, I assume, that removing it from the console doesn't delete it from storage. &nbsp;You need to go and manually delete the file and folder containing that database in order to remove it permanently.
</div>


<div>
Got it. Thank you for your help!
</div>


<div>
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.<br />
<br />
I have recommended this question be closed as follows:<br />
<br />
Split: <br />
-- 'Jose Gabriel Ortega Castro' (<a href="https:#a42525688" rel="ugc">https:#a42525688</a>)<br />
-- 'timgreen7077' (<a href="https:#a42525918" rel="ugc">https:#a42525918</a>)<br />
<br />
<br />
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.<br />
<br />
seth2740<br />
Experts-Exchange Cleanup Volunteer
</div>


<div>
<div class="content wysiwyg-content">
<a href="https://filedb.experts-exchange.com/incoming/2018/04_w14/1295884/ExchMgmt-Cosole.png" target="_blank" title="Exchange Mgmt Console (18 KB)"><img alt="Exchange Mgmt Console" class="file-block lazyload" style="max-width: 772px;" data-src="https://filedb.experts-exchange.com/incoming/2018/04_w14/1295884/ExchMgmt-Cosole.png" /></a><a href="https://filedb.experts-exchange.com/incoming/2018/04_w14/1295885/Mailbox-Database-Removal.png" target="_blank" title="Mailbox Database Removal (49 KB)"><img alt="Mailbox Database Removal" class="file-block lazyload" style="max-width: 800px;" data-src="https://filedb.experts-exchange.com/incoming/2018/04_w14/800_1295885/Mailbox-Database-Removal.png" /></a>Hi,<br />
<br />
&nbsp; I have SBS2011/Exchange 2010 with one 230GB exchange database called &quot;New_Mailbox&quot;.<br />
&nbsp;Sometime ago, the server got locked up and when I rebooted it, it had damaged Exchange database file. so I had to go thru exchange database repair process, but it did not recover 100% of data and I had to repair each mailbox separately. For those mailboxes that had so many errors, I had to create 2nd mailbox database called &quot;New_Mailbox2&quot; and moved them to the new database. The database &quot;New_Mailbox2&quot; size is 110GB. However,even &nbsp;after several mailbox were moved, &nbsp;&quot;New_Mailbox&quot; database size still remained the same as 230GB. As I understand it, if I want to reclaim HD space, I need to run &nbsp;&quot;Offline defrag&quot;. I have not done it because I learned that the better way of handling it (saving space on HD) is to create a new mailbox database &quot;New_Mailbox3&quot; , &nbsp;move the remaining mailboxes to it and delete &quot;New_Mailbox&quot;.<br />
&nbsp;(1) I wanted to know if &nbsp;that is a right approach.<br />
&nbsp;(2) Other than active &nbsp;user mailboxes, I see two additional mailboxes - &quot;Discovery Search Mailbox&quot; and &quot;Domain Administrator&quot; mailbox as seen in the screenshot. Is it safe to move these to &quot;New_Mailbox3&quot; too?<br />
&nbsp;(3) Once I confirm that every single mailbox listed in Recipient Configuration/Mailbox shows listed in &quot;Databases\New_Mailbox2&quot; or &quot;Databases\New_Mailbox3&quot;, can I go to Organization Configuration/Mailbox/Sele<wbr />ct &quot;New_Mailbox&quot;, dismount database and click &quot;Remove&quot; to delete it as seen in the screenshot?<br />
<br />
Thanks.
</div>
</div>


ExchMgmt-Cosole.png

Mailbox-Database-Removal.png

Hi,

  I have SBS2011/Exchange 2010 with one 230GB exchange database called "New_Mailbox".
 Sometime ago, the server got locked up and when I rebooted it, it had damaged Exchange database file. so I had to go thru exchange database repair process, but it did not recover 100% of data and I had to repair each mailbox separately. For those mailboxes that had so many errors, I had to create 2nd mailbox database called "New_Mailbox2" and moved them to the new database. The database "New_Mailbox2" size is 110GB. However,even  after several mailbox were moved,  "New_Mailbox" database size still remained the same as 230GB. As I understand it, if I want to reclaim HD space, I need to run  "Offline defrag". I have not done it because I learned that the better way of handling it (saving space on HD) is to create a new mailbox database "New_Mailbox3" ,  move the remaining mailboxes to it and delete "New_Mailbox".
 (1) I wanted to know if  that is a right approach.
 (2) Other than active  user mailboxes, I see two additional mailboxes - "Discovery Search Mailbox" and "Domain Administrator" mailbox as seen in the screenshot. Is it safe to move these to "New_Mailbox3" too?
 (3) Once I confirm that every single mailbox listed in Recipient Configuration/Mailbox shows listed in "Databases\New_Mailbox2" or "Databases\New_Mailbox3", can I go to Organization Configuration/Mailbox/Select "New_Mailbox", dismount database and click "Remove" to delete it as seen in the screenshot?

Thanks.

Removing Exchange Mailbox Datbase

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

Databases are organized collections of data, most commonly accessed through management systems including schemas, tables, queries and processes that allow users to enter and manipulate the information or utilize it in other fashions, such as with web applications or for reporting purposes.