Archiving files after migration
FSA Migrator can ingest items in to a new, target Enterprise Vault environment during the migration. There are three aspects of this feature which need to be configured.
Configuring the archive files schedule/threads
The number of worker threads, and the schedule for when FSA Migrator will ingest items in to a new Enterprise Vault environment have been described in the previous section.
Configuring the target API server
FSA Migrator makes use of the Enterprise Vault 10.0.2 FSA API to ingest items. This means that the target environment must be running Enterprise Vault 10.0.2 or later, or this functionality will not be available. To configure the FSA API Server navigate to Settings > Archiving.
In this dialog the FSA API Server must be specified using an FQDN. In addition the port number can be given, along with whether FSA Migrator needs to communicate to the FSA API Server using SSL or not.
Configuring retention category mapping
The source and destination Enterprise Vault environments may have different retention categories and in order for FSA Migrator to ingest the items into a target environment a mapping of retention categories need to take place. In order to configure the mapping navigate to Settings > Archiving.
This dialog will show a list of the mappings if any have already been configured. The retention categories from each environment can be loaded by clicking on the green + button:
Once the retention categories have been loaded, the source categories can be mapped to destination categories.