Archive Shuttle 11.4 - Installation Guide

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:

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:

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.

Using a proxy

Configuring the Archive Shuttle modules to use a web proxy

When using Archive Shuttle Cloud it may be necessary to configure the Archive Shuttle modules to communicate with the Archive Shuttle via a web proxy. Each of the module .exe.config files can be modified as shown below:

<startup><supportedRuntime version="v2.0.50727"/></startup>

 <system.net>

  <defaultProxy enabled="true" useDefaultCredentials="true">

              <proxy  proxyaddress="http://proxy:8080" />

  </defaultProxy>

   <connectionManagement>

     <add address="*" maxconnection="100"/>

   </connectionManagement>

 </system.net>

You may need to bypass some of the addresses, and therefore it needs to add the addresses you want to bypass into the config file:

<system.net>

   <defaultProxy enabled="true">

    <bypasslist>

        <add address="[a-z]+\.contoso\.com" />

        <add address="192\.168\..*" />

    </bypasslist>

    <proxy bypassonlocal="True" proxyaddress="http://proxy:8080"/>

  </defaultProxy>

 </system.net>