Solved

Why this mailbox always failed in moving to another exchange server?

Posted on 2015-02-10
6
109 Views
Last Modified: 2015-02-16
This is setting up a new Exchange Server 2013 to join with one existing Exch2k13 server. The objective is, moving all of the mailboxes from old server to this new server. However, I tried from ECP, and the status shown completed, but none was synced and moved.

I tried with powershell command - new-moverequest, and found that some mailboxes can moved but only one, with total size of 16.0 gb. When I tried on this failed mailbox again, it shows inprogress, but 2 hours later, it shows failed.
Why the move failed? How should I troubleshoot and get the mailbox migrated successfully?

Appreciate help!
0
Comment
Question by:MichaelBalack
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
6 Comments
 
LVL 4

Expert Comment

by:Manoj Bojewar
ID: 40600491
Follow below steps to resolve this issue

1 ) First you suspend and remove failed migration.
2)Restart exchange mailbox replication services
3)Start the user mailbox migration again.
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 40600856
You need to look at the log file to see why it is failing.
A 16gb mailbox though is likely to have issues - corrupt items or items that are over the limit size set on the new server. Both of those can cause the migration to fail. The log should tell you why it has failed.

Simon.
0
 
LVL 31

Expert Comment

by:Gareth Gudger
ID: 40601607
Hey Michael,

Have you tried setting/raising the bad item limits to allow the migration process to drop corrupted items?

Also, another option would be to move the mailbox to another database on the old server. Once it is moved, then migrate it to 2013.
0
Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

 
LVL 1

Accepted Solution

by:
MichaelBalack earned 0 total points
ID: 40602396
Hi all,

This is how I did it:

   1. Using ADSI Edit, and browse to the properties of the affected user account that owns the mailbox
   2. Look for msExchMailboxMovestatus and msExchMailboxMoveFlag, and clear them
   3. rerun "new-moverequest mailbox1 -targetdatabase "DB2"

And mailbox successfully moved in 5 hours.
0
 
LVL 31

Expert Comment

by:Gareth Gudger
ID: 40602945
Glad you got it going. Please accept your own comment as the answer.
0
 
LVL 1

Author Closing Comment

by:MichaelBalack
ID: 40611853
By following the steps, i managed to get the mailbox moved without problem. Think most likely the values in the given msexch attributes stop the attempt to move the mailbox in the subsequent try.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

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

Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
In-place Upgrading Dirsync to Azure AD Connect
In this video we show how to create a Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …
This video discusses moving either the default database or any database to a new volume.

728 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