Solved

Migration jobs stuck "Relinquished" Exchange 2007-2013 migration.

Posted on 2016-09-12
5
23 Views
Last Modified: 2016-10-25
Recent migrations have been flying through but today (to a different DB) its not good.

All of the mailbox move requests are stuck in a status of Relinquished or RelinquishedWlmStall.
Looing at move request statistics it seems it its saying:-

"Job is waiting for resource reservation. MRS will continue trying to pick up this request. Resource reservtion failed for DB-XYZ. Load ration 999999. Load state "critical". This resource is currently unhealthy.

Servers look fine. No other problems.
 Just migrating to a different DB.
0
Comment
Question by:paulfoel
  • 3
5 Comments
 
LVL 9

Expert Comment

by:RantCan
ID: 41794560
Have you checked the health of the destination database/server? Based on this error, it seems Exchange is resource constrained at either disk space, CPU or RAM. You might try the migrations off hours and see if the error goes away.
0
 

Author Comment

by:paulfoel
ID: 41795711
Desitnation server/DB looks fine to me. Never had a problem before running during day.

Been running 24 hours + now. 12Gb in 24 hours. Before we were approaching 7-8Gb/hour.
0
 
LVL 8

Expert Comment

by:Kevin k
ID: 41795918
Please refer to below article having couple of suggestions might helps you to resolve this issue:
http://www.adnsolutions.com/speed-up-mailbox-moves-to-exchange-2013-theyre-too-slow/

Move requests are throttled not to overload the infrastructure and can take some time. Do you get any errors in event logs?

Also check this blog discusses how you can intelligently deal with the problem of slow Exchange 2013 Migration and what best practices can users adopt while taking the big move to ensure enhanced migration performance.

You can try few options and check few things too:

1. Both servers and drives have enough available space
2. Try with MRS for a different server
3. In eventviewer do you see any events ?
4. Did you try with higher BadItemLimit count ?

Hope this helps!
0
 

Accepted Solution

by:
paulfoel earned 0 total points
ID: 41795937
To be honest, it looks like a server issue. Noticed passive DBs going into failed state randomly.

I've now switched active dbs off this server and rebooted it. (and also paused migrations) Looks much healthier now. Will switch actives back on later.

And then restart migrations tomorrow am.
0
 

Author Closing Comment

by:paulfoel
ID: 41858222
No other answers provided.
0

Featured Post

Are end users causing IT problems again?

You’ve taken the time to design and update all your end user’s email signatures, only to find out they’re messing up the HTML, changing the font and ruining the imagery. What can you do to prevent this? Find out how you can save your signatures from end users today.

Join & Write a Comment

Resolve Outlook connectivity issues after moving mailbox to new Exchange 2016 server
"Migrate" an SMTP relay receive connector to a new server using info from an old server.
In this video we show how to create a User Mailbox 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 Recipients >> Mailb…
In this video we show how to create a Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …

760 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

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now