License Server
The computer where Migration Console is installed also usually hosts the Migration Manager license server. The license server depends on the Remote Registry service. Please make sure that the Remote Registry service startup type is set to Automatic on the license server computer. On Windows 7, Automatic is not the default startup type for this service.
Migration Manager Database Servers
Active Directory Lightweight Directory Services Server
This server is required to store the migration project information.
| Requirement | Details |
|---|---|
| Platform |
One of the following:
|
| Operating System |
For ADAM (supported in upgrade scenario only):
For AD LDS:
|
| Additional Software |
Active Directory Application Mode (ADAM) or Active Directory Lightweight Directory Services (AD LDS) instance running on the server. |
|
|
NOTE: You can install AD LDS from the Redist\AD LDS folder on the Migration Manager CD. |
Migration Manager for Exchange Database Server
Supported SQL Servers
Migration Manager can work with the following Microsoft SQL server versions:
- Microsoft SQL Server 2008
- Microsoft SQL Server 2008 R2
- Microsoft SQL Server 2012
- Microsoft SQL Server 2014
- Microsoft SQL Server 2016
- Microsoft SQL Server 2017
- Microsoft SQL Server 2019
|
|
IMPORTANT: For environments where the TLS version 1.2 is the only enabled for Migration Manager for Exchange Database Server, the following additional software is required: Microsoft ODBC Driver for SQL Server, version 17, on all computers running Migration Manager console and on Statistics Collection Agent host. Required version of ODBC Driver for SQL Server can be downloaded from Microsoft Download Center. |
Processor Requirements
A processor for the database server must be an Intel® Xeon® E5-2650 v2 or a similar-performance processor.
Number of cores for the processor can be estimated using the following formula:
[Number of cores] = 2 + (([Mail agents count] + [Calendar agents count]) x 0.03)
|
|
Important:
|
The following table contains recommended number of cores for migrations with different parameters.
| Mail agents | Calendar agents | Number of cores | |
| Small migration | 10 | 10 | 4 |
| Medium migration | 100 | 100 | 8 |
| Large migration | 250 | 250 | 17 |
| Extra large migration | 500 | 500 | 32 |
|
|
Important: Ensure that SQL Server Edition on the database server supports required number of cores. |
Memory Requirements
To estimate the amount of RAM required for the database server, use the following formula:
[Amount of RAM] = ([Total number of mailboxes] x [Average number of messages in a mailbox] * 1.28) / 10000000
|
|
Important: The minimum amount of RAM is 8 GB. |
The following table contains required amount of RAM for migrations with different parameters.
| Number of mailboxes | Average number of messages | RAM Required | |
| Small migration | 1,000 | 20,000 | 8 GB |
| Medium migration | 30,000 | 16,000 | 64 GB |
| Large migration | 100,000 | 5,000 | 64 GB |
| Extra large migration | 500,000 | 2,000 | 128 GB |
|
|
Important: Ensure that operating system on the database server supports required amount of RAM. |
Disk Space Requirements
Disk space required to store SQL database produced by Migration Manager for Exchange depends on a type of migration you plan to perform.
Migration to Microsoft Office 365 or Microsoft Exchange 2013/2016/2019
If you migrate to Microsoft Office 365 or Microsoft Exchange 2013/2016/2019 by means of Migration Agent for Exchange (MAgE), then to estimate the disk space that SQL database will take during the course of migration, use the following formula:
[SQL database size] = [Total number of mailboxes] x [Average number of messages in a mailbox] x 1024 bytes [Size of information for single message] x 1.05 [Additional 5% of size to store error messages]
For a sample migration that involves
- 100 mailboxes
- Around 30,000 messages per each mailbox
The resulting database size is calculated as follows:
[SQL database size] = 100 mailboxes x 30,000 messages x 1024 x 1.05 = 3,225,600,000 bytes ≈ 3GB
|
|
TIP: To calculate total number of mailboxes and number of messages within them, use Quest MessageStats, or refer to the corresponding Microsoft documentation. |
|
|
Important: If you plan to use express edition of Microsoft SQL Server, consider that database size may eventually exceed the allowed size limit. That limit is 4GB for SQL Server versions prior to 2008 R2 and 10GB for version 2008 R2 or later. For detailed information on differences between SQL Server editions, refer to the corresponding Microsoft documentation. |
Other types of migration
If you are plan to perform any other type of migration supported by Migration Manager for Exchange, such as migration with legacy agents or native mailbox move, the database size does not exceed 4GB. Therefore any database servers stated above can be used as Migration Manager for Exchange Database Server including express editions.