Chat now with support
Chat with Support

Migration Manager for Exchange 8.15 - User Guide

Pre-Migration Activities Migration Process Calendar Synchronization Mailbox Migration Public Folder Synchronization Free/Busy Synchronization Tracking the Migration Progress Creating Batches of Synchronization Jobs Outlook Profile Update Fine-Tuning the Agents Using Agent Hosts for Migration Agents Configuring Migration Using PowerShell Appendix A. Measurement of Migration Agent for Exchange Performance Appendix B. Migrating Large Public Folders to Exchange 2013 (or Higher) and Office 365 Appendix C. Migration of Recoverable Items Subfolders (Optional)

Load Balancer solution parameters

Load Balancer solution handling

The Add-MMExExchangeRemoteHost has the following syntax:

Add-MMExExchangeRemoteHost -OrganizationName <Exchange organization name> -FQDN <FQDN name> -Version <Exchange server version> [-ADSite <Active Directory site name>]

Where

  • OrganizationName is a name of Exchange Organization.
  • FQDN is FQDN name of Client Access Server or Load Balancer in Exchange organization.
  • Version is version of Exchange server that is accessed by means of Client Access Server or Load Balancer in Exchange organization.
  • Ex2010sp2
  • Ex2010sp3
  • Ex2013
  • Ex2016
  • Ex2019
  • ADSite - is a name of Active Directory site where Client Access Server or Load Balancer is located. This parameter is optional.

Example: Add-MMExExchangeRemoteHost

The following cmdlet adds the FQDN of Client Access Server or Load Balancer that reside in the source or target organization to the project database:

Add-MMExExchangeRemoteHost -OrganizationName ExchangeOrg1 -FQDN ExchCAS.source.com -Version Ex2010sp3

Appendix A. Measurement of Migration Agent for Exchange Performance

IMPORTANT: This section is applicable for migration scenarios supported by legacy Exchange Agents only. For migration scenarios supported by MAgE refer to the Public Folder Synchronization (MAgE) document.

This section contains performance test results of a single Migration Agent for Exchange instance that performs mail data migration from Exchange Server 2010 to Exchange Server 2013.

Performance test results:

  • Maximum memory consumption per instance is about 1000 MB.
  • Average data processing speed per instance is 3.5 GB per hour.

Configuration of the Test Environment:

Server Role Server Operating System CPU RAM, GB
Exchange Server 2010, source Windows Server 2008 R2 Enterprise SP1 4 vCPUs (Intel Xeon E5-2665) 34
Exchange Server 2013, target Windows Server 2012 8 vCPUs (Intel Xeon E5-2670 v2) 30
Agent host Windows Server 2012 R2 8 vCPUs (Intel Xeon E5-2670) 15
SQL server 2008 R2, Migration Manager console Windows Server 2008 R2 Enterprise SP1 2 vCPUs (Intel Xeon E5-2665) 17

Network speed: 1 Gbit/s.

Appendix B. Migrating Large Public Folders to Exchange 2013 (or Higher) and Office 365

Unlike Exchange versions 2010 and earlier, in Exchange 2013 or higher and Office 365 public folders are stored in public folder mailboxes, and size limit for such mailboxes is 100GB for Exchange organization and 50GB for Microsoft Office 365. Therefore, if public folder content in source organization is larger than the limit on the target, then to migrate it you will need to perform specific steps described in this section.

Important: Currently, Migration Manager for Exchange processes public folders of source Exchange 2013 or higher organizations as a single list of public folders ignoring their actual division by public folder mailboxes. Therefore, you need to plan public folder migration from an Exchange 2013 or higher organization according to information in this section in the same way as for Exchange 2010 and earlier organization.

Determining Public Folders Size

As a first step, you need to analyze the overall size of public folders that are planned to be migrated to Exchange organization. This can be done by reviewing information in Exchange System Manager (applicable to Exchange 2003) or by invoking theGet-PublicFolderStatistics cmdlet (applicable for Exchange 2007 or 2010).

  • If the size is less than the size limit, you don’t need to follow the below procedures. Instead you can simply migrate all public folders to a single public folder mailbox using Migration Manager for Exchange. For more information, see Public Folder Synchronization.
  • If the size is almost equal to or more than the size limit, you will need to split public folders into branches where each branch is less than the size limit and then migrate branches of public folders to separate Exchange public folder mailbox, as described in subsequent topics.
Related Documents