サポートと今すぐチャット
サポートとのチャット

Quadrotech Archive Shuttle 10.3 - Planning Guide

Introduction Architecture Modules Migration Workflow Planning Component Installation Planning for the Archive Shuttle Databases Planning Export/Import Storage Permissions/Access requirements for complex deployments Sizing the PST Output Location How to change Folder Translations Preserving the Chain of Custody Planning for Migrations Migrating Leavers Data and Journal Archives Journal Transformation Migration Tuning a Migration About Us Contacting Quest

Additional details on Enterprise Vault to Exchange Mailboxes migrations

Introduction

This section explains what the requirements are for an Enterprise Vault (EV) to Exchange migration, and then covers the basic steps that should be followed to start such a migration.

Requirements

The following is a list of requirements.

Requirement

Description

Modules installed on source

The EV-type modules should be installed on each appropriate source Enterprise Vault server involved in the migration. The EV import module is not required on these machines.

Modules installed on appropriate bridgehead to reach target

Exchange and Post Processing modules are the two which are primarily needed to work with this type of migration.

AD Collector module installed

An AD Collector module should be installed so that it can collect user-level information for the migration project.

Staging Area created

One or more staging areas should be setup, of an appropriate size and should be excluded from virus scanners.

Ingest accounts configured for Application Impersonation

5 accounts should be configured with Application Impersonation rights, and those accounts should be added to the credentials editor on the machine running the Exchange ingest module.

Workflows reviewed

The Stage 2 workflows should be reviewed, and if necessary, customized to meet the needs of the project.

Apply appropriate failed item threshold

It is best practice to find an appropriate failed item threshold for the project/customer and apply that at the links level. This way all mappings which are created will inherit this value.

 

Basic Steps

The following are the basic steps to start this type of migration.

Step

Screen

Description

Enable Modules

Modules

All Archive Shuttle modules must be enabled, and optionally a schedule for them defined. It is important to verify that none of the modules have a red background (this indicates that Archive Shuttle Core has not had contact with the module) and that the module versions are as expected.

Enable Domains

Active Directory

Select and enable one or more domains for synchronization.

Add EV Environment

EV Environment

Add the Enterprise Vault source environment.

Add Source Links

Links

Configure all appropriate source links. Select the links, and then click on ‘Map Modules’, create the item database(s) and enable archive gathering. Ensure there is no import module specified on the links as this may impact the process later on.

Add Target Links

Links

Add all appropriate target links. An ingest and post-processing module should be associated with each possible target Exchange Database.

Add Staging Area

Links

Ensure that the Default Staging Area is configured correctly. Depending on the migration, the free space, and the number of vault stores being used as the source for the migration, the ‘high water mark’ can be adjusted upwards.

Configure Folder-Less Item Handling

System Configuration

Many versions of Enterprise Vault allow archiving of items in a folder-less area called the Top Of Information Store. On the System Configuration, enter a folder name to be used for placing the items in the target archive.

Ensure AIP/EWS is configured correctly

System Configuration

Ensure that the migration providers are listed in the required order and that the AutoDiscoverURL is specified if required. The account which is to be used for ingest needs to have Application Impersonation rights. This article will help with configuring that.

Consider disabling reminders for appointments in the past

System Configuration > Exchange Import Module

Consider enabling the option to ‘Disable reminders for appointments in the past’ this will prevent pop-ups appearing from Outlook on end-user machines when old appointments are processed.

Map one or more Containers

Map Containers

One or more containers can now be mapped and migration can begin.

General Considerations

The following general considerations should be taken into account for this type of migration:

·When migrating from a pre EV 10.0.3 system extraction of data may be slower than expected if Enterprise Vault Collections have been used. Access to the data inside the CAB file is single threaded. This issue does not exist in Enterprise Vault 10.0.3 and later.

·EVPM may have difficulty in connecting to, and processing, mailboxes which are homed on Exchange 2013. This knowledge base article may help.

·EVPM may need to have the DS Server registry key set. This knowledge base article may help.

 

Enterprise Vault to Office 365

Stage 1 – Synch

MigrationWorkflow5

As soon as a user is enabled for migration, the synch process-flow shown above starts.

Archive Shuttle Core sends a command to collect all needed metadata information such as the number of items, size, and Enterprise Vault transaction ID’s for the archive of the user. The results are reported back to Archive Shuttle Core to allow item level tracking and auditing.

The Enterprise Vault Export and Office 365 module then begin to work. This runs continuously in the background until the administrator initiates a “Switch” (stage 2).

Stage 2 - Switch

MigrationWorkflow6

After the administrator has initiated a “Switch” (stage 2) to the target environment, the Metadata Collector determines the gap between the source archive and the last imported item. Archive Shuttle then synchronizes the difference one last time to the target mailbox.

The last step is to ‘Zap’ the mailbox to remove Enterprise Vault settings, cleanup shortcuts in the source mailbox by deleting them, and change any pending-archive items back to normal items.

Additional details on Enterprise Vault to Office 365 Mailboxes migration

Introduction

This section explains what the requirements are for an Enterprise Vault (EV) to Office 365 migration, and then covers the basic steps that should be followed to start such a migration.

Requirements

The following is a list of requirements.

Requirement

Description

Modules installed on source

The EV-type modules should be installed on each appropriate source Enterprise Vault server involved in the migration. The EV import module is not required on these machines.

Modules installed on appropriate bridgehead to reach target

Office 365 and Post Processing modules are the two which are primarily needed to work with this type of migration.

AD Collector module installed

An AD Collector module should be installed so that it can collect user-level information for the migration project.

Staging Area created

One or more staging areas should be setup, of an appropriate size and should be excluded from virus scanners.

Ingest accounts configured for Application Impersonation

5 accounts should be configured with Application Impersonation rights, and those accounts should be added to the credentials editor on the machine running the Office 365 module. One account should also be configured as a Global Administrator in Office 365, and be marked as that in the credentials editor.

Workflows reviewed

The Stage 2 workflows should be reviewed, and if necessary, customized to meet the needs of the project.

Apply appropriate failed item threshold

It is best practice to find an appropriate failed item threshold for the project/customer and apply that at the links level. This way all mappings which are created will inherit this value.

 

Basic Steps

The following are the basic steps to start this type of migration.

Step

Screen

Description

Enable Modules

Modules

All Archive Shuttle modules must be enabled, and optionally a schedule for them defined. It is important to verify that none of the modules have a red background (this indicates that Archive Shuttle Core has not had contact with the module) and that the module versions are as expected.

Enable Domains

Active Directory

Select and enable one or more domains for synchronization.

Add EV Environment

EV Environment

Add the Enterprise Vault source environment.

Add Source Links

Links

Ensure that the Default Staging Area is configured correctly. Depending on the migration, the free space, and the number of vault stores being used as the source for the migration, the ‘high water mark’ can be adjusted upwards.

Add Staging Area

Links

Select the newly created link, and map a Shortcut Process Module to it.

Configure Folder-Less Item Handling

System Configuration

Many versions of Enterprise Vault allow archiving of items in a folder-less area called the Top Of Information Store. On the System Configuration, enter a folder name to be used for placing the items in the target archive.

Set Office 365 Credentials


There are two options:

Option 1: Service account user name/password

Screen: External Application installed by the O365 module

Run the Archive Shuttle Office 365 Module Credentials Editor and supply multiple service account credentials. When running the credentials editor, it is important to make sure the account that is logged in is the account used to run the Office 365 service.

We recommend that you add at least as many service accounts as the number of mailboxes that will be handled in parallel (Configured on the System Configuration screen).

Option 2: OAuth authentication

Screen: Office 365 module

Run the Archive Shuttle Office365 Module Credentials Editor and add OAuth credentials. Then test the connection. Then, from the Office 365 Module, select the Use modern authentication (OAuth) option.

Update Shortcut Processing Module Configuration

System Configuration > Shortcut Processing

Update the settings so that ‘Use EWS for Processing’ is enabled.

Consider disabling reminders for appointments in the past

System Configuration > Office 365 Module

Consider enabling the option to ‘Disable reminders for appointments in the past’.

Map one or more Containers

Map Containers

One or more containers can now be mapped and migration started.

General Considerations

The following general considerations should be taken into account for this type of migration:

·A call should be logged with Microsoft to get the throttling limits raised for the duration of the migration, otherwise ingest performance will be reduced.

·When migrating from a pre EV10.0.3 system extraction of data may be slower than expected if Enterprise Vault Collections have been used. Access to the data inside the CAB file is single threaded. This issue does not exist in Enterprise Vault 10.0.3 and later.

·Different flavors of Office 365 license have different size limits, as described here.  It is advised to run SQL Queries on the source environment in order to determine if any archives are likely to have.

·Many large items- Many archives have more data in them than is allowed by the Office license.

·It is advised to ensure a high level of Mailbox Parallelism and a low level of item/batch parallelism. This gives least chance to get to throttling limits.

·It is advised to have 5 accounts configured with application impersonation rights in Office 365. This gives least chance to reach throttling limits. Go to the Quadrotech Archive Shuttle Installation Guide for more on application impersonation rights.

Mapping retention categories from Enterprise Vault to Office 365 retention tags

In Archive Shuttle 9.8 and later you can collect retention tags from Office 365 and map/apply them in a migration where Enterprise Vault is used as the source, and Office 365 is used as a target.

By default the collection of retention tags is disabled. If you want to make use of this new feature, then the option in System Settings needs to be enabled:

O365RET1

When this is enabled, retention tags will be collected by the Office 365 module.

Retention category mapping can then be performed. The user interface has been extended to allow the mapping between Enterprise Vault retention category and Office 365 retention tag.

O365RET2

During a migration, items will be ingested into Office and two additional attributes will be set/populated:

·PR_POLICY_TAG (GUID of the retention tag)

·PR_RETENTION_PERIOD (Age limit for retention)

PowerShell commands have also been extended to allow for this mapping to process to be performed.

info

NOTE: If an item is exported, and there is no retention mapping for it, the item will not ingest.

There is also the ability to bind Enterprise Vault retention categories with the Office 365 Compliance Retention labels. When the feature is active, PR_POLICY_TAG and PR_RETENTION_PERIOD properties are put into messages properties. This works only with AIP as an ingest protocol. The validation on the existing retention mapping is processed; if this doesn’t exist, the ingest is not processed (items are exported only). In the case when Enterprise Vault archive contains items with more retention categories (in case when PST file was imported into archive under another RC as is origin of the EV archive) and only one 1 RC mapping exists, then these items will ingested and stamped with the O365 Compliance Retention label.

This is reflected in the UI below:

O365RET3

 

EV Retention Mappings screen:

O365RET4

O365RET5

Mapping health page has been updated to handle with this missing retention mapping for Office 365.

O365RET6

Archive Shuttle collects ALL retention labels, published or unpublished.

·Published labels are visible via Outlook > Assign Policy.

·Unpublished are hidden for users via Outlook.

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択