Important: We are no longer supporting Enterprise Vault migrations using in-flight stub rehydration. This documentation is available only for reference purposes; it will be archived soon.
What is the archive extractor for in-flight stub rehydration?
The archive extractor for in-flight stub rehydration is a small console application that extracts archived messages and attachments from the Enterprise Vault (EV) servers configured on the Source environment. The data is then securely transmitted to MigrationWiz for the purpose of reconstructing the messages and migrating them as whole to the Destination environment.
Note: Read the In-Flight Stub Rehydration Overview article to learn more about how the extractor agent and MigrationWiz work in tandem. Also read the How do I migrate archived email using in-flight stub rehydration? article for full instructions on how to migrate a mailbox using in-flight stub rehydration and deploy the archive extractor.
Deploy the archive extractor to a virtual or physical machine that is in the same local area network as the EV SQL servers, file server, and the Active Directory.
These are the additional system requirements for the archive extractor:
- Windows OS.
- .NET Framework version 4.6.1 or later.
- 8GB of RAM or more, depending on the number of concurrent migrations.
- Free disk space for the extractor logs. For example, large mailboxes of 10 GB or more may generate a log file as large as 100 MB.
- Read-only access to all EV tables on all EV SQL servers through port 1433, as well as access to the EV file server and the environment's Active Directory.
An ideal configuration is to run the archive extractor on a virtual or physical machine running Windows Server 2008 or later, with 8+ GB of RAM, and 500 GB of storage.
- If you plan on using SQL authentication, make sure that SQL authentication is enabled on the SQL server(s).
- If you plan on using Windows Authentication, make sure the Windows user account under which the archive extractor is running has access to the SQL servers.
Note: To use Windows Authentication, there must be no "UserId" in the SQL connection string that you input into MigrationWiz when setting up the project.
- Ensure the user account and machine running the archive extractor has access to all EV tables on all EV SQL servers.
- Do not deploy the archive extractor directly on the Enterprise Vault SQL server, file server, or the Active Directory server.
- Leave the archive extractor up and running through the duration of the mailbox migration (i.e., leave console window open). The migration will start automatically after the last step of the configuration.
- After authenticating, the archive extractor generates "succeeded" and "failed" CSV files which list the mailboxes and messages that were successfully migrated and the ones that failed, such as orphaned email or email addresses that were incorrect and could not be found. The "failed" file can be used to correct the failures. Read the What are the archive extractor CSV log files? article to learn how to modify the CSV file for your mailbox migration project.