?
Solved

Why is the Microsoft Exchange Migration tool sending mailboxes to a database other than the one I select?

Posted on 2015-01-18
4
Medium Priority
?
54 Views
Last Modified: 2015-05-19
When using the MS Exchange Migration tool through the Exchange Admin center (http interface) to move mailboxes, the migration tool sent the mailbox to a completely different database than the one selected.  We have three databases, db1, db2, and spamdb.  We are moving servers to a datacenter offsite.  DB1 and SPAMDB are local to each other (i.e. on the same server) and DB2 is the datacenter.  All mailboxes are on DB1.

When I migrated mailboxes to DB2, some actually went and others went to the SPAMDB.  Now, when I individually select the mailboxes in SPAMDB to migration to DB2, it tells me it migrated fine but I look and they're all still on SPAMDB.

Any suggestions?
0
Comment
Question by:jhudson1977
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
4 Comments
 
LVL 4

Expert Comment

by:pcmghouse
ID: 40556912
can you please check if you have the database excluded from provisioning. manual moves should work but there is a bug.
get-mailboxdatabase db2|fl isexcludedfromprovisioning
0
 

Author Comment

by:jhudson1977
ID: 40556976
I guess I have another issue I need to figure out first.  I ran the above command and got:

"The operation couldn't be performed because object 'db2' couldn't be found..."
0
 

Accepted Solution

by:
jhudson1977 earned 0 total points
ID: 40558780
Well, to fix this, I did a crash course in EMS.

I first found out that all of the move requests were getting in the way so I removed all of those using:
     "get-moverequest -movestatus completed|remove -moverequest"

Then, I did a batch move of all mailboxes in "spamdb1" back to "db1" by:
     "get-mailbox -database spamdb1|New-moverequest -BatchName "WhateverINamedIt"

Then, I did another clear of all the move requests using the commands from step 1.

I guess this was set to simply move back to the database on the local server as I didn't specify "db1".  So, in hindsight I would probably specify the target database next time (see command set below).

But, when that was all done, I went to the Exchange Admin Console (web interface) and validated that it saw everything where it was supposed to be.  Then, for giggles, I tried another migration of five small mailboxes using this interface.  It got all wonky again.  So I decided I would use the EMS again for the batch move.

I did one mailbox just to make sure I had the command correct (and it worked) and then went for the whole banana tree using:

     "get-mailbox -database db1|New-MoveRequest -TargetDatabase db2 -BatchName "WhateverYouWantToCallIt"

Everything queued up and the first three moved fine.

So, I guess the moral of the story is learn and use EMS because outside of learning the syntax, it gave me zero headaches.
0
 

Author Closing Comment

by:jhudson1977
ID: 40784721
I accepted my comment as the solution because it worked.  Not sure what else to say.  I included all the code I used in PowerShell to assist others who might run into this issue.
0

Featured Post

Are your AD admin tools letting you down?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A couple of months ago we ran into an issue that necessitated re-creating our Edge Subscriptions. However, when we attempted to execute the command: New-EdgeSubscription -filename C:\NewEdgeSub_01.xml we received an error indicating that the LDAP se…
I don't pretend to be an expert at this, but I have found a few things that are useful. I hope that sharing them here will help others, so they will not have to face some rather hard choices. Since I felt this to be a topic of enough importance and…
In this video we show how to create a mailbox database in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Servers >> Data…
This video discusses moving either the default database or any database to a new volume.

719 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question