Solved

2013 Exchange database migration empty

Posted on 2016-08-08
7
23 Views
Last Modified: 2016-08-14
I recently migrated 10 mailboxes from 1 DB to the another and they completed successfully but after the move the migration tab in EAC didn't work. It would generate an error when I clicked on it. I went to view the DBs and found that one had dismounted and wouldn't mount. I ended up repairing the DB and now I'm able to mount it and also able to open the Migration tab again BUT when I attempt a mailbox migration it doesn't queue it. I click on the Migration tab in EAC and it's empty. No errors.
0
Comment
Question by:jaynes-it
7 Comments
 

Expert Comment

by:Member_2_7970830
ID: 41747569
you have to clear all the move requests. See if there are any by using the following.

Get-MoveRequestStatistics -MoveRequestQueue <database>  

Then remove them using:

Remove-MoveRequest
0
 
LVL 16

Expert Comment

by:FOX
ID: 41747571
run this command in exchange management shell to check if anything is still lingering

Get-MoveRequest | where {$_.status -ne ”Completed”} | Get-MoveRequestStatistics

ref link:  http://jermsmit.com/tag/get-moverequeststatistics/

more useful commands
ref link:  http://www.exchangemaster.net/index.php?option=com_content&task=view&id=181&Itemid=1&lang=en
0
 

Author Comment

by:jaynes-it
ID: 41747615
DisplayName               StatusDetail              TotalMailboxSize          TotalArchiveSize         PercentComplete
-----------               ------------              ----------------          ----------------         ---------------
Ray K****                CompletedWithWarnings     1.11 GB (1,191,619,840...                          100




[PS] C:\Windows\system32>
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 

Author Comment

by:jaynes-it
ID: 41747619
you have to clear all the move requests. See if there are any by using the following.

Get-MoveRequestStatistics -MoveRequestQueue <database>  

Then remove them using:

Remove-MoveRequest

I tried this but it didn't return anything
0
 
LVL 11

Expert Comment

by:Kevin k
ID: 41748496
First, you must make sure that the mailbox in DB1, not in DB2.

Second, you can run the following command to check additional information about the mailbox move:

Get-MoveRequestStatistics -Identity UserName -IncludeReport |Export-CSV C:\MRStats.csv

As a workaround, run Get-MigrationBatch -Identity "BatchJobName" | fl command and see if it pointed you directly on the cause.

Also have a look at below earlier threads might helps you to get in more detailed:

Thread1

Thread2

Also check this blog to move an Exchange Server 2013 Database to a New Location: http://exchangeserverpro.com/exchange-2013-move-database-to-new-folder-path/

Hope this helps!
0
 

Accepted Solution

by:
jaynes-it earned 0 total points
ID: 41748953
what ended up fixing this problem was recreating the migration mailbox.
1
 

Author Closing Comment

by:jaynes-it
ID: 41755365
i had to contact microsoft support and we spent hours recreating the migration mailbox which resolved the batch migrations.
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

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

Lotus Notes – formerly IBM Notes – is an email client application, while IBM Domino (earlier Lotus Domino) is an email server. The client possesses a set of features that are even more advanced as compared to that of Outlook. Likewise, IBM Domino is…
When table data gets too large to manage or queries take too long to execute the solution is often to buy bigger hardware or assign more CPUs and memory resources to the machine to solve the problem. However, the best, cheapest and most effective so…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

839 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