Enterprise Vault Discovery Accelerator environment
This is an overview page of Enterprise Vault Discovery Accelerator (EV DA) customers that are needed for the migration project. New EV DA customer databases can be added here, and Archive Shuttle collects information from the environment to get information about the cases associated with that customer database through the assigned Archive Shuttle Enterprise Vault Collector module.
|
|
NOTES: ·Enterprise Vault export and collector modules must run under the user account which has access to the Enterprise Vault and Enterprise Vault Discovery Accelerator server. ·An Enterprise Vault Discovery Accelerator environment requires dependency on an existing Enterprise Vault environment. |
EV DA cases will be shown on the bulk mappings, manual mappings and existing mappings pages as an archive type. Collection of items from EV DA cases are processed automatically after a mapping is created in the Bulk Mapping wizard (when collection of items is enabled.)
All target containers are supported for migration (Office 365, Exchange, Enterprise Vault, PST and Storage Import).
For more on Enterprise Vault Discovery Accelerator, click here.
User interface
For every Enterprise Vault Discovery Accelerator directory, the table lists the following information:
·Display Name
·SQL Server
·Database name
·Number of Cases
·Total Item Count
·Total Item Size
The actions you can take on this page are:
·Add: Add an EV DA environment.
·Run Now: Collect cases immediately.
·Refresh: Refresh table to show up to date statistics.
·Reset: Reset the grid to default layout.
·Columns: Choose which columns to display.
·Load: Load previously saved grid layout.
·Save: Save current grid layout. Click the Shared box to share the layout to other users.
·Export: Export grid into a .pdf, .xls, .xlsx or .csv format.
How to add an Enterprise Vault Discovery Accelerator environment
1.On the EV DA Environment page, click Add.
2.Select the module to associate with this environment. This module is responsible in collecting information on the EV DA directory.
3.Enter the Associated EV SQL server. This is the SQL server name/instance where this directory hosts its 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. Examples include:
omysqlserver.mydomain.com
omysqlserver
o192.168.0.1
omysqlserver.mydomain.com\instance
omysqlserver\instance
o192.168.0.1\instance
4.Enter the EV DA SQL Server. If this value is empty, the value from the Associated EV SQL server field will be used instead.
5.Enter the EV DA customer database SQL database name. This is the name of the database associated with your EV DA customer in the Discover Accelerator user interface.
6.Enter the Link SQL server. This should be filled by default.
7.Click Add.
Repeat these steps for each EV DA customer you wish to add to Archive Shuttle.
Additional details
·Migration from EV DA cases supports the following filters:
oPath
oItem Date
oItem Size
·Journal Transformation is currently not supported.
·EV DA supports the migration of EML messages.
Enterprise Vault retention mappings
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. |
Retention related mappings can be logged when interacted with. The logs will also show the retention label prior to its ingestion. This setting needs to be enabled, and the source container needs to be Enterprise Vault to be able to view the core logs.
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 site
·Source Retention Category
·Target Site
·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. |
SourceOne/EMX environment
This is an overview page of all the SourceOne/EmailXtender (EMX) environments that are needed for the migration project. New SourceOne/EMX environments can be added and ran here.
User interface
For every SourceOne/EMX environment, the table lists the following information:
·Environment Name
·SQL Server
·Database name
·Number of Archives
·Total Item Count
·Base Paths
The actions you can take on this page are:
·Add: Add a SourceOne/EMX environment.
·Enable Organization: Enable Exchange organization for archive collection.
·Disable Organization: Disable Exchange organization for archive collection.
·Run Now: Run archive collection now.
·Run Organization Collection: Run organization collection now.
·SMTP Settings: Set SMTP settings for archive collection. Click the checkbox to include SMTP archives, and add domains into the text box to be included into archive collection. This can be ran from the user interface, or is automatically ran once per day by using command S1CollectSMTPArchives in PowerShell.
|
|
NOTES: ·SourceOne does not have archives. ·Archive Shuttle determines message ownership and associates the first instance of a message to each sender and recipient Archive Shuttle identifies, and the routes a copy of that message. ·The command S1CollectSMTPArchives runs once per day and can be also ran from the user interface, on the SourceOne environment page. |
·Refresh: Reset the grid to default layout.
·Columns: Choose which columns to display.
·Load: Load previously saved grid layout.
·Save: Save current grid layout. Click the Shared box to share the layout to other users.
·Export: Export grid into a .pdf, .xls, .xlsx or .csv format.
How to add an SourceOne/EMX environment
1.On the Source/EMX Environment page, click Add.
2.Select the module to associate with this environment. This module is responsible in collecting information on the SourceOne/EMX environment.
3.Enter the SourceOne/EMX SQL server. This is the SQL server name/instance where this directory hosts its 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. Examples include:
a.mysqlserver.mydomain.com
b.mysqlserver
c.192.168.0.1
d.mysqlserver.mydomain.com\instance
e.mysqlserver\instance
f.192.168.0.1\instance
4.Enter the SourceOne/EMX customer database SQL database name. This is the name of the database associated with your SourceOne/EMX customer in the SourceOne/EMX user interface.
5.Enter the BasePath, and select whether to create an item database and/or enable archive collection.
6.Enter the Link SQL server. This should be filled by default.
7.Click Add.
Repeat these steps for each SourceOne/EMX customer you wish to add to Archive Shuttle.
Workflows for SourceOne SMTP archives
Below are workflows for SourceOne SMTP archives as a source into all supported targets in Stage 2.
|
|
NOTE: These workflows do not utilize shortcut deletion. |
·SourceOne SMTP to Enterprise Vault
·SourceOne SMTP to Exchange
·SourceOne SMTP to Office 365
·SourceOne SMTP to Office 365 Leavers
·SourceOne SMTP to Proofpoint
·SourceOne SMTP to PST
·SourceOne SMTP to Storage Import
·SourceOne SMTP to Storage Import (ownerless)
Links
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 Office 365 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.
Example: mysqlserver.mydomain.com
mysqlserver
192.168.0.1
mysqlserver.mydomain.com\instance
mysqlserver\instance
192.168.0.1\instance
·SQL Database Name
Default: ArchiveShuttleItem_. Read only.
Link
Map Modules: Provides the ability to allocate modules to this link.
|
|
NOTE: Multiple links can be selected and modules allocated to them. |
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.
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)
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 Collection: 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.
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.
Office 365
Create Office 365 Link: Provides the ability to create a new Office 365 link. It is possible to choose a name for the link.
Sync Mailboxes: Synchronizes mailbox information from Office 365 to Archive Shuttle.
Sync cloud-Only Mailboxes: Synchronizes cloud only mailbox information from Office 365 to Archive Shuttle.
Sync Mailboxes Filter: Specify filters for Office 365 mailbox sync commands. Properties include:
·Display Name
·Country
·Department
·User Principal Name
|
|
NOTE: The filter is applied over full mailbox search results. The module then returns only those mailboxes that fit the filter configuration. |
PST
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.
Set Rollover Threshold: Specify the size in MB, or number of items that PST files should be rolled over.
PST Target: Set PST target path for PST links.
PST Source: Set PST source folders for PST links.
File Name Policy: Set file name policy for PST files.
Output Watermark: Set watermarks for PST output paths.
Temporary Path: Set PST temporary path for PST links.
Proofpoint
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.
Edit Proofpoint Link: Modify the Proofpoint link.
Journal Transformation
Create Journal Transformation Link: Provides the ability to create a new Journal Transformation link. It is possible to choose a name for the link, and to specify the output folder.
Edit Journal Transformation Link: Modify the Journal Transformation link.
Storage Import
Create Storage Import Link: Provides the ability to create a new Storage Import link. It is possible to choose a name for the link, and to specify the output folder.
Edit Storage Import Link: Modify the Storage Import link.
Grid
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.
Load: Load a previously saved grid format.
Save: Save the grid format. Click the Shared box to share the layout to other users.
Export: Export the grid in a .pdf, .xls, .xlsx or .csv format.