This article explains what the requirements are for migrating away from EAS, 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 EAS module should be installed on each the 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.
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 best practice 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 following are the basic steps to start this type of migration.
All Archive Shuttle modules must be enabled, and optionally a schedule for them defined. It is important to verify that none of the modules have a red background (indicating that Archive Shuttle Core has not had contact with the module) and that the module versions are as expected.
Screen: Active Directory
Select and enable one or more domains for synchronization.
Configure EAS Environment
Screen: EAS Environment
Add a new EAS environment, specifying the following:
- Module to associate with this link
- Display name to use for this link
- EAS SQL Server Name
- EAS SQL Database Name
- SQL Table schema
Assign Post Processing module to EAS Link
Select the newly created link, and map a Shortcut Process Module to it.
Map Modules to Target Link
Ensure that the link for the migration target is added, and modules associated with it.
Add Staging Area
Ensure that the Default Staging Area is configured correctly. Depending on the migration, the free space, and the number of document stores being used as the source for the migration, the ‘high water mark’ can be adjusted upwards.
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 EAS as a source.
The following general considerations should be taken into account for this type of migration:
- Ensure Shortcut Processing is configured to use EWS.
- The database server hosting EAS must be SQL Server