Exchange Migration StalledDueToTarget_DiskLatency

The move request statistics can be viewed by running the below command:
Get-MoveRequestStatistics | Select DisplayName,StatusDetail,PercentComplete

ISSUE:

Stalledtotarget_disklatency:

StalledDueToTarget_DiskLatency exchange migration statusStalledDueToTarget_DiskLatency exchange screenshot

CAUSE:

This might happen if there are any issues in the disk performance causing disk latency; the response time from the source is getting high and the migration batches are getting timed out. This delays the movement of the mailboxes.

RESOLUTION:

Start checking the target Exchange 2016 disk performance IOPS etc. If we get this, then there are some serious problems in the Exchange 2016 performance. And this depends on the designed storage architecture, how the database copies are distributed with how many mailboxes in each copy.

If this is a migration to Exchange Online, this will require a ticket to Microsoft. They will work the restrictions and throttling on their side; once we mention “Stalledtotarget_disklatency” they typically address the issue very quickly.

One suggestion we did get from a Microsoft was to remove the move request the create a new one with highest priority.

Remove-MoveRequest -Identity “[email protected]”

New-MoveRequest -Identity “” -TargetDatabase “” -BatchName “” -Priority Highest

Brandon Stuart, PEI

This post is part of a series on Exchange Migration Status Messages. If you’re interested in learning more technical tips like this one, subscribe to our blog below!

Other Posts in this Series

RelinquishedWlmStall

StalledduetoCI

Let’s talk IT.

Request a consultation. Tell us where your offices are and one of our engineers will be in touch within one business day — no sales script, no obligation, just a working conversation about what you’re trying to do.

cyber insurance

"*" indicates required fields

This field is for validation purposes and should be left unchanged.
Your Name*