Solved

Exchange 2007 mailbox migration to Exchange 2013 fails

Posted on 2015-01-07
14
181 Views
Last Modified: 2015-01-08
Hi,
I created a migration batch in the ECP for a single 2007 exchange mailbox.  After it ran, it said it failed due to the fact that there were a few (2 exactly) corrupted email records.  Apparently, I should have specified a maximum number of corrupt records so that it would be able to complete the migration .  How do I correct this so that I can tell the ECP to 'Complete this migration batch'?  It doesn't seem to want to let me let changes beforehand.  Thanks very much.

Pete
0
Comment
Question by:sndmnsix
  • 7
  • 7
14 Comments
 
LVL 8

Expert Comment

by:Leo
ID: 40537062
0
 
LVL 8

Expert Comment

by:Leo
ID: 40537065
0
 

Author Comment

by:sndmnsix
ID: 40537068
Ok.  So I'll run the integrity check and then try to rerun that batch and see if it clears up.  On a side note, Is there anything wrong with creating a new batch to run the same mailbox migration ?
0
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.

 
LVL 8

Expert Comment

by:Leo
ID: 40537076
0
 

Author Comment

by:sndmnsix
ID: 40537081
Hi Striker,
Ya, that second link is really good and I think hits the mark.  I can probably run the shell and specify the 'badlimititem' so it can resume.  I'm going to see if that actually does the trick.  I'll let you know shortly.  Thanks !

Pete
0
 

Author Comment

by:sndmnsix
ID: 40537119
So I ran the Get-MoveRequest - Identiy "{batchname}" |
Then I ran Set-MoveRequest -BadItemLimit 100 |
Then I ran Resume-MoveRequest

It appears to be continuing on just from the way the system looks to be a little busier than before.  I can't really tell for sure since it seems like the ECP has no idea and doesn't update the status of that particular batch.  I thinking it probably won't until its completed?  What are your thoughts on that?

Pete
0
 
LVL 8

Expert Comment

by:Leo
ID: 40537163
yes please, let it complete, and if you are worried about server resources, please download process explorer...
0
 

Author Comment

by:sndmnsix
ID: 40537911
Hi Striker,
As far as I can tell, it didn't complete yet.  It's been running for 10 hours minimum.  Is there any other way to check the progress on this type of thing?
0
 

Author Comment

by:sndmnsix
ID: 40538294
Hi Striker,
I didn't see error but I don't believe it ever started the operation.  It says 'Couldn't find a move request that corresponds to the specified identity.  I guess there's a difference between migration and move.
0
 
LVL 8

Expert Comment

by:Leo
ID: 40539282
yes migration is different then move.

Were you trying to move? is it completed, you can check the status through powershell....

Get-moverequest -MoveStatus Inprogress | Get-moverequeststatistics (This cmdlet will give you the status of current move request with %age of mailbox moved. After running this cmdlet run the following cmdlet to check how many move requests are in queued)

Get-moverequest -movestatus Queued | FT

After checking this, check the status of source database from where you are moving the mailbox. Check the status of databases using following cmdlet

Get-mailboxdatabasecopystatus -server "ServerName" | FT


Have a look at the Services list, and if you notice "Microsoft Exchange Migration Workflow" Service. Restart this service..
0
 

Author Comment

by:sndmnsix
ID: 40539331
Hi Striker,
It never did complete.  It actually threw an error because I believe it was looking for a mover request instead of a migration.  It actually never did start and I didn't realize it hadn't.   Anyway, there are 2 items that were skipped.  I ran 'Get-MigrationUser -BatchID "{batchname}" | Get-MigrationStatistics' and it told me 56826 items synced, and 2 items skipped.  How can I reconfigure the batch to accept more corrupted items?

Pete
0
 
LVL 8

Accepted Solution

by:
Leo earned 500 total points
ID: 40539354
0
 

Author Closing Comment

by:sndmnsix
ID: 40539448
Thanks Striker for your patience on this one.  The solution came from that last URL.  The last paragraph:

'The workaround was to export the mailbox content, rules (and every conceivable account setting) then disable the mailbox and create a brand-new one on an Exchange 2010 server. The settings were then reinstated (so the user could get back to sending and receiving) while the mailbox’s backup was gradually restored, backfilling the mailbox. The orphaned Exchange 2007 mailbox was then connected to a generic created-for-the-purpose user just in case any of the mailbox content hadn’t made it across'

The report said there was a corrupted Search Folder which I couldn't actually find.  I deleted all the search folders this specific user had and it didn't matter.  Anyway, all is well.  

Pete
0
 
LVL 8

Expert Comment

by:Leo
ID: 40539463
Good to know :-)
0

Featured Post

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.

Question has a verified solution.

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

Resolve DNS query failed errors for Exchange
Marketers need statistics and metrics like everybody else needs oxygen. In this article we explain how to enable marketing campaign statistics for Microsoft Exchange mail.
Familiarize people with the process of retrieving data from SQL Server using an Access pass-thru query. Microsoft Access is a very powerful client/server development tool. One of the ways that you can retrieve data from a SQL Server is by using a pa…
In this video we show how to create an Accepted Domain 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 Mail Flow >> Ac…

830 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