Solved

Exchange 2013 mailbox migration problem

Posted on 2013-12-22
7
4,765 Views
Last Modified: 2013-12-25
Hello--

I'm using EMS to migrate 300 mailboxes from our Exchange 2010 server to Exchange 2013 (CU3).  All but 9 of the mailboxes show "completed."  The others show either "stalledduetowritecpu" or "stalledduetowritethrottle"  If I look at the mailboxes in the console, it shows that they're on the correct database.

How do I verify whether the move request has completed or not?  I don't want to suspend or cancel it and risk corrupting anything.
0
Comment
Question by:bsternfield
  • 4
  • 3
7 Comments
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39734731
Suspend/Cancel does not corrupt anything.
Move mailbox doesn't actually move the content, it copies it, then verifies it, before deleting it on the source. Therefore it is completely safe.
As such the first thing I would do is suspend them all. Once the suspension is complete start them off again one at a time.

Simon.
0
 

Author Comment

by:bsternfield
ID: 39734899
How do I suspend them?  The command I used to initiate the migration was:

Get-Mailbox -Database <2010 DB> | New-MoveRequest -TargetDatabase <2013 DB> -BatchName "<name>"

I tried suspend-moverequest -identity "user@domain" (for the users with stalled status) and also

get-moverequest -status stalledduetowritecpu | suspend-moverequest

and they both error out.
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39734961
When you say they error out, what is the error?

When you run get-moverequest does it show the requests?

Simon.
0
U.S. Department of Agriculture and Acronis Access

With the new era of mobile computing, smartphones and tablets, wireless communications and cloud services, the USDA sought to take advantage of a mobilized workforce and the blurring lines between personal and corporate computing resources.

 

Author Comment

by:bsternfield
ID: 39734984
Error is as follows:

[PS] C:\>get-moverequest -movestatus stalledduetowritecpu | suspend-moverequest
Cannot process argument transformation on parameter 'MoveStatus'. Cannot convert value "stalledduetowritecpu" to type
"Microsoft.Exchange.Data.Directory.Recipient.RequestStatus". Error: "Unable to match the identifier name
stalledduetowritecpu to a valid enumerator name.  Specify one of the following enumerator names and try again: None,
Queued, InProgress, AutoSuspended, CompletionInProgress, Synced, Completed, CompletedWithWarning, Suspended, Failed"
    + CategoryInfo          : InvalidData: (:) [Get-MoveRequest], ParameterBindin...mationException
    + FullyQualifiedErrorId : ParameterArgumentTransformationError,Get-MoveRequest
    + PSComputerName        : argon.xxx.org

And for one of the stalled users, I get the following, which is confusing because that user still shows as stalled when I run the get-moverequeststatistics command

[PS] C:\>suspend-moverequest -identity "xxx@xxx.org"
You can't modify move request 'xxx'  because it has already completed.
    + CategoryInfo          : InvalidArgument: (xxx@xxx.org:MoveRequestIdParameter) [Suspend-MoveRequest], Recipi
   entTaskException
    + FullyQualifiedErrorId : [Server=ARGON,RequestId=1bef0f87-8138-4231-8b1c-c366b383ecdb,TimeStamp=12/22/2013 7:54:0
   2 PM] 26F30416,Microsoft.Exchange.Management.RecipientTasks.SuspendMoveRequest
    + PSComputerName        : argon.xxx.org
0
 

Author Comment

by:bsternfield
ID: 39735115
I just checked the move request status with:

get-moverequest -batchname <name>  and the problem mailboxes show up there as completed, while the output of:

get-moverequeststatistics -moverequestqueue "<name>

shows those mailboxes as stalled.

EMC shows all mailboxes in the correct database.  I still need to migrate mailboxes out of our archive database on the old server, and this fails on each one with the following error:

xxxx@xxx.org,"Mailbox 'xxxx, xxx' has a completed move request associated with it. Before you create a new move request for the mailbox, run the Remove-MoveRequest cmdlet to clear the completed move request.

Running the remove-moverequest cmdlet does clear the mailbox and lets me migrate that user's archive mailbox.  So it appears that the original migration never completed and cleared the move requests, even though all of the mailboxes were migrated?  Is there some way to clear all of the move requests without having to do it for each mailbox?
0
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 500 total points
ID: 39735587
I haven't got an Exchange 2013 server in front of me at the moment, but this command (or a variant of it) should work:

Get-MoveRequest -MoveStatus Completed | Remove-MoveRequest

Simon.
0
 

Author Closing Comment

by:bsternfield
ID: 39739328
Thanks, I was able to clear the move requests with that command.
0

Featured Post

Are your end users making ugly email signatures?

Have you left it up to your end users to create their own email signatures? Are they forgetting to add the company logo or using garish font colors? Take control and ensure all users have the same email signature.

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.
Find out what you should include to make the best professional email signature for your organization.
In this video we show how to create an Address List 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 Organization >> Ad…
This video discusses moving either the default database or any database to a new volume.

919 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

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now