I currently have a user that has 8,583 folders in Outlook. I was attempting to do a mailbox move for the user and the move reached 95% and was working to complete the move and then it rolled back to 0%.

I ran the following command to verify any corruption:
New-MailboxRepairRequest -Mailbox user@domain.com  -CorruptionType ProvisionedFolder,SearchFolder,AggregateCounts,Folderview -DetectOnly

The results returned as: Online integrity check for request a547a36a-a2d0-4d55-881c-06a8a201470c completed successfully.

So no corruption was found.

I also ran the following command for the move: New-MoveRequest -Identity User@domain.com -TargetDatabase DataBasexx -BadItemLimit 1000 -AcceptLargeDataLoss

Even with the bad item limit set to 1000 and no corruption found the move request did not complete.

A few questions with this,

1. Has anyone ever moved a mailbox with 8,000 plus folders and had it happen with success? How did you handle the move?
2. Any suggestions for making this move successfully?
3. Has anyone had a move request hit 95% and then go back to 0%? Why did it happen, how was it resolve?

Thanks

It should work without issue, however have you checked your application event log to see if any additional information is revealed?

Hi DigiScope,

I have reviewed the logs and have found nothing that is helpful in determining why the percentage of 95% went back to zero%. There are no warning and or critical messages that give a clear reason as to why the count for the move reset. In the logs it looks as if the move went as expected.

Odd, have you turned up the diagnostic logging as outlined here to see if you can determine the cause https://technet.microsoft.com/en-us/library/dd638094%28v=exchg.141%29.aspx?f=255&MSPPError=-2147217396

Digi,

Thanks for the link, I am going to run the move this evening and I will increase the logging level for the mailbox move service to get a better picture if the move fails again.

I am still open for any other insights or advice from any one who may have seen this or dealt with this in the past. The thing that I have never seen before that is still a bit of a mystery is when the move request is at 95% and is in the completion phase and then dumps back to 0%.

Thanks again. 

Usually I see failures at the end are caused by mailbox corruption which you checked OR by some type of mailbox rule.  So you could remove all mailbox rules and see if it will move properly, although rebuilding rules is a pain so you may want to crank up the logging to see what it finds since if its a specific rule at issue logging should catch that as well

I am going to run the increased logging this evening and I will post my results then. I verified the users rules and they only have three. So if it turns out to be one of them that shouldn't be a big issue.

Thanks again.

Great thanks for the update and I look forward to hearing more tomorrow

what version(s) of Exchange are we looking at here?

Exchange 2010 SP3 rollup 8v2. Upgrading to rollup 9 this weekend.

Ok - thanks!

Thanks everyone for your input, to resolve this I did the following:

I increased the logging level for Set-EventLogLevel -Identity "MSExchange Mailbox Replication" -Level High

I ran the following command:

New-MoveRequest -Identity User@Domain.com -TargetDatabase mailboxDBXX -BadItemLimit unlimited -AcceptLargeDataLoss

Even though there was no corrupted items when I ran a test against the mailbox and the move report showed no corrupted items the unlimited for the bas items seems to have resolved this. That is the only different factor in relation to the other failed moves attempts prior to last evenings. This is now resolved.

• Marked as answer by DHV655 17 hours 59 minutes ago

Excellent, glad turning up the logging as suggested helped you resolve the issue, thanks for the update