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.
NOTE: This same configuration can be used to migrate to Exchange 2013.
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 its 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.
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.
Another option is to use a bridgehead server as shown below:
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback 利用規約 プライバシー