立即与支持人员聊天
与支持团队交流

Archive Shuttle 11.4 - Planning Guide

Automated lifting of throttling restrictions

Microsoft has made it possible to easily lift EWS throttling limits for up to 90 days during a migration. Archive Shuttle uses EWS to communicate with Office 365.

To request that Microsoft relax the throttling limits, follow these steps:

1.Go to the Help (?) section of the Microsoft 365 admin center.

2.Click the Need Help icon.

3.Enter “EWS throttling” as the search phrase.

4.Click Run tests when asked to check your environment. The tests check what EWS throttling applies to the tenant.

5.The support assistant checks the tenant settings and should normally conclude that EWS is throttled. You will then be offered the chance to update the settings to the tenant EWS policy to lift throttling for 30, 60, or 90 days.

6.Select the number of days you would like to adjust the policy for and then Update Settings.

7.After a short delay, the support assistant should confirm that the settings have been changed.

8.The new setting will be effective for the tenant in about 15 minutes and you should then be able to start migration transfers at full speed.

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.

Planning component installation

Where to set up Archive Shuttle components

The core Archive Shuttle Components include the following:

·Archive Shuttle Core Web Interface

·Archive Shuttle Core Web Services

·Archive Shuttle Core Service

It is recommended to install these components on the same server. For a production environment, this must be a dedicated server (physical or virtual). They can; however, be installed on separate servers.

See the chapter Hardware requirements for Archive Shuttle Core Server for more information about prerequisites.

Archive Shuttle also has the following Modules:

·Archive Shuttle Active Directory Collector Module

·Archive Shuttle Enterprise Vault Collector Module

·Archive Shuttle Enterprise Vault Export Module

·Archive Shuttle Enterprise Vault Import Module

·Archive Shuttle Enterprise Vault Provisioning Module

·Archive Shuttle Enterprise Vault Shortcut Processing Module

·Archive Shuttle Exchange Import Module

·Archive Shuttle Office 365 Module

·Archive Shuttle Native Format Import Module

·Archive Shuttle EAS Module

·Archive Shuttle Metalogix Module

·Archive Shuttle PST Export Module

·Archive Shuttle Dell Archive Manager Module

·Archive Shuttle SourceOne Module

Depending on the migration scenario, some or all of these modules have to be installed.

The following table provides a guideline on where to install these modules:

MODULE

NUMBER OF MODULES

NOTES

Active Directory Collector Module

One per Active Directory forest

Needs to be installed on a Server in the Active Directory Forest where data is to be collected from. The account that it is running under must have privileges to read Active Directory and its objects – a normal user account is sufficient.

Enterprise Vault Collector Module

Minimum: One per source Enterprise Vault environment

Recommended: One per Enterprise Vault Server hosting a Vault Store.

Note: If performing an EV to EV migration, this module is also needed in the target environment to gather site settings (HTTP/HTTPS) used when running ‘Fix Shortcuts’.

There needs to be at least one Enterprise Vault Collector Module installed in the source Enterprise Vault environment. It is recommended to install this component near the SQL Server that hosts the Vault Store databases. Care should be taken when additional Enterprise Vault Collector Modules are installed. Performance might not necessarily be increased, the limiting factor is usually the time it takes to retrieve data from the Vault Store databases.

Enterprise Vault Provisioning Module

One per source Enterprise Vault environment, and one per target Enterprise Vault environment.

There needs to be one Enterprise Vault Provisioning Module per Enterprise Vault environment, i.e. per Enterprise Vault Directory Database. This module uses EVPM. It is recommended to install this component on the least busy Enterprise Vault server.

Enterprise Vault Export Module

Minimum: One per source Enterprise Vault environment

Recommended: One per Enterprise Vault Server hosting a Vault Store.

There needs to be at least one Enterprise Vault Export Module installed in the source Enterprise Vault environment. It is recommended to install the Enterprise Vault Collector module on each Enterprise Vault server that hosts Vault Store partition data, in the source environment. This module requires the Enterprise Vault API. If this module is to be installed on a non-Enterprise Vault server, then the Enterprise Vault API Runtime needs to be installed.

Enterprise Vault Import Module

Note: This module is only required if the migration scenario includes migration to an Enterprise Vault environment.

Minimum: One per target Enterprise Vault environment.

Recommended: One per target Enterprise Vault Server hosting a Vault Store.

There needs to be at least one Enterprise Vault Import Module per target Enterprise Vault environment, i.e., Enterprise Vault Directory. It is recommended to install an Enterprise Vault Import Module on each Enterprise Vault Server where the Vault Store to import to is hosted. This module requires the Enterprise Vault API. If this module is to be installed on a non-Enterprise Vault server, then the Enterprise Vault API Runtime needs to be installed.

Shortcut Processing Module

Minimum: One per target environment.

There needs to be at least one Shortcut Processing Module per target environment.

This module must be installed on a Server with Microsoft Outlook 2007/2010/2013 (32 bit).

Note: An optional change in the System Configuration can change this module to use EWS rather than MAPI (however the installation of the module still requires Outlook)

Exchange Import Module

Note: This module is only required if the migration scenario includes migration to an Enterprise Vault environment.

Minimum: One per target Exchange environment.

There needs to be at least one Exchange Import Module per target Exchange environment. This module requires Microsoft Outlook to be installed. It is not supported to install the module on an Exchange Server. It is recommended to install this module on a dedicated physical or virtual machine.

To improve performance, multiple Exchange Import Modules can be installed. It is recommended to start with one module and add more modules (up to one per Exchange database) if required.

Office 365 Module

One per environment

There needs to be an Office 365 module in order to migrate containers to Office 365. This module collects data about Office 365 mailboxes, as well as migrating data into the target container and post-processing the ingested data to remove Enterprise Vault shortcuts and pending items.

The module connects to Office 365 using the credentials specified in the Credential Editor, which is installed by the module.

Native Format Import Module

One per environment

One Native Format Import Module is required in order to take extracted data and create PST files. This module will split PST files at predetermined sizes and store them with a name defined by policy into a UNC accessible staging area which is defined per link.

This module must be installed on a Server with Microsoft Outlook 2007/2010/2013 (32 bit).

Proofpoint Module

One per environment

One Proofpoint Module is required in order to take extracted data and prepare/construct the data required for Proofpoint ingestion.

This module must be installed on a Server with Microsoft Outlook 64-bit. This module also requires a 64-bit JRE. Additional information is available in the Installation Overview.

EAS Zantaz Module

One per environment

One EAS Module is required on a machine which can communicate with an EASIIS Server which has access to all the required Document Repositories.

Metalogix

One per environment

One Metalogix Module is required on a machine which can communicate with an Metalogix Server which has access to all the required Document Repositories.

PST Export Module

One per environment

One PST Export Module is required, and can process a number of UNC paths to extract data from PST files which are located there.

Dell Archive Manager Module

One per environment

One Dell Archive Manager module is required for the source environment.

SourceOne Module

One per environment

One SourceOne module is required for the source environment.

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级