Exchange 2010 Mailbox Move stuck in "Completing" for hours

One more thing to add:
Without knowing that this mailbox move was NOT completed, I initiated another mailbox move (15GB in size) and that task has been completed.

[PS] C:\Users\admin\Desktop>Get-MoveRequest -Identity 'user@domain.com'

DisplayName               Status                           TargetDatabase
-----------                           ------                              --------------
User                       CompletionInProgress       New_Mailbox2

Hi,

all exchange services are running?

Do you see any events regarding migration in Event Viewer?

Cheers

Try this:

Get-MoveRequest -Identity 'user@domain.com' | Get-MoveRequestStatistics | Format-List

If you can paste the results in this thread.

"all exchange services are running?' --> Yes
"Do you see any events regarding migration in Event Viewer?"--> Please see attached.
MoveStat.txt

I see a lot of these:
(1)
Log Name:      Application
Source:        MSExchangeIS
Date:          11/23/2017 3:33:22 PM
Event ID:      9660
Task Category: Logons
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      DC1.domain.local
Description:
User UserName (/o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=UserName   Jra74) failed to sign in because their mailbox is in the process of being moved.

I saw several of these around the same time frame.
(2) Log Name:      Application
Source:        MSExchange ActiveSync
Date:          11/23/2017 1:27:53 PM
Event ID:      1016
Task Category: Server
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DC1.domain.local
Description:
Exchange ActiveSync has encountered repeated failures when it tries to access data on Mailbox server [DC1.domain.local]. It will temporarily stop making requests to the Mailbox server for [60] seconds to reduce load on that server. This delay may occur if the Mailbox server is overloaded. If this event is logged frequently, review the Application log on this server and the Mailbox server noted above for other events that could indicate the root cause of performance problems.

(1) I used 10,000 in -BadItemLimit.
(2) I can wait. It is holiday.
(3) " Otherwise you can try removing the move request and restarting the MRS service." ---> I picked up this article in google. Someone said they got lucky when they restarted Exchange Replication Service. Can you explain to me how it may help this situation? What is the harm doing it now?

Restarting in the middle of a move?  I've never done that but I can't imagine it would help, but if you're going to kill it anyway then why not.  This has happened to me before and for the life of me I can't remember what I did.  I think it had something to do with the disconnected mailbox left by the move but I could be wrong.  In any case that's a huge mailbox so maybe it's just taking a long time.

I have moved the several mailboxes since yesterday and at the end of each mailbox move request, I saw either - completed or  failed. Since it says “completing”, given enough time, I may see the status changed to completed.
I will sit tight for the balance of the day.

Have you checked the Event Viewer on both the source and target servers?

The move is within the same server (SBS2011).

I attached a text file that contains three types of Exchange related events that I see repeatedly.
Event-Viewer.txt

YES!!! IT IS FINALLY FINISHED:

DisplayName                          Status                    TargetDatabase
-----------                                    ------                        --------------
User_Name                             Completed           New_Mailbox2

Should I clear all these  "Completed" move requests in Move Request Window in Exchange Management?
If I keep them there, what is the draw back or benefit?

If you keep those requests, any other migration for a user listed in the move request will not be able to start.