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

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

Dell Archive Manager as a Source

Stage 1 - Synch

MigrationWorkflow19

The first task which has to be performed is the discovery of archives in DAM. One or more of these archives are mapped and enabled for migration, Archive Shuttle Core sends a command to collect all needed metadata information from each archive. The results are reported back to Archive ShuttleCore to allow item level tracking and auditing.

The DAM module and chosen target environment import module then start to process the items from the archives. This runs continuously in the background until the administrator initiates a ‘Switch’ (stage 2) for the archive.

Stage 2 - Switch

DAM to Exchange or Office 365

MigrationWorkflow20

DAM to PST

MigrationWorkflow21

 

Additional details on Dell Archive Manager/Quest Archive Manager migrations

Introduction

This section explains what the requirements are for migrating from Dell Archive Manager (DAM)/Quest Archive Manager (QAM) to a target environment, 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 DAM/QAM module should be installed on an appropriate server.

Modules installed on target

The appropriate modules should be installed on each appropriate target server involved in the 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.

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.

Configure Dell Archive Manager Environment

Dell Archive Manager Environment

Add a new Dell Archive Manager environment, specifying the following:

·Module to associate with this link

·Display name to use for this link

·SQL Server Name

·SQL Database Name

Finally indicate that you want to ‘Create Item Database’, an ‘Enable Archive Collection’. The ‘Link SQL Server’ should be set to the server where the Archive ShuttleItem databases are hosted.

Assign Post Processing module to DAM Link

Links

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

Map Modules to Target Link

Links

Ensure that the link for the migration target is added, and modules associated with it.

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.

Map one or more Containers

Bulk Mapping

One or more containers can now be mapped and migration can begin. It is often easiest to use a filter on the bulk mapping screen to show only DAM as a source.

General Considerations

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

·Ensure Shortcut Processing is configured to use EWS.

SourceOne as a Source

Stage 1 - Synch

MigrationWorkflow22

The first task which has to be performed is the discovery of archives in SourceOne. One or more of these archives are mapped and enabled for migration, Archive Shuttle Core sends a command to collect all needed metadata information from each archive. The results are reported back to Archive ShuttleCore to allow item level tracking and auditing.

The SourceOne module and chosen target environment import module then start to process the items from the archives. This runs continuously in the background until the administrator initiates a ‘Switch’ (stage 2) for the archive.

Stage 2 - Switch

SourceOne to Exchange or Office 365

MigrationWorkflow23

SourceOne to PST

MigrationWorkflow24

 

Additional details on SourceOne/EmailXtender migrations

This section explains the requirements for migrating from SourceOne or EmailXtender to another environment, 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 SourceOne module should be installed on an appropriate source server.

Modules installed on target

The appropriate modules should be installed on each appropriate target server involved in the 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.

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.

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 a schedule for them defined if necessary. It is important to verify that none of the modules have a red background (indicating that the 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.

Note: Configuration of EmailXtender is done in the same way as SourceOne.

Configure SourceOne Environment

SourceOne Environment

Add a new SourceOne environment, specifying the following:

·Module to associate with this link

·Display name to use for this link

·SourceOne Basepaths (These are the share paths for each archive folder. Multiple paths should be semicolon separated.)

·SourceOne/EMX SQL server

A Link Database will be created for this environment. It is possible to override the SQL Server and instance, if required.

Enable Organization

SourceOne Environment

The module will scan for organizations and present them in a list. The required organizations should be enabled so that the module can scan for archives.

Map Modules to Target Link

Links

Ensure that the link for the migration target is added, and modules associated with it.

Map Modules to Source Link

Links

Ensure that the source links have a Shortcut Processing module assigned to them. This module will scan mailboxes to find shortcuts. This is required before the import can begin.

Add Staging Area

Links

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

Configure Folder-less folder name

System Configuration

SourceOne does not maintain folder information for items. Therefore, a folder will be created to migrate items into. The name of this folder can be specified under ‘Folder name for folder-less items’ on the General System Settings Page.

The module scans for shortcuts in a mailbox and any items which have a shortcut will be migrated to the current folder where that shortcut resides.

Map one or more containers

Bulk Mapping

One or more containers can now be mapped and migration can begin. It is often easiest to use a filter on the bulk mapping screen to show only SourceOne as a source.

General Considerations

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

·If you need to migrate the primary S1 archive into a primary mailbox, and a secondary S1 archive into a personal archive (in Exchange or Office 365), then two mappings will be required.

·It is recommended to add the following index to the SQL databases relating to S1. It will improve the item collection process:CREATE NONCLUSTERED INDEX IX_RouteEmailId ON [dbo].[Route] ([EmailId])INCLUDE ([MessageID], [RouteMask], [PartitionId]

·It is recommended to add the following index to the SQL databases relating to EmailXtender. It will improve the item collection process:CREATE NONCLUSTERED INDEX IX_RouteEmailId ON [dbo].[Route] ([EmailId])INCLUDE ([MD5HashKey],[TimeStamp])

·Disabling source archives is currently not available as part of a Workflow Policy and will need to be done manually post migration.

The following filters are not supported:

·ArchivedDate

·RetentionCategory

·HasLegalHold

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択