Backing Up Exchange
Before implementing Migration Manager for Exchange in your production environment, back up your Exchange infrastructure. We recommend that Active Directory data be backed up at least twice a day during migration.
Transaction Log File Cleanup
When Migration Manager for Exchange synchronizes mail, for every megabyte of data migrated from the source to the target, a transaction log file of equal size is generated on the target Exchange server. Exchange-aware backup applications purge the transaction logs after the backup completes. By the time the backup finishes, all logged transactions have already been applied to the store and backed up to tape, making log cleaning safe.
Large transaction logs that are generated during mailbox migration quickly occupy free disk space. To work around this problem, perform one of the following:
- If a full backup strategy is implemented in the organization or there is no backup strategy at all, then circular logging may be enabled for unattended log deletion.
- If an incremental or differential backup strategy is already implemented in the organization, then make sure that logs are cleared automatically when backup process is finished. Do not enable circular logging in this case.
Note also that Microsoft recommends turning OFF circular logging on the Exchange server. For more information, refer to Microsoft Knowledge Base article 147524: XADM: How Circular Logging Affects the Use of Transaction Logs.
Creating Aelita EMW Recycle Bin Public Folder (Optional)
|
|
Caution: If you skip this step, you must manually turn off using the Aelita EMW Recycle Bin folder during public folder synchronization (set the UseRecycleBin parameter to 0). See the Use Fine-Tuning the Agents section of the Migration Manager for Exchange User Guide for details. |
If you plan to perform public folder synchronization using Migration Manager Public Folder agents, you should create a special public folder called Aelita EMW Recycle Bin. Replicate this folder to all the public folder servers involved in the public folder synchronization process.
This folder will help prevent data loss in case of accidental public folder deletion. When a public folder is deleted in one of the environments, the public folder synchronization agents move the corresponding folder in the other environment to the Aelita EMW Recycle Bin folder, if it exists, instead of permanently deleting the folder. You can use this folder to check whether important information has been deleted, and restore any data deleted by mistake.
|
|
Caution: Only deleted public folders will be put into the Aelita EMW Recycle Bin. If you delete a message from a public folder, it will be destroyed permanently in both the Source and Target Exchange organizations. |
Creating Administrator Mailboxes for Public Folder and Free/Busy Synchronization
Administrator mailboxes should be created on all Exchange servers involved in public folder and free/busy synchronization. These mailboxes will be used to access the public folder tree and the Schedule+ Free/Busy folder when creating public folder and free/busy synchronization jobs.
The administrative mailbox selected for public folder synchronization should reside in a private mailbox database located on the same server as the public folder database. The mailbox database should be also associated with that public folder database. To set this association, in Exchange Management Console open properties of the mailbox database and specify the public database as Default public folder database on the Client Settings tab.
|
|
Caution:
|
Creating Administrator Mailboxes for Mailbox and Calendar Synchronization (Optional)
Mailbox and calendar synchronization agents access the migrated mailboxes via the administrator mailbox. By default, the Microsoft System Mailbox is used as the administrator mailbox on Exchange 2010 servers. However, in some cases it is necessary to create custom administrator mailboxes and use them instead of the Microsoft System Mailbox.