Dear all,

I'm in the middle of migrating from Exchange 2007 to Exchange 2013. So far everything looks good. While migrating a couple of mailboxes via Move-Request cmdlt I received an error that one particular mailbox hasn't been successfully migrated. With "Get-MoveRequest -BatchName "20140821 SBSUsers" | Get-MoveRequestStatistics" I found that error: "FailedOther" in StatusDetail.

With "Get-MoveRequest "Martin Brsamle" | fl" I had a look at its details and it showed me something strange. The contents of that mailbox seem to have been moved to the "Archive Database" instead of the supposed "Mailbox Database" though this particalur didn't even had an enabled Archive in the first place:



So I had a closer look at the details of my whole Batch: "Get-MoveRequest -BatchName "20140821 SBSUsers" | fl DisplayName,Status,TargetDatabase,Suspend,SuspendWhenReadyToComplete", and it showed several migrations being performed into the Archive Database:



I then checked whether these users now have an Archive enabled after the migration process has completed (Get-Mailbox | where {$_.ArchiveDatabase -ne $null})

But that looked normal and as expected; only users previsouly enabled with an Archive were shown here.

So why did Move-Request place the mailboxes being migrated in the Archive Database instead of the Mailbox Database and does this pose a problem?

Any help would be greatly appreciated.

If you generate a move request and do not specify target database move request will pick any database based on the site where the move request is run from. 

if you need to exclude archive database from provisioning you need to set that option. (IsExcludedFromProvisioning) switch look at http://technet.microsoft.com/en-gb/library/bb123971(v=exchg.150).aspx

So after that mailboxes move request will move it to remaining mailbox database and then you can manually create -archive mailbox on archive database.

Let me know how you get on.

Abhi