We are getting ready to start a massive migratin of mailboxes from 2010 to 2013.
We just did a small pilot migration and here is the analysis. What should I be looking at for the cause of the high IdleDuration time. The documantation for the script says:
IdleDuration | Amount of time that the MRSProxy service request waits in the MRSProxy service's in-memory queue due to limited resource availability. |
But what does that limited Resource availability mean.
Name : ProcessedStats1
StartTime :
EndTime : 7/12/2016 10:48:04 PM
MigrationDuration : 04:40:09
MailboxCount : 182
TotalGBTransferred : 71.61
PercentComplete : 98.51
MaxPerMoveTransferRateGBPerHour : 1.12
MinPerMoveTransferRateGBPerHour : 0.01
AvgPerMoveTransferRateGBPerHour : 0.22
MoveEfficiencyPercent : 80.20
AverageSourceLatency :
AverageDestinationLatency :
IdleDuration : 89.61 %
SourceSideDuration : 4.78 %
DestinationSideDuration : 5.39 %
WordBreakingDuration : 3.06 %
TransientFailureDurations : 0.89 %
OverallStallDurations : 0.03 %
ContentIndexingStalls : 0.00 %
HighAvailabilityStalls : 0.00 %
TargetCPUStalls : 0.03 %
SourceCPUStalls : 0.00 %
MailboxLockedStall : 0.00 %
ProxyUnknownStall : 0.00 %
Jeff C