Dell Migration Manager 8.14 for exchange - Outlook slow

[deleted]

Hello Luke,

We have now shutdown the migration servers and no calls reported till now.

Also ref the release notes and see comment

Users will not be able to use Microsoft Outlook to log on to their mailboxes while the Mail Source Agent is processing them within a Remote Users Collection. If a user is working online, Microsoft Outlook will not operate while the mailbox is being processed. After mailbox processing has been completed, a user must log off and log back on to the mailbox.

support.quest.com/.../release-notes

Regards,
Ajit

Ajit,

Are you using Remote User Collections? (RUC) What is your source & target Exchange versions, because it's not likely that you would be using a RUC in this day as they are only available using the legacy Mail processing agents, and that's not very common these days.

It's true, if you were, that's expected behaviour, and your processing of these mailboxes, if done with a RUC, should be done off hours.

Luke

My apologies, I did missunderstand that the users are "Currently" in a migration batch.

I can understand that if the mail agents are running, that your environment will see some impact, there isn't much we can do about that. The Disks/Attached storage will see lots of usage, along with other resources in your exchange environment. This is somewhat expected during processing.

You may wish to not process so many mailboxes at once if the environment cannot handle the impact. Perhaps disable a collection, and see if this helps.

Per below though, if you are using RUCs, then the users cannot be logged into their mailboxes. It will absolutely cut them off/block access.

Luke

Hello,

Sorry to interject here, where does it say in the documentation that the RUC is supported with EX 2013 using Legacy clients? Only Migration Agent for Exchange (Mage) can be used.

The only agents that preserve the OST file in Outlook outside of the Legacy mail source and mail target agents that preserve OST files is the Native move.

You're absolutely right. That's my point. Only Mage works with 2013, not legacy agents, so this isn't the cause. It could simply be that the target Exchange, or attached storage is overwhelmed with all the processing.
Luke

I have seen this before in Exchange Virtual environments the technology being used is most likely experiencing disk thrashing.

How many mailboxes are you currently sync'ing? How many agent instances are you using?

Hello,

80 calendar sync is process now for past 4 hours
No issues reported till now.

Issue observed at server :

Time: 11/23/2017 12:09:36 AM
ID: 306
Level: Information
Source: Microsoft-Exchange-HighAvailability
Machine: exchangeserver.domain.com
Message: Initiating move for database 'db1' (FromServer)



<DatabaseName>DB521EG</DatabaseName>
<DatabaseGuid></DatabaseGuid>
<ActiveServer></ActiveServer>
<ActionCategory>Move</ActionCategory>
<ActionInitiator>Automatic</ActionInitiator>
<ActionReason>FailureItem</ActionReason>
<AmRole>PAM</AmRole>
<PAMServer></PAMServer>
<MountFlags>None</MountFlags>
<DismountFlags>SkipCacheFlush</DismountFlags>
<MountdialOverride>None</MountdialOverride>
<FromServer>/FromServer>
<TargetServer></TargetServer>

It is observed that the EWS app pool indicates high cpu utilisation and the databases fail over