Solved

exchange migration 2010 to 2013 maibox move failed

Posted on 2016-08-21
2
44 Views
Last Modified: 2016-08-23
I have just performed an Exchange 2010 to 2013 migration. I have to move 31 mailboxes to the new server, 29 boxes moved over successfully. Two mailboxes failed. When I tried to move them over individually the migration status window states completed but the mailboxes don't move
0
Comment
Question by:SchoolNet
[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
2 Comments
 
LVL 25

Accepted Solution

by:
-MAS earned 500 total points
ID: 41764491
Hi,
Please post the error  if you can.
If your error indicates about source mailbox is larger than the target database quota.
Please check your mailbox size and the remote database quota.
If the target database quota is less than the mailbox size your migration will fail.

Please adjust the database quota on the target database according to the source mailbox and try the migration again.


Thanks
MAS
0
 
LVL 12

Expert Comment

by:Ajit (Kevin k)
ID: 41766795
If it's only 2 mailboxes and if they aren't that big then might be best just to export to pst, remove the mailbox from Exchange server 2010 and create a new one on Exchange server 2013 and import.  

Powershell cmdlets to export Exchange mailbox to PST, get detailed here.

Powershell cmdlets to import PST file to Exchange 2013 Mailbox, get detailed here.

As a workaround, check If there were any old move requests on the Exchange server, If so Remove the move requests.

Run these Exchange Management Shell commands:

Get-moverequest -identity 'mailbox name'   

Open in new window


This will show a failed status for this mailbox.

Remove-moverequest -identity 'mailbox name'  

Open in new window


To clears out the move migration for this mailbox

New-moverequest -identity 'mailbox name' -baditemlimit '100' -targetdatabase 'Mailbox Database name' 

Open in new window


Runs the move via command line instead of via EAC

I hope the deleting migration batch fixed the issue.
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

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

MS Outlook is a world-class email client application that is mainly used for e-communication globally.  In this article, we will discuss the basic idea about MS Outlook, its advanced features, and types of MS Outlook File formats.
As cyber crime continues to grow in both numbers and sophistication, a troubling trend of optimization has emerged over the last year.
This tutorial will walk an individual through the process of installing of Data Protection Manager on a server running Windows Server 2012 R2, including the prerequisites. Microsoft .Net 3.5 is required. To install this feature, go to Server Manager…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…

738 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