error while migration from exchange 2016 to exchange 2019

Question

hi everyone.

i have 2 exchange servers 2016 with mailboxes and 2019 cu13 clean

after starting migration 33 databases by batchname, i have an error:

StalledDueToMRS_CapacityExceeded

MsExchangeMailboxReplication.exe.config tuned, maybe some errors in file? my file:

<MRSConfiguration
    MaxRetries="60"
    MaxCleanupRetries="480"
    MaxStallRetryPeriod="00:15:00"
    RetryDelay="00:00:30"
    MaxMoveHistoryLength="5"
    MaxActiveMovesPerSourceMDB="100"
    MaxActiveMovesPerTargetMDB="100"
    MaxActiveMovesPerSourceServer="100"
    MaxActiveMovesPerTargetServer="100"
    MaxActiveJobsPerSourceMailbox="100"
    MaxActiveJobsPerTargetMailbox="100"
    MaxTotalRequestsPerMRS="100"
    FullScanMoveJobsPollingPeriod="00:15:00"
    FullScanLightJobsPollingPeriod="00:15:00"
    ADInconsistencyCleanUpPeriod="1:00:00:00"
    HeavyJobPickupPeriod="00:00:05"
    LightJobPickupPeriod="00:00:10"
    MinimumDatabaseScanInterval="00:01:00"
    BackoffIntervalForProxyConnectionLimitReached = "00:05:00"
    DataGuaranteeCheckPeriod="00:00:05"
    DataGuaranteeTimeout="00:10:00"
    DataGuaranteeLogRollDelay="00:01:00"
    DataGuaranteeRetryInterval="00:15:00"
    DataGuaranteeMaxWait="1.00:00:00"
    DelayCheckPeriod="00:00:05"
    MailboxLockoutTimeout="02:00:00"
    MailboxLockoutRetryInterval="00:05:00"
    EnableDataGuaranteeCheck="true"
    DisableMrsProxyBuffering="false"
    WlmThrottlingJobTimeout="00:05:00"
    WlmThrottlingJobRetryInterval="00:10:00"
    MRSProxyLongOperationTimeout="00:50:00"
    ContentVerificationIgnoreFAI="false"
    ContentVerificationIgnorableMsgClasses=""
    ContentVerificationMissingItemThreshold="0"
    DisableContentVerification="false"
    DisableDynamicThrottling="true"
    UseExtendedAclInformation="true"
    SkipWordBreaking = "false"
    FailureHistoryLength="60"
    LongRunningJobRelinquishInterval="04:00:00"
    ReservationExpirationInterval="00:05:00"
    LoggingPath=""
    MaxLogAge="30.00:00:00"
    MinBatchSize="500"
    MinBatchSizeKB="7168"
    ExportBufferSizeKB="10240"
    OldItemAge = "366.00:00:00"
    BadItemLimitOldNonContact = "0"
    BadItemLimitContact = "0"
    BadItemLimitDistributionList = "0"
    BadItemLimitDefault = "0"
    BadItemLimitInDumpster = "0"
    BadItemLimitCalendarRecurrenceCorruption = "0"
    BadItemLimitStartGreaterThanEndCalendarCorruption = "0"
    BadItemLimitConflictEntryIdCorruption = "0"
    BadItemLimitRecipientCorruption = "0"
    BadItemLimitUnifiedMessagingReportRecipientCorruption = "0"
    BadItemLimitNonCanonicalAclCorruption = "0"
    BadItemLimitStringArrayCorruption = "0"
    BadItemLimitInvalidMultivalueElementCorruption = "0"
    BadItemLimitNonUnicodeValueCorruption = "0"
    SendGenericWatson = "false"
    MaxIncrementalChanges = "1000"
    CrawlerPageSize = "10"
    EnumerateMessagesPageSize = "500"
    MaxFolderOpened = "10"
    CrawlAndCopyFolderTimeout = "00:00:10"
    CopyInferenceProperties ="true"
    DCNameValidityInterval = "02:00:00"
    GetActionsPageSize = "1000"
    ReconnectAbandonInterval = "2.00:00:00"
    IsEnabled = "true"
    IsJobPickupEnabled = "true"
    DeactivateJobInterval = "00:17:00"
    AllAggregationSyncJobsInteractive = "false"
    AllowRestoreFromConnectedMailbox = "false"
    StalledByHigherPriorityJobsTimeout = "00:10:00"
    CanStoreCreatePFDumpster = "true"
    DisableContactSync = "false"
    CacheJobQueues = "false"
    QuarantineEnabled = "true"
    MalwareScanEnabled ="false"
    ServerBusyBackoffExpired = "01:00:00"
    DefaultIncrementalSyncInterval = "00:15:00"

    MaxMRSConnections="100"
    DataImportTimeout="00:20:00"  
   />

Answer 1

Hi @Ilya Bokov ,

I tried to do a lot of searching for this error but couldn't find any useful information.

Regarding that config file, compare the default settings in our environment and notice that you have indeed made quite a few changes. But judging from the content of the error report, it doesn't seem to be related to these changes.

For the current situation, considering that the error report is literally related to the MRS capacity, you can try to increase the MaxMRSConnections slightly (back up the original config file first)

Mailbox migration number exceeds the default limit - Exchange | Microsoft Learn

Since there are too many factors that may affect the performance of mailbox migration, changing this value may not be useful. It is recommended to migrate in small quantities, you could try to reduce the number of mailboxes being migrated simultaneously by adjusting the batch size.

Regards

Shaofan

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". 

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.  

Answer 2

Hello Ilya,

Thank you for your question and for reaching out with your question today.

The configuration you provided for MsExchangeMailboxReplication.exe.config seems to be mostly default settings, and I don't see any obvious issues with it. However, the "StalledDueToMRS_CapacityExceeded" error typically indicates that the maximum capacity for mailbox moves or active jobs has been reached.

To address this issue, you can try adjusting the following settings in the configuration file:

1. Increase the values for the following parameters to allow for more concurrent mailbox moves and active jobs:
   - MaxActiveMovesPerSourceMDB
   - MaxActiveMovesPerTargetMDB
   - MaxActiveMovesPerSourceServer
   - MaxActiveMovesPerTargetServer
   - MaxActiveJobsPerSourceMailbox
   - MaxActiveJobsPerTargetMailbox

2. If the issue persists, you can try increasing the maximum number of MRS (Mailbox Replication Service) connections by adjusting the "MaxMRSConnections" parameter. This allows for more simultaneous connections, which can help alleviate capacity issues.

3. You may also consider increasing the maximum number of retries and the retry delay by adjusting the "MaxRetries" and "RetryDelay" parameters, respectively. This can provide more flexibility in handling transient errors or delays during mailbox moves.

After making these changes, restart the Microsoft Exchange Mailbox Replication service to apply the updated configuration.

Keep in mind that increasing these values will consume more system resources, so ensure that your server has sufficient resources to handle the additional load. It's also recommended to monitor the server's performance after making these changes to ensure that it remains within acceptable limits.

If the issue persists or you encounter any other errors, it may be helpful to review the Exchange server's event logs or consult with Microsoft support for further assistance in diagnosing and resolving the issue.

I used AI provided by ChatGPT to formulate part of this response. I have verified that the information is accurate before sharing it with you.

If the reply was helpful, please don’t forget to upvote or accept as answer.

Best regards.