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

Quadrotech Archive Shuttle 10.3 - Installation Guide

Configuring Access to Office 365 Through a Proxy Server

If the migration environment needs to use a web proxy to access HTTP or HTTPS sites on the internet, then the Office 365 module needs to be configured to also route traffic that way.

1.Log in to the server or workstation where the Office 365 Module is currently deployed using the account that is used to run the Archive ShuttleOffice 365 Service.

2.Browse to the folder where the module is installed, and locate the file ‘ArchiveShuttle.Module.Office365.exe.config’ and open it in a text edit.

3.Remove the <!—and –> from the line containing the ‘defaultProxy’ and set the value to be one of:

IEConfig

AutoDetect

WinHttpConfig

NoProxyServer

4.Save and close the file.

Restart the Office 365 Module service using Windows Service Control Manager.

Configuring Modules to Use HOTS

HOTS is a feature with Archive Shuttle which allows for less bandwidth usage for migrations to Office 365 by combining a highly-optimised transfer system with storage of extracted data taking place in Microsoft Azure. The following diagram presents an overview of HOTS:

HOTS

Requirements

For migrations from legacy archives to Office 365 using HOTS the following needs to be considered:

·Using HOTS is supported for all currently supported sources, when migrating to Office 365 mailboxes or Personal Archives.

·More CPU uses might be needed on the source environment in order to create the HOTS-format data

·An Azure Storage Account must be configured and used for storing the extracted data

·All export and import modules must have been configured with the connection string to the Azure Storage Account

·A bridgehead server running the ingest and shortcut processing module should be deployed in Azure to facilitate the ingestion of the data from the Azure Storage Account.

Bridgehead Server

The bridgehead server in Azure should consist of a virtual machine with the following specification:

info

NOTE: Microsoft Azure machine classes change frequently so a specific machine class is not specified here.

Component

Configuration

Processors (cores)

Minimum 4, Recommended 8

CPU Speed

2 GHz

Memory

Minimum 16 GB, Recommended 32 GB

Hard disk

Minimum 2 GB of free space

PowerShell Execution Module

This module is responsible for executing PowerShell commands in the Stage 2 Workflow for a mapping. It is recommended to have one of these installed in the environment.

It is not necessary to associate this module with a particular link, that process is done automatically, and is controlled by the Core.

info

NOTE: This module requires .Net Framework 4.5.2.

Ports Used by Archive Shuttle

The following table shows the network communication ports used by Archive Shuttle. These ports are provided for reference for the situation where a firewall exists between the source and target environments in the archive migration.

SOURCE

Destination

Port(s)

Description

Module Servers

Archive Shuttle Server

TCP 80 (HTTP)

TCP 443 (HTTPS)

HTTP/S Communication from Modules to Archive Shuttle Servers (*1)

Export / Import Module Servers

Storage Servers (CIFS Shares)

TCP 445 (CIFS)

Access to CIFS Shares (*2)

Archive Shuttle Server

SQL Server

TCP 1433 (MSSQL)

Access to Microsoft SQL Server hosting the Archive Shuttle databases

Archive Shuttle Server

DNS Servers

UDP 53 (DNS)

Access to DNS for Windows

Archive Shuttle Server

Domain Controllers

TCP 88 (Kerberos)

TCP 445 (CIFS)

Access to Domain Controllers for Windows

Enterprise Vault Module Servers

Enterprise Vault Servers

–

Please see your Enterprise Vault documentation on what ports are needed for the Enterprise Vault API to talk to Enterprise Vault

Exchange Module Servers

Exchange Servers

–

Please see your Microsoft Exchange documentation on what ports are needed to talk to Microsoft Exchange (MAPI/EWS)

Office 365 Module Servers

Office 365

TCP 443 (HTTPS)

HTTPS communication from Archive Shuttle Office 365 Module to Office 365

SourceOne/EMX Module

SQL Server

TCP 1433 (MSSQL)

Access to Microsoft SQL Server hosting the SourceOne/EMX databases

Zantas EAS Module

SQL Server

TCP 1433 (MSSQL)

Access to the Microsoft SQL Server hosting the EAS database

Zantas EAS Module

Zantas App Server

TCP 443 (HTTPS)

TCP 80 (HTTP)

HTTP(S) communication with the Zantas EAS application server

Metalogix Archive Manager Module

SQL Server

TCP 1433 (MSSQL)

Access to the Microsoft SQL Server hosting the Metalogix Archive Manager database

Metalogix Archive Manager Module

Metalogix App Server

TCP 443 (HTTPS)

TCP 80 (HTTP)

HTTP(S) communication with the Metalogix Archive Manager application server

(*1) If the Archive Shuttle core is configured to use HTTPS, then port 443 needs to be open on any firewalls. If the core is configured to use HTTP, then port 80 needs to be open on any firewalls.

(*2) Please note that this is also supported through SMB 2 and SMB 3.

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択