Journal Transformation detail grid
The Journal Transformation detail grid on the Stage 1 page of the user interface contains many details relating to the item level detail surrounding a mapping which is in migration.
Here is an example of how the screen might look:
As shown in the screenshot, it is possible to perform grouping to aid with management of the migration.
In addition the filtering possibilities have the ability to enter free text:
Journal 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- or -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:
1. Provisioning
a.A user account will be created according to the naming scheme.
b.A Personal Archive will be created if it was required in the mapping.
c.The mailbox/personal archive will be placed on the selected type of hold.
d.A license will be assigned from the pool.
e.The data from Office 365 about the user will be synchronized.
2. Migration
a.Data will be exported after the provisioning process is done.
b.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.
3. Stage 2
a.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 in the Quadrotech Archive Shuttle Migration Guide.
Which Office 365 license to use for leavers or virtual journal
Archive Shuttle has ability to provision mailbox in Office 365 and set flags like Legal Hold, Hide from GAL, etc for Leavers, or Virtual Journal type of migrations.
There are several differences between each Office 365 Plan/License options. This can be checked here or here.
The biggest difference from the migration perspective is the mailbox size/storage limits as the data will be migrated there:
|
Feature |
Microsoft 365 Business Basic and Standard |
Microsoft 365 Business Premium |
Microsoft 365 Enterprise E3/E5 |
Office 365 Enterprise E1 |
Office 365 Enterprise E3/E5 |
Office 365 Enterprise F3 |
|---|---|---|---|---|---|---|
|
User mailboxes |
50 GB |
50 GB |
100 GB |
50 GB |
100 GB |
2 GB |
|
Archive mailboxes |
50 GB |
1.5 TB |
1.5 TB |
50 GB |
1.5 TB1 |
Not available |
|
Shared mailboxes |
50 GB |
50 GB |
50/100 GB |
50 GB2 |
50/100 GB |
50 GB |
|
Resource mailboxes |
50 GB |
50 GB3 |
50 GB |
50 GB |
50 GB |
50 GB3 |
|
Public folder mailboxes |
100 GB |
100 GB |
100 GB |
100 GB |
100 GB |
100 GB |
|
Group mailboxes |
50 GB |
50 GB |
50 GB |
50 GB |
50 GB |
50 GB |
Click here for more information on storage limits.
Therefore, Archive Shuttle recommends to use Enterprise E3 or E5 licenses for migration as Leavers. If the mailboxes will not exceed 50GB, use an E1 license.
Enterprise E1 and all Microsoft 365 Business licenses include Exchange Plan 1 licenses. Enterprise E3 and E5 licenses include Exchange Plan 2 licenses. Click here for more information.
|
|
NOTEs: ·Use of an E1 license does not include data loss protection. Microsoft recommends to use an additional Exchange Online archiving service. For more information, click here. You may also need to confer with Microsoft to determine whether the terms of your licensing agreement are impacted by the legal hold feature. ·Review this associated article. ·Archive Shuttle also supports the government equivalent of each of these licenses mentioned. |
Suggested values for splitting journal data
This article gives an indication of some suggestions relating to splitting of data when migrating with Archive Shuttle.
Virtual Journal Total Mailbox Item Count Limit
900,000 items
Virtual Journal Total Mailbox Item Size Limit (MB)
80 Gb, this way it is lower than the normal size allowed for a personal archive
Journal Split Base Folder Name
This is a customer/migration dependent, or can be left at the default
Journal Split Threshold
100,000 items, this way if it is ever necessary to open a mailbox it wont cause too many problems if using Outlook.