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

paulfoel
paulfoel used Ask the Experts™
on
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.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
RantCanSr. Systems Administrator

Commented:
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.

Author

Commented:
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.
E ATech Lead

Commented:
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!
Commented:
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.

Author

Commented:
No other answers provided.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial