-
Titre
Is there a way to increase migration throughput when using QMM to migrate to Office 365? -
Description
Is there a way to increase migration throughput when using QMM to migrate to Office 365?
-
Cause
The Office 365 migration service migrates users in batches. By default, the batch size is 6, and only 3 users from the batch are processed concurrently. Mail is pulled from the Exchange environment by the Office 365 cloud, and the throughput is determined by Microsoft. Given this, additional consoles/agent hosts would not improve performance.
-
Résolution
The default batch size can be change to improve performance by modifying the registry on the QMM console. Exercise caution when modifying these values, and avoid setting the parameters to use wide ranges.
To increase the batch size numbers, create the following registry keys on a 32 bit OS Agent Host:
HKEY_LOCAL_MACHINE\SOFTWARE\Aelita\Migration Manager\Migration Agent for Exchange Online\MaxConcurrentMigrations
DWORD
Controls how many users are processed in parallel in one batch
HKEY_LOCAL_MACHINE\SOFTWARE\Aelita\Migration Manager\Migration Agent for Exchange Online\BatchSize –
DWORD
Controls how many users are put into one migration session (batch)
Migration statistics will updated after each batch.
Windows Registry Disclaimer
Quest Software does not provide support for problems that arise from improper modification of the registry. The Windows registry contains information critical to your computer and applications. Make sure you back up the registry before modifying it. For more information on the Windows Registry Editor and how to back up and restore it, refer to Microsoft Article ID 256986 “Description of the Microsoft Windows registry” at Microsoft Support.http://support.microsoft.com/default.aspx?kbid=256986 -
Informations supplémentaires
On a 64 bit machine the registry keys will need to be created under: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Aelita