This article explains the requirements for migrating from SourceOne or EmailXtender to another environment, and then covers the basic steps that should be followed to start such a migration.
The following is a list of requirements.
- Modules installed on source: The SourceOne module should be installed on an appropriate source server.
- Modules installed on target: The appropriate modules should be installed on each appropriate target server involved in the migration.
- AD Collector module installed: An AD Collector module should be installed so that it can collect user-level information for the migration project.
- Staging Area created: One or more staging areas should be setup, of an appropriate size, and should be excluded from virus scanners.
- Workflows reviewed: The Stage 2 workflows should be reviewed and, if necessary, customized to meet the needs of the project.
- Apply appropriate failed item threshold: It is recommended to find an appropriate failed item threshold for the project/customer and apply that at the links level. This way, all mappings which are created will inherit this value.
The basic steps to start this type of migration are below.
1: Enable Modules
All Archive Shuttle modules must be enabled, and a schedule for them defined if necessary. It is important to verify that none of the modules have a red background (indicating that the Archive Shuttle Core has not had contact with the module), and that the module versions are as expected.
2: Enable Domains
Screen: Active Directory
Select and enable one or more domains for synchronization.
Note: Configuration of EmailXtender is done in the same way as SourceOne.
3: Configure SourceOne Environment
Screen: SourceOne Environment
Add a new SourceOne environment, specifying the following:
- Module to associate with this link
- Display name to use for this link
- SourceOne Basepaths (These are the share paths for each archive folder. Multiple paths should be semicolon separated.)
- SourceOne/EMX SQL server
A Link Database will be created for this environment. It is possible to override the SQL Server and instance, if required.
4: Enable Organization
Screen: SourceOne Environment
The module will scan for organizations and present them in a list. The required organizations should be enabled so that the module can scan for archives.
5: Map Modules to Target Link
Ensure that the link for the migration target is added, and modules associated with it.
6: Map Modules to Source Link
Ensure that the source links have a Shortcut Processing module assigned to them. This module will scan mailboxes to find shortcuts. This is required before the import can begin.
7: Add Staging Area
Ensure that the Default Staging Area is configured correctly. Depending on the migration, the free space, and the number of archive folders being used as the source for the migration, the ‘high water mark’ can be adjusted upwards.
8: Configure Folder-less folder name
Screen: System Configuration
SourceOne does not maintain folder information for items. Therefore, a folder will be created to migrate items into. The name of this folder can be specified under ‘Folder name for folder-less items’ on the General System Settings Page.
The module scans for shortcuts in a mailbox and any items which have a shortcut will be migrated to the current folder where that shortcut resides.
9: Map one or more containers
Screen: Bulk Mapping
One or more containers can now be mapped and migration can begin. It is often easiest to use a filter on the bulk mapping screen to show only SourceOne as a source.
The following general considerations should be taken into account for this type of migration:
The following filters are not supported:
- If you need to migrate the primary S1 archive into a primary mailbox, and a secondary S1 archive into a personal archive (in Exchange or Office 365), then two mappings will be required.
- It is recommended to add the following index to the SQL databases relating to S1. It will improve the item collection process:CREATE NONCLUSTERED INDEX IX_RouteEmailId ON [dbo].[Route] ([EmailId])INCLUDE ([MessageID], [RouteMask], [PartitionId]
- It is recommended to add the following index to the SQL databases relating to EmailXtender. It will improve the item collection process:CREATE NONCLUSTERED INDEX IX_RouteEmailId ON [dbo].[Route] ([EmailId])INCLUDE ([MD5HashKey],[TimeStamp])
- Disabling source archives is currently not available as part of a Workflow Policy and will need to be done manually post migration.