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

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

Planning for Migrations to PST

In order to perform a migration of Enterprise Vault data to PST, a PST File Name policy can be defined. The file name policy is defined with tokens, as shown in the table below:

Token

Description

*username*

Username of the owning user (sAMAccount Name)

*firstname*

First name of the owning user

*lastname*

Last name of the owning user

*fullname*

Full name of the owning user

*email*

E-mail address of the owning user

*upn*

User principal name of the owning user

*pstid*

ID of the PST file; continuous integer over all PST files

*pstnumber*

Number of PST file; continuous integer per user

*archivename*

Name of the archive

*archiveID*

The Enterprise Vault Archive ID associated with the archive

The tokens can be used to construct filenames and paths.

Planning for Migrations to UNC

If you plan to migrate data to UNC, install the Storage Import Module before beginning.

You’ll use the Storage Import and Storage Provider target when configuring the workflow policy, mapping wizard, etc.

While setting up the migration, use the Storage Import Module tab of the System Configuration page to, for example, set item/archive parallelism, set up conversion of MSG to EML, fail items permanently on specified errors, etc.

Migrating Leavers Data and Journal Archives

When performing a migration with Archive Shuttle a question which arises and needs to be addressed is whether to migrate leavers data if journal migration is being performed.

Journal archives contain messages from everyone inside the organization, and all inbound and outbound communications. It has messages from everyone in the company now, and everyone that left the company over the preceding years.  The tricky part is determining when journal archiving was turned on. That can affect whether or not you need to migrate just the journal archive, or the journal archive and leavers data.

Let’s look at a couple of examples.

Example 1

Let’s say Bob works for the organization now, and has been working for the organization for 3 years.  Jane doesn’t work for the company any more, she joined about 18 months ago and left 3 months ago.

Journal archiving has been in place for 5 years.

In this example, the data which would be in Bob’s archive will be in the journal archive. The data which would be in Jane’s ‘leaver’ archive will also be in the journal archive. Therefore, the organization could make the decision that they do not need to migrate that leaver archive.

Example 2

Let’s say Sarah has been working for the company for 6 months.  Let’s say David is a leaver, he left 3 months ago, and has been working for the company for 7 years.

Journal archiving has been in place for 5 years.

In this example the data in Sarah’s archive will be in the journal archive, but not all of the data in David’s ‘leaver’ archive will be in the journal archive. Therefore, the organization could make the decision that they do need to migrate David’s data as well as the journal archive.

This comparison would need to be done across all leaver archives before an overall decision could be reached, and ultimately it’s the organizations decision to migrate the data or not.

Naming Conventions for Leaver Archives

An important consideration when migrating leaver archives with Archive Shuttle is the naming convention (or naming standard) to use for the mailboxes which Archive Shuttle will create.

NCFLA1

The above screenshot shows where the configuration / selection is made in Archive Shuttle.

There are many tokens that can be used to help form the name such as:

·Archive ID

·Archive Name

·Container Mapping iD, and more.

 

It's important to remember that there should not be any overlap or collision with existing names in the target.

In selecting ‘archive name’, problems will be encountered when someone exists and a leaver has the same name. For example, if there is already an active mailbox owned by John Smith, and Archive Shuttle tries to process a lever called John Smith.

Ultimately, the naming scheme should be unique. Often the name will have a prefix; they will all appear in the directory in the same sort of place (compared with postfixing a token). Here is an example:

AL-*archivename*

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択