Exchange 2003 to 2010 Move Request Timming

We are migrating some mailboxes in our test lab from Exchange 2003 to Exchange 2010 and we've mgirated a handfull and they are on the new mailbox database. I migrated a bunch at one time and didn't pay much attention to how long it took. Now I'm trying to migrate a single mailbox however it's been shy 24 hours and it still shows it's a legacy mailbox on the old database.

First question; how long does it take to move from one database to another? I know there are variables such as speed of network and size of mailbox. This is a very small mailbox and it's on the same VM host server.

Secondly; is there any way I can force it to move now? Obviously, I don't care about what it does since it's just a lab...

Thanks!
LVL 3
pitchfordAsked:
Who is Participating?
 
abhijitmdpConnect With a Mentor Commented:
If a very small mailbox is taking more than 24 hrs., you should stop the move process and check logs for corrupted messages, also check the mailbox for any corrupted messages, and reinitiate the local move request.
0
 
pitchfordAuthor Commented:
Further more; found the "Move REquest" is filled with a bunch of statuses. I show one is currently moving and the one I'm really looking for is "Queued". Anyway to tell it to just move this one now?
0
 
pitchfordAuthor Commented:
Thanks! I found I was able to manipulate the system into doing what I wanted through the Recipient Configuration > Move Request. I just suspended everyone's move and the one I wanted to move began the process.

On a side note, our VM disk was filled up which resulted in the database unmounting. I believe this was the cause for the extended times... =)

Thanks though!
0
All Courses

From novice to tech pro — start learning today.