Archive Shuttle 11.0 - Installation Guide

Enterprise Vault to Enterprise Vault - Cross forest/org/geography

The following diagram shows a slightly more complex migration scenario that also involves more data than the first scenario.

In this example, the dotted red line shows the possibility that the data is manually shipped between the two environments. There are several ways that this can be achieved, for example:

Physically ship the data on tape or other media between the environments. The import modules used in the target environment then need to be configured to point to the location where the copy is mounted.

Copy the data through restricted ports or firewalls. Again, the import modules used in the target environment need to be configured to point to the location where the copy is mounted.

NFS and CIFS in tandem. With this approach, the Staging Area needs to be shared via a generic username/password using NFS and again shared as a normal CIFS share. If appropriate to the environment, firewall ports for NFS then need to be opened to allow the export module to write to the NFS share. For this reason, this approach normally means that the Staging Area is located on the target environment. This is shown in the diagram below.

Note that the same approach can be used for migration to other target environments.

Reference:

http://technet.microsoft.com/en-us/library/dd758767%28v=ws.10%29.aspx

http://blogs.technet.com/b/filecab/archive/2012/09/14/server-for-nfs-in-windows-server-2012.aspx

Enterprise Vault to Exchange 2010

In the following diagram, Archive Shuttle is being used to migrate data from Enterprise Vault to Exchange 2010 (either primary mailbox or secondary mailbox/personal archive). The data involved is not particularly large; therefore, many of the modules are installed on regular, already-deployed, servers. The Archive Shuttle application server in many ways is operating as a plug-and-play appliance and also houses the data location used for export and import of the data involved in the migration.

Enterprise Vault to Office 365

In the following diagram, Archive Shuttle is being used to migrate data from Enterprise Vault to Office 365. The communication to Office 365 allows mapping of Enterprise Vault archives to mailboxes in the cloud. The migration can be performed to either primary mailboxes or Personal Archives.

The example below illustrates a more complex environment where the environment is split across two geographies US and Europe. Each of those geographies has it’s own internet connection, and there is a corporate wide-area network joining the locations also.

In this situation, one Core can still be deployed. The modules will receive commands and transmit metadata over the corporate network. The export/import is done within each geography.

Enterprise Vault to Office 365 using ArchiveShuttle.cloud

In the following diagram, Archive Shuttle.cloud is being used to migrate data from Enterprise Vault to Office 365 mailboxes. This new option with Archive Shuttle gives a cloud-based instance of Archive Shuttle (and the necessary SQL databases). This leaves customers to simply install the modules required to perform the migration and to provide a Network Share to house the Staging Area.

If you cannot install the modules directly onto the Enterprise Vault servers, then you can install all modules on the bridgehead server or a separate bridgehead server exclusively used for the extraction of data.