Splitting

Archive Shuttle Journal Splitting setup

The Office 365 Virtual Journal feature brings with it the possibility to migrate large journal archives to Office 365, using multiple target mailbox/personal-archives and specifying criteria such as number of items and size of target. This article explains more detail about this splitting process.

There are two ways that data can be split:
Number of Items
This is the simplest form. The splitting to a new mailbox/personal-archive occurs when the specified number of items are routed to the target mailbox or personal archive.
Size of Items
The splitting here is determined by the size of the items from the source environment. In the case where migration is from Enterprise Vault, the size used is the larger of the original size versus compressed size. When the amount of data routed to a target container reaches the specified value, a new target container will be created.

Journal Archives in source environments are typically large. Their multiple terabyte nature makes it currently quite hard to migrate the data to Office 365 as there are limits imposed by Microsoft on both the mailbox and personal archive sizes. To be able to migrate a large journal archive to Office 365, the product introduced a concept of a ‘Journal Splitting’.

There are two processes in migrating a journal archive to Office 365. This can be via Journal Splitting or a Journal Transformation. Below are the steps for Journal Splitting.

The general process for doing this is:

  1. Define the naming scheme for the target. It is suggested to prefix or postfix names, eg AL-<archivename> or <archivename>-Departed. This makes the data easier to find in the target after the migration has completed.
  2. Define the allowed number of rolling licenses.
  3. Decide on the type of ‘hold’ to place on the migrated data.
  4. Configure the maximum number of items allowed per child container, and maximum size allowed.
  5. Perform the mapping.

In the background what will happen is:
a. Provisioning

  1. A user account will be created according to the naming scheme.
  2. A Personal Archive will be created if it was required in the mapping.
  3. The mailbox/personal archive will be placed on the selected type of hold.
  4. A license will be assigned from the pool.
  5. The data from Office 365 about the ‘user’ will be synchronized.

b. Migration

  1. Data will be exported after the provisioning process is done.
  2. Data will be imported soon after it is exported, when a particular child container is full, as determined by the system settings, a new one will be created.

c. Stage 2

  1. The license which was assigned in order to be able to ingest data in to the mailbox (or Personal Archive) will be removed (usually as the last step) and returned to the pool so that another mapping can take that license and complete the provisioning step.

Transformation

Journal Transformation information can be found here.

To PST

This can be found here.

Print Friendly, PDF & Email