Solved

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

Posted on 2015-02-10
6
89 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
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
NAS Cloud Backup Strategies

This article explains backup scenarios when using network storage. We review the so-called “3-2-1 strategy” and summarize the methods you can use to send NAS data to the cloud

 
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

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

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

Suggested Solutions

Exchange server is not supported in any cloud-hosted platform (other than Azure with Azure Premium Storage).
Not sure what the best email signature size is? Are you worried about email signature image size? Follow this best practice guide.
In this video we show how to create a User Mailbox 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 Recipients >> Mailb…
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…

772 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