How do I migrate archived email using in-flight stub rehydration?
Complete each of the major steps listed below to perform a mailbox migration with in-flight stub rehydration:
- Step 1: Create the mailbox migration project with in-flight stub rehydration
- Step 2: Add items to the mailbox migration project in MigrationWiz
- Step 3: Run the archive extractor
- Step 4: Start the mailbox migration
The sections below provide detailed instructions for each of these major steps.
Note: Read the In-Flight Stub Rehydration Overview article to learn more about in-flight stub rehydration.
Important: If the source Exchange Server uses two or more domains for email, and archived email needs to be migrated for both domains, then you must configure separate migration projects with in-flight stub rehydration for each domain. A different LDAP server is defined in each project as covered in step 6 and 7 below.
Step 1: Create the mailbox migration project with in-flight stub rehydration
- Create a new mailbox migration project. Read the How do I create a new mailbox migration project? article for more information about how to create a project.
- Configure Exchange Server 2003+ or Hosted Exchange as the source endpoint, and click Next Step. Read the How do I add endpoints to a customer in MSPComplete? article for more information about how to create an endpoint.
- Checkmark the box next to Migrate archive stubs to configure in-flight stub rehydration for the mailbox migration project.
Note: Stub rehydration for hybrid Exchange configurations can only be performed using the BitTitan Archive Migration Service (AMS). Read the AMS Overview article for more information.
- Enter the connection string for the Enterprise Vault SQL server "Directory" databaseeinto the SQL Connection String field.into the SQL Connection String field.
Example: Initial Catalog=<Enterprise Vault directory>;Data source=<data source>;User Id=sa;Password=<password>
- In the Archive source Type drop-down menu, leave "Enterprise Vault" selected. Veritas Enterprise Vault (version 9 or later) is the only email archive system supported at this time.
- Select Specify Active Directory if any of these conditions are true:
- If the source Exchange Server connects to an Active Directory that is not configured as a default.
- If the source Exchange Server uses two or more domains for email, and archived email needs to be migrated for both domains. Configure separate migration projects with in-flight stub rehydration for each source domain, and define the appropriate LDAP server in the step below.
Note: Skip to step 9 below if the Exchange Server connects to the default Active Directory.
- Enter the path for the Active Directory into the Active Directory Path field.
- Enter a username and password if credentials are required to connect to the Active Directory.
- Click Save Project.
- Configure the destination endpoint, and click Next Step.
Note: Read the How do I add endpoints to a customer in MSPComplete? article for more information about how to create an endpoint.
- On the project summary page, you can choose to use an access token or enter your own unique extractor code to associate the archive extractor that will run on the source environment with the mailbox migration project in MigrationWiz.
- The access token is a system-generated code that you enter into the archive extractor without having to share your username and password for MigrationWiz. This option is advantageous if you plan to delegate deployment of the archive extractor to your customer but don't want to share your MigrationWiz password.
- The extractor code is a user-defined code that you enter into the archive extractor only after first authenticating to MigrationWiz. This option is advantageous if you are migrating from multiple source servers to a single destination server, or from a single source server to multiple destination servers and are able to share your MigrationWiz password.
Write down (or copy/paste) the access token or extractor code, because you will need it when running the archive extractor setup file.
Add items to the mailbox migration project in MigrationWiz. Read the How do I add items to my migration project? article for more information about how to add items to a project.
- Open the archive extractor setup file on a virtual or physical machine that is in the same local area network as the Enterprise Vault SQL server, file server, and the Active Directory. Read the What is the archive extractor for in-flight stub rehydration? article for more information about the archive extractor.
- Type one of the following options and press Enter to associate the archive extractor with the mailbox migration project in MigrationWiz.
- Option 3 to test the connection between the archive extractor and the Enterprise Vault SQL server, file server, and the Active Directory.
- Option 4 to view the help menu for the archive extractor.
- Option 1 to enter your MigrationWiz credentials and the extractor code you defined when you created the mailbox migration project.
- Option 2 to enter the system-generated access token that you wrote down when you created the mailbox migration project.
- The following support options are also available:
- The archive extractor must be up and running for the entire duration of the mailbox migration because it does not run as a background process. Read the In-Flight Stub Rehydration Overview to learn how the archive extractor works in tandem with MigrationWiz to migrate archived email.
- The archive extractor will fail when it finds vault stores that are not part of a vault store group; that is, when the vault store’s group version field is empty.
- There are many migration strategies that you can employ, depending on the size of the mailbox migration. Read the What are the common migration strategies? article for more information about the different migration strategies.
- Start the mailbox migration when you are ready to begin. Read the How do I start a migration? article for more information about starting the migration.
- During the migration, the archive extractor generates "success" and "failed" CSV files that can be used to define the destination of orphaned archived email or correct email addresses that may be incorrect or could not be found. Read the What are the archive extractor CSV files? article to learn how to modify the CSV file for your mailbox migration project.