Exchange 2007 - Moving Mailboxes did not move Data

We have an Exchange 2007 environment, we moved mailboxes from one mailbox store to another.  We were able to send/recieve without any issues from a Blackberry device.  After opening the mailbox all of the "old" information that was in database A has not moved over to Database B.  We can see the files in the database A, but cannot get them to Database B.  It is almost as if it created a new mailbox instead of moving the mailbox from Database A.

Any ideas?
letotadAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
letotadConnect With a Mentor Author Commented:
Well it seems that this was an error with the database itself.  We had to take the database offline, do a defrag then a hard repair of the database to get it working.  Thanks to all of the suggestions.
0
 
pr0t0c0lConnect With a Mentor Commented:
You need to use the System Manager to move the mailboxes.  Depending what options you use, they will take some time.  
Under mailboxes folder choose folder you would like to move.  Right Click and then go to exchange tasks.  Click move mailbox. Choose the next container you would like to move it to.  Approximately and account with 500MB will take like 10 - 20 minutes.  Several mailboxes might take more time.  All this will be blind to the user.  Hope this helps.
0
 
letotadAuthor Commented:
We are running on Exchange 2007 there is not a System Manager.  We are using the Exchange Management Console.  We have done some testing and it appears that during the copy there was an error and it made a new mailbox on Database B.  When we tried to move it back there was a mailbox already in Database A so now there are 2 mailboxes.  When we try and use the - AllowMerger:$true command after the move mailbox command in the Command Shell it says that the mailbox already exists and will not merge the 2 mailboxes.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
Exchange_GeekConnect With a Mentor Commented:
This definitely leaves two errors in application logs - i remember this one. I had taken this to Microsoft (our client had 2k7 SP1 RU3) - they spent 3 weeks analyzing logs - they provide me with the same KB (that i had read ages ago)

http://support.microsoft.com/default.aspx?scid=kb;EN-US;940757 

Hope this is not your issue (do not mind if your EMC does not crash as per the KB - refer the events)
0
 
letotadAuthor Commented:
I am not sure that this is the same issue.  We have used the command shell in Exchange to try and merge the mailboxes, but it fails stating that the mailbox is in both databases, but it will not merger the two when using the -AllowMerge:$true paramater.  We are not getting the errors that are included in that article, just one that says it was unable to move the mailbox through the command shell.

Any other thoughts?
0
 
Exchange_GeekCommented:
Take the pst out of the new mailbox - disable the mailbox - reconnect the old mailbox to the user - give him the PST. Simple

Glad to hear you're not in the same mess.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.