Solved

Local move request failed in Exchange 2010 SP1

Posted on 2011-09-14
11
1,679 Views
Last Modified: 2012-05-12
I am migrating from Exchange 2003 to 2010 SP1. All but 5 mailboxes were successfully moved.
The remaining 5 all have the identical error message:


move-failed.txt
0
Comment
Question by:clesin
  • 6
  • 5
11 Comments
 
LVL 15

Accepted Solution

by:
It breaks therefore I am earned 500 total points
ID: 36536182
This happened because the move-request encountered corrupt items.

The following article explains this in more detail and tells you how to override the corrupt item count limitation in EMC

http://www.petri.co.il/baditemlimit-override-exchange-2010.htm

This is very common.
0
 

Author Comment

by:clesin
ID: 36536279
Thank you. but at this point, where it already copied over 10GB of data, I really don't want to suspend the move at this point.

Is there any was to 'resume' the move from Shell with the 'bad items' switch??
0
 
LVL 15

Expert Comment

by:It breaks therefore I am
ID: 36536469
If you go to EMC and drill down to recipient config and Move Request the status will be on failed, that means the request has already failed so if you remove it you will be able to create a new move request by going to to mailbox and this time select a corrupt item count. Nothing will be lost, except corrupt items which the user will probably not notice. I have never seen a migration where I have not encountered corrupt items on one or two mailboxes, and I have done a lot. I have never done a corrupt item move where a user has noticed anything. If you want peace of mind, make sure you have a back up of the mailboxes first.
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

 

Author Comment

by:clesin
ID: 36536521
If I follow your instructions. Will the new move start where the first attempt let off, or will it start from 0 again??
0
 
LVL 15

Expert Comment

by:It breaks therefore I am
ID: 36536678
You have told Shell to skip the mailbox if it encounters a corrupt item, in this case it has so the mailbox move was skipped. So it will start again with a new move request.
0
 

Author Comment

by:clesin
ID: 36536732
No I did not. At the initial move request, I ticked where it says 'Skip the corrupted messages' and left the number at 0.

Now if I look under 'Move Request', it says the mailbox move has 'failed' and that 26% (Mailbox size is 10GB) has been moved.

My question: is there 'any' way to resume from the 26% and skip corrupted items??

It doesn't matter to me if we need EMC or EMS to do it.

It its doable, what would the process be?
0
 
LVL 15

Expert Comment

by:It breaks therefore I am
ID: 36537424
I hope I am not misunderstanding you. If you set the Corrupt item count to Zero it will fail the move if it encounters a single corrupt item. As far as I am aware its a new request now which will start a new move, not where you left off and I can not see any way to do this differently. I have checked this on a few resources and can not see otherwise. Of course someone else might tell us a way of doing this but I do not think that's going to be the case.
0
 

Author Comment

by:clesin
ID: 36538924
I tried running the command from EMS and allowed 110 corrupted items. At 27% of the move it alrady has reached that limit, therefore canceling the move again.

Question: How can I repair this corruption on the Exchange 2003 box so that we can move ahead with the migration?

0
 
LVL 15

Expert Comment

by:It breaks therefore I am
ID: 36541999
I suggest you move all the mailboxes that you can until a point where the Exchange 2003 Database only has mailboxes with a high corrupt item value. At this stage you can then run isinteg with the -fix and alltests switches.

http://support.microsoft.com/kb/301460

You will need to run the same test a couple of times and remember that unlike Exchange 2010 any mailbox maintenance tasks like Isinteg or ESEUtil require that the database is unmounted so its going to result in downtime for these users. You might find however that you have to Exmerge or use Outlook to export these mailboxes.
0
 

Assisted Solution

by:clesin
clesin earned 0 total points
ID: 36543633
Thank you 'johan_strange'. I did the -Bad Item Limit 200 and it worked.

See image attached. move requeset
0
 

Author Closing Comment

by:clesin
ID: 36565451
Just putting the screenshot of the command on article.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. 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

Exchange server is not supported in any cloud-hosted platform (other than Azure with Azure Premium Storage).
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.
In this video we show how to create a Contact 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 >> Contact ta…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

821 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