Local move request failed in Exchange 2010 SP1

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??

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.

If I follow your instructions. Will the new move start where the first attempt let off, or will it start from 0 again??

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.

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?

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.

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?

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.

Just putting the screenshot of the command on article.