Shulou(Shulou.com)06/03 Report--

Customer Questions:

1)Exchange 2013 to Exchange 2016!

2)migration failed

3)The failure status is FailedOther

Solution:

1) Failed to migrate users, check migration status

[PS] C:\>Get-MoveRequest -Identity XXX.XXX | Get-MoveRequestStatistics

DisplayName StatusDetail TotalMailboxSize TotalArchiveSize PercentComplete

XXX FailedOther 1.268 GB (1,361,081,89... 20

2) View migration status details

[PS] C:\>Get-MoveRequest -Identity xxx.xxx | Get-MoveRequestStatistics | fl

Message : Error: This mailbox exceeds the maximum number of corrupted items specified for this request

Reasons for migration failure:

This is because there are damaged items in the user mailbox. If you want to migrate successfully, you need to skip the damaged items.

3) Migrate users, skip 100 projects

Note:

Skip items, will I lose mail?

not

Damaged items, not necessarily mail.

Notepad, contacts, calendar are all objects, generally damaged are not mail.

New-MoveRequest -Identity "xxx.xxx@contoso.com" -TargetDatabase maildb01 -BadItemLimit 100

Warning: A message is considered corrupted when it cannot be read from the source database or written to the destination database. By specifying nonzero

BadItemLimit, you ask Exchange not to copy such messages to the destination mailbox. When the move is complete, these corrupted messages will not be available on the destination mailbox.

DisplayName StatusDetail TotalMailboxSize TotalArchiveSize PercentComplete

----------- ------------ ---------------- ---------------- ---------------

xxx.xxx WaitingForJobPickup 1.268 GB (1,361,081,89... 0

Migration complete.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.