Pre-Enterprise Vault 10.0.0.4 source
Prerequisites
It is essential that the following steps have been completed prior to beginning the migration:
·All Modules are enabled
·Appropriate Active Directory Domains are enabled for scanning
·An Enterprise Vault Environment has been added for migration
·A Link Database has been created for the source archive
·Module Mappings are configured for the source Vault Store and also the target Vault Store
The target for the journal archive migration must also:
·Be a user and be setup with a mailbox
·Have a journal archive created for it, in an appropriate Vault Store
·Be listed as a Journal Target in the Vault Administration Console
|
|
NOTE: The Enterprise Vault journal task is used to ingest the data in to the target journal archive container. |
Map containers - For the journal archive
The first thing to do when migrating a journal archive to a new vault store is to do a container mapping. This is slightly different to the process followed earlier in the document since Archive Shuttle must do a single container mapping. To setup the mapping, follow these steps:
1.Click Manual Mapping.
You will now see two lists of containers.
2.Locate the source journal archive in the left hand list, and select the radio button next to the archive.
3.Locate the target journal archive in the right hand list, and select the radio button next to the archive.
|
|
NOTE: All the normal filtering and searching is available on the Single Container Mapping screen, which can help identify the correct archives when there are many journal archives displayed on screen. |
4.Click Add Mapping.
Set policies and enable migration
Once the container mapping has been selected, it is necessary to add two more components to the link, before the migration can be enabled. To setup the migration, follow these steps:
1.Click Existing Mappings.
|
|
NOTE: All the normal filtering and searching is available on the Existing Mapping screen, which can help identify the mapping. |
2.Locate the mapping that was created in the previous step.
3.Select the checkbox next to the mapping.
4.From the toolbar, select Set Workflow Policy and choose the Journal Workflow.
5.From the toolbar, select Set Filter Policy and choose a filter if one is required.
6.Finally, from the toolbar select Enable for Migration, and Enable Item Gathering.
|
|
NOTE: The container mapping will now look much like other mappings that may have been created. Ensure that the Item Gathering and Migration Enabled flags are displayed before moving on to monitoring the migration. |
Monitoring the migration
Monitoring the Stage 1 synch process for a journal archive is the same as with other types of archive migration. A few minutes after setting the policies and enabling migration (see previous section), the container will appear on the Stage 1 (Sync Data) screen in the administration console.
Performing Stage 2 and extra steps
Migrating a journal archive is slightly different than migrating an ordinary Enterprise Vault archive. There are a few additional steps, as outlined below:
1.Stop the Enterprise Vault Journal Task, and set the startup of the task to Disabled.
|
|
NOTE: The journal mailbox that the task was targeting will now start to grow in size because Enterprise Vault is no longer processing items from it. |
2.Go to the Stage 1 (Sync Data) screen.
3.Locate the container mapping for the journal archive, and select the check box next to it.
4.From the toolbar, select Enable Stage 2.
5.After a few minutes, observe the Stage 2 (Switch User) screen and ensure that after a few more minutes the migration is marked as complete.
The Journal Archive has now been moved to a new Vault Store, and a new archive. The final step is to change the journaling process in Enterprise Vault. Usually this is a matter of changing the journal target to be the new archive, and restarting the journal task after setting the task startup back to Automatic.
|
|
NOTE: Depending on the migration being performed, it may also be necessary to reconfigure the Exchange journaling configuration to journal to the new mailbox. |
Enterprise Vault 10.0.0.4 or later source
Prerequisites
It is essential that the following steps have been completed prior to beginning the migration:
·All Modules are enabled
·Appropriate Active Directory Domains is enabled for scanning
·An Enterprise Vault Environment has been added for migration
·A Link Database has been created for the source archive
·Module Mappings are configured for the source Vault Store and also the target Vault Store
Map containers - For the Journal Archive
The first thing to do when migrating a journal archive to a new vault store is to do a container mapping. This is slightly different than the process followed earlier in the document since Archive Shuttle must do a single container mapping.
To setup the mapping, follow these steps:
1.Navigate to the Bulk Mapping or Manual Mapping page.
2.Type the beginning of the archive name in the Name filter. Click the Apply button at the right of the filter row.
3.Select the checkbox next to the archive, and click Add Mappings from the navigation bar.
|
|
NOTE: A short wizard will start, which gathers information relating to the mapping for the archive. |
4.The destination of the migration can then be chosen from the available list and then subsequent pages of the wizard will prompt for further information.
|
|
NOTE: It is recommended that a workflow policy is created that suits the requirements, or the Journal Archive workflow is chosen. |
Set Policies and Enable Migration
Once the container mapping has been selected, it is necessary to add two more components to the link, before the migration can be enabled.
To setup the migration, follow these steps:
1.Click Existing Mappings.
|
|
NOTE: All the normal filtering and searching is available on the Existing Mapping screen, which can help identify the mapping. |
2.Locate the mapping that was created in the previous step.
3.Select the checkbox next to the mapping.
4.From the toolbar, select Set Workflow Policy and choose the Journal Workflow.
5.From the toolbar, select Set Filter Policy and choose a filter if one is required.
6.Finally, from the toolbar select Enable for Migration and Enable Item Gathering.
|
|
NOTE: The container mapping will now look much like other mappings that may have been created. Ensure that the Item Gathering and Migration Enabled flags are displayed before moving on to monitoring the migration. |
Monitoring the Migration
Monitoring the Stage 1 synch process for a journal archive is the same as with other types of archive migration. A few minutes after setting the policies and enabling migration (see previous section), the container will appear on the Stage 1 (Sync Data) screen in the administration console.
Performing Stage 2 and Extra Steps
Migrating a journal archive is slightly different to migrating an ordinary Enterprise Vault archive. There are a few additional steps, as outlined below:
1.Stop the Enterprise Vault Journal Task, and set the startup of the task to Disabled.
|
|
NOTE: The journal mailbox that the task was targeting will now start to grow in size because Enterprise Vault is no longer processing items from it. |
2.Go to the Stage 1 (Sync Data) screen.
3.Locate the container mapping for the journal archive, and select the check box next to it.
4.From the toolbar, select Enable Stage 2.
5.After a few minutes, observe the Stage 2 (Switch User) screen and ensure that after a few more minutes the migration is marked as complete.
The Journal Archive has now been moved to a new Vault Store, and a new archive. The final step is to change the journaling process in Enterprise Vault. Usually this is a matter of changing the journal target to be the new archive, and restarting the journal task after setting the task startup back to Automatic.
|
|
NOTE: Depending on the migration being performed, it may also be necessary to reconfigure the Exchange journaling configuration to journal to the new mailbox. |
Migrating a journal archive to Office 365
This section outlines actions you can take to perform a migration of a single journal archive to Office 365.
Convert journal messages to Office 365 journaling format
Occasionally, before migrating Journal messages from Enterprise Vault to Office 365, it is important to consider if want to have migrated the entire envelope, or just the P2.
Archive Shuttle has a Convert Journal messages to Office 365 Journaling Format setting on Office 365 module tab in System Configuration, and this setting works as follows:
a) If unchecked (default), it will migrate the whole envelope (P1 and P2) to Office 365. In the Compliance Center, then you can do a search, because envelopes were implemented in the search functionality.
Journal message migrated with P1 and P2 item to Office 365:
b) If checked, it will migrate only the P2 message and will remove the P1 header. The metadata of the P1 message (DL Expansion, BCC etc.) is then put into special properties of the P2. Because of this, Office 365 Compliance Search can find them.
Journal message migrated with P2 item to Office 365:
In the background, once Archive Shuttle collected information from the P1 message, it will create new properties and store the P1 info into them.
|
|
NOTE: Archive Shuttle does not currently support only ingesting P1 and stripping P2. |
Considerations when enabling the option
·If you wish for the items to be migrated much more as-is, i.e. matching the source system, then do not enable the option.
·If you wish for the items to be more inline with the way that Office 365 does this natively, then the option should be enabled.
·If you are doing a Journal Transformation migration, then the option is enabled silently, and can not be disabled.
·When looking at emails from a compliance point of view, messages stored with the GERP attribute contain information about who got the original email, but not the why they got the email (that information is stored in the P1 message, for example, the message was sent to a distribution that contained a particular recipient)
·Office 365 works with either formatted message.
·Migrating data with the P1 & P2 data means that the P1 data becomes a free-text search, whereas enabling the option to convert the journal message (and adding the information to the GERP attribute) means it is a fully indexed property of the message. Confusion can arise if you search for mails to X, if P1 & P2 data is migrated, this type of query may return fewer results. Instead, you should perform a free-text search instead, but then it is not possible to search for mails o X in the same way.