?
Solved

Exchange 2010 Archive Mailbox moved to another database but copy still remains in the source

Posted on 2012-12-24
3
Medium Priority
?
249 Views
Last Modified: 2013-11-22
Dear All,

I have moved some users archive mailboxes in Exchange 2010 to another database. They have actually copied themselves to the second database meaning no space has been freed on the drive hosting the original database. Also I do not have the "New Local Move Request" option available for these users too as they are still showing up with the green arrow in exchange management console.

Today, I set the Mailbox retention for the Archive database to 2 days as I thought it could be waiting for this time to expire before mailboxes are cleared from the database. I am not sure if this is the problem.

Thanks for any help on this matter.
0
Comment
Question by:ExchangeGroup
3 Comments
 
LVL 15

Accepted Solution

by:
Rajkumar-MCITP earned 2000 total points
ID: 38718100
Please refer the below

When mailboxes are moved from an Exchange 2010 SP1 database to any other database, Exchange doesn't fully delete the mailbox from the source database immediately upon completion of the move. Instead, the mailbox in the source mailbox database is switched to a soft-deleted state. Mailbox data can be accessed during a mailbox restore operation using the MailboxRestoreRequest cmdlet set. The soft-deleted mailboxes are retained in the source database until either the deleted mailbox retention period expires

http://technet.microsoft.com/en-us/library/dd298174(v=exchg.141).aspx
0
 
LVL 37

Expert Comment

by:Neil Russell
ID: 38718118
The following will remove he "Deleted" orriginal for you safely.

Get-MailboxStatistics -Database "YourDataBaseName" |  foreach {Remove-StoreMailbox -Database $_.database -Identity $_.mailboxguid -MailboxState SoftDeleted}
0
 

Author Comment

by:ExchangeGroup
ID: 38718124
Thanks very much Rajkumar for providing insight into the matter and Neilsr for the quick fix. I will try it and update you guys.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If something goes wrong with Exchange, your IT resources are in trouble.All Exchange server migration processes are not designed to be identical and though migrating email from on-premises Exchange mailbox to Cloud’s Office 365 is relatively simple…
Exchange administrators are always vigilant about Exchange crashes and disasters that are possible any time. It is quite essential to identify the symptoms of a possible Exchange issue and be prepared with a proper recovery plan. There are multiple…
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…
This video shows how to quickly and easily deploy an email signature for all users in Office 365 and prevent it from being added to replies and forwards. (the resulting signature is applied on the server level in Exchange Online) The email signat…
Suggested Courses

839 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question