I am in the midst of a 2007 to 2013 exchange migration. Everything was working great and we have been running concurrently since CU1 was released. We did several practice migrations and had no issue. We start our final migration this weekend, and the migration goes south. Now I queue up a group of mailboxes, and it takes an extremely long time to finish, and I have log files filled with indexing error and replication service errors, to which I can find nothing on google. I try to tweak settings but I am afraid im going to do more harm than good. It seems like only one mailbox is actively moving 1 mailbox at a time, even tho 20 are "actively syncing". One error log event that concerns me the most is this one :
Log Name: Application
Source: MSExchange Mailbox Replication
Date: 8/11/2013 4:38:31 AM
Event ID: 1121
Task Category: Request
Level: Error
Keywords: Classic
User: N/A
Computer: red-ex1.redlands.edu
Description:
The Microsoft Exchange Mailbox Replication service was unable to process a request due to an unexpected error.
Request GUID: 'e42e5447-942b-4a0d-bf64-31d86efd4657'
Database GUID: 'c05eb970-d0a8-400f-9759-8511fdce6845'
Error: Resource reservation failed for 'MdbWrite(DBname)' (MdbLatency(DBame)): load ratio -1, load state 'Unknown', metric (null)..
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchange Mailbox Replication" />
<EventID Qualifiers="49156">1121</EventID>
<Level>2</Level>
<Task>2</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-08-11T11:38:31.000000000Z" />
<EventRecordID>1400432</EventRecordID>
<Channel>Application</Channel>
<Computer>red-ex1.redlands.edu</Computer>
<Security />
</System>
<EventData>
<Data>e42e5447-942b-4a0d-bf64-31d86efd4657</Data>
<Data>c05eb970-d0a8-400f-9759-8511fdce6845</Data>
<Data>Resource reservation failed for 'MdbWrite(DBName)' (MdbLatency(DBName)): load ratio -1, load state 'Unknown', metric (null).</Data>
</EventData>
</Event>
I currently have a job running to migrate 7 users with large mailboxes. This error appears 6 times every 15-20 minutes. It seems that there is a collision, then the mailbox goes into some sort of time out period, and try again. I've googled this error and tried the exchange 2010 fixes but no luck.
Thanks!