This is an overview page of all the Enterprise Vault environments that are needed for the migration project. New Enterprise Vault Directories can be added, and Archive Shuttle collects information about this Enterprise Vault directory through the assigned Archive Shuttle Enterprise Vault Collector module.
For every Enterprise Vault Directory, the table lists the following information:
·Vault Store Name
·Number of Archive in this Vault Store
·Total Item Count in this Vault Store
·Total Item Size in this Vault Store
·Total Shortcut Count in the archives associated mailbox
·Total Legal Hold Count
·Archive Gathering Enabled
·Backup Mode enabled
NOTE: The data values will only be shown on screen when Archive Gathering has been enabled, and an EV Collector module has been linked. (See below)
Actions to be performed on the EV Environment page
·Add EV Directory: Adds an Enterprise Vault Directory to Archive Shuttle. The following information is needed in order to perform this action:
·Module to associate: Archive Shuttle Enterprise Vault Collector module which should be responsible for collecting information about this Enterprise Vault Directory
·Display Name: Friendly name for this Enterprise Vault Directory. This is only a display name and can be used to identify this Enterprise Vault Directory
·EV SQL Server: SQL Server name / instance where this Enterprise Vault Directory hosts its Directory database. This can be a hostname, a Fully Qualified Domain Name, an IP Address or all of the previous with a SQL Named Instance provided:
·EV SQL Database Name: Database name. Defaults to EnterpriseVaultDirectory. This entry is for display purposes only.
·Sync all EV Environments: Queues an update request for all Enterprise Vault Directories by their respective Archive Shuttle Enterprise Vault Collector Modules.
·Sync Active Directory: Queues an update request for all enabled Active Directory Domains by their respective Archive Shuttle Active Directory Collector modules.
·Enable: Enable Archive Gathering for the selected Vault Store(s)
·Disable: Disable Archive Gathering for the selected Vault Store(s)
·Run Now: Queue an Archive Gathering request for the selected Vault Store(s)
·Refresh: Refresh the information on the displayed EV Environment table
This page shows all Enterprise Vault Retention Categories that have been mapped, and allows an administrator to add or delete existing mappings.
A Retention Category mapping is necessary in cross-Enterprise Vault Site/Directory migration scenarios. This is required so that Archive Shuttle knows which Retention Category it should apply to the target item, based on the retention category of the source item.
A Retention Category mapping can also be used to change the Retention Category in intra-Enterprise Vault Site/Directory migration scenarios. This is useful if it is required to consolidate Retention Categories.
NOTE: Without Retention Category mappings in place, Archive Shuttle will export data from Enterprise Vault, but not import any items into Enterprise Vault.
Actions to be performed on the EV Retention Mappings page
Create Mapping: Create a new Retention Category Mapping. The following information is required, and can be selected from drop-down lists when creating the mapping:
·Source Retention Category
·Target Retention Category
Create Multiple Mappings: This can be used to add multiple retention category mappings at one time.
Add Intrasite Migration Mappings: This can be used in intra-Enterprise Vault Site scenarios. It maps every Retention Category to itself, thus keeping the existing Retention Category during migration.
Delete Mapping: Deletes the selected Retention Category mapping(s)
Edit Mapping: Allows a mapping to be modified.
Refresh: Refresh the information on the displayed Retention Category table
NOTE: Unmapped retention categories can be seen on the System Health page.
The page shows all Links in the environment (e.g., Vault Stores, Exchange Mailbox databases) that were discovered through the Active Directory Collector Modules, and the Enterprise Vault Collector Modules. It also shows links that were created manually (e.g. Native Format Links, and Office 365 links).
For each link, you can see the following information:
Type: Enterprise Vault, Exchange, Office 365, or PST.
Name: Name of the link. This is usually the Vault Store name or the Exchange database name. For links that were created manually it will be the name that was chosen.
Computer Name: The name of the server hosting the link. This is usually the Enterprise Vault server or the Exchange server.
AS DB: If an Archive Shuttle Item database has been created for this Link. A green and white check mark will be displayed if the database exists.
Failed Item Threshold: The failed item threshold that has been configured for this link.
Number of Containers: Container Count for this Link
Associated Modules: This grid will show the module to link mappings that have been defined.
Staging Area Path: Path used for export or import for this link
NOTE: The Archive Shuttle Active Directory Collector, and Enterprise Vault Collector may have already scanned Active Directory and pre-populated some of the information on this page.
Actions to be performed on the Links page
Create PST Link: Provides the ability to create a new PST link. It is possible to choose a name for the link, and to specify the PST Output Path where final PST files will be placed
Create O365 Link: Provides the ability to create a new Office 365 link. It is possible to choose a name for the link.
Create Proofpoint Link: Provides the ability to create a new Proofpoint link. It is possible to choose a name for the link, and to specify the output folder.
Create Database: Create an Item database for the selected Link.
NOTE: The source Link needs to be of type Enterprise Vault. An Item database should be created for each Enterprise Vault source Vault Store.
You need to provide the following information:
Link SQL Server: The SQL Server name / instance where you want to create the Link database. This can be a hostname, a Fully Qualified Domain Name, an IP Address or all of the previous with a SQL Named Instance provided.
·SQL Database Name
Default: ArchiveShuttleItem_. Read only.
Map Modules: Provides the ability to allocate modules to this link.
NOTE: Multiple links can be selected and modules allocated to them.
Use Local Modules: Attempts to automatically map modules to this link based on the modules that may be already deployed to the servers involved. For example, if the Archive Shuttle EV Collector Module, Export Module and Provisioning Module have already been deployed on a particular Enterprise Vault server when Auto Map Modules is selected for a vault store that resides on this server, those three modules will be automatically mapped to the link.Use Local Modules
Threshold: Define an error threshold for the migration. If the count of failed messages is below this threshold, the migration is still considered successful, and Stage 2 will continue at the appropriate time.
Set Export Path: This option should be configured when reviewing failed items, and moving them to a secondary location. This location is where those items will be moved to from the regular staging area.
Staging Area Path: Defines a path to which items should be exported, and items ingested. Multiple links can share the same export/import path, or they can be separate in order to distribute the exported data ready for ingestion. This path can be overridden on individual links if required.
PST Output Path: Allows the configuration of a PST Output Path for links where the type is PST. The output Path can be an UNC Path or an Azure Blob Storage Account.
Temporary Path: Allows the configuration of a temporary path to store PST files while they are processed on PST as a Target. It is recommended that this is FAST disk (Preferrably SSD)
Refresh: Refresh the contents of the grid.
Columns: Allows the selection of additional data columns that can be added to the grid.
Reset: Reset the columns and grid layout to their defaults.
Sync Mailboxes: Synchronizes mailbox information from Office 365 to Archive Shuttle
Cleanup Staging Area: Issues a command to the Archive Shuttle modules to clean up the staging area of already imported files. The EVExport, and all Import Modules will receive the command.
Enable/Disable/Run-Now Archive Gathering: Allows quick access to the functionality provided on the EV Environment page. These buttons allow for archive gathering to be enabled or disabled for a link, and to issue the command to perform archive gathering now.
Enable/Disable Offline Mode: When a link is enabled for offline mode, it will perform migration based on the Offline Media that has been configured for it. The staging area, if shown on this page, will not be used.
Set Rollover Threshold: Specify the size in MB, or number of items that PST files should be rolled over.
Watermark: The high and low watermarks can be configured per link. More information on the functionality of the high and low watermarks is available in the section relating to System Health.
The Workflow Policies page in the Admin Interface allows an administrator to customize Workflows and create new ones. These can either be new, original workflows or copies of existing workflows with some amendments.
NOTE: It is recommended that the built-in workflows are left as-is, and copies made if required.
Creating a New Policy
A new Policy can be created by clicking on New the Actions Bar and entering a name for the policy. It is recommended that existing policies are reviewed before creating new ones.
New Policies can contain any of the commands list on the right hand side of the Workflow Policies screen.
NOTE:It is recommended that new policies contain the command-pair CollectItemsForArchive and WaitForImportFinished, these perform the last-synch of the container.
When creating a new policy it is required to indicate the types of mapping that can use this particular workflow by selecting the check boxes at the top right of the Workflow Policies screen.
For information on the detail relating to each command, see below.
NOTE: Remember to save before leaving the screen in order to commit the changes to the Workflow Policy to the Archive Shuttle database.
Copying a Policy
When a policy is being viewed it is sometimes desirable to copy the policy and then make some small alterations to it. This is achieved by using the Copy button in the Actions Bar. Once a copy of the policy has been made, it can be given a new name, and saved to the Archive Shuttle database.
Editing a Policy
A policy can be edited by clicking on Edit in the Actions Bar, and selecting an existing policy from the list. If appropriate, the types of mapping that the policy can be used with can be adjusted. All changes are only committed to the Archive Shuttle database when the Save button is clicked.
Adding a New Command
A new command can be added to the bottom of the list of current commands in the Workflow by single clicking on it in the list on the right hand side of the page.
Moving a Command
A command can be moved from its current position in the list by clicking on the grey title area and dragging it to a new position in the list:
Editing the Details of a Command
The details behind a command such as the number and frequency of retries can be edited by clicking on the hyper link relating to the command, as shown below: