Configuring Journal Commander
This section outlines the basic steps required to configure Journal Commander. This is applicable for most archive migration projects. The user interface and other components of Journal Commander are explained in subsequent sections. We recommend reading each section before performing the post-installation configuration.
Initial Journal Commander setup
After Journal Commander has been installed, the following five tasks need to be performed before you start migrating archives:
- Configure module schedules.
- Enable Active Directory domains.
- Add source and target environments.
- Add link databases.
- Configure module mappings.
These tasks are explained below.
Configure module schedules
During Journal Commander installation, the core product, databases, and a number of modules will have been deployed in the environment to fulfill migration requirements. During the installation of the modules, each module is enabled. If modules are not enabled, they will not receive any work from the Journal Commander Core.
To check that all appropriate modules are enabled and operational, follow these steps:
- From the Journal Commander web interface, click Configuration > AS Modules in the navigation bar.
- Review the list of modules:
- Ensure all required modules are present.
- Ensure that the computer name, domain name, and version are as expected.
- Verify that all modules are reported appropriately and that none of the modules have a red background. If they do, there is a communication problem between the module and the Journal Commander Core.
All of the modules are configured to run continuously by default. If this doesn’t meet your requirements for the migration, modules can be individually scheduled to more suitable times using the Set Schedule button on the AS Modules page. This is described later in this guide.
Enable Active Directory domains
A few minutes after the Active Directory Collector Module is enabled, a list of domains where the Active Directory Collector Module is running become visible on the Configuration > Active Directory page.
By default, all domains are discovered, but won’t be scanned for user accounts. To enable one or more domains to be scanned, follow these steps:
- From the Journal Commander web interface, click Configuration > Active Directory in the navigation bar.
- Review the list of domains.
- Select the check box next to one or more domains.
- Click Enable in the navigation bar.
- Make sure the Scan Domain column shows a check mark.
Add source and target environments
Note: The steps are specific for each type of source and target, so review the appropriate documentation for that.
Add link databases
Once archive collection is enabled, the next step in the migration is to add link databases for each of the vault stores. A link database is needed for each link in the source environment.
The Configuration > Links page may already contain some links that were collected. These links are created automatically. You must manually create other links, for example, links to Office 365 and PST. To create a link database:
- Open the Configuration > Links page.
- Select the tab of the type of link database you’re creating (for example, Office 365), and then click Create Link.
- Follow the prompts to create the link.
Configure module mappings
The next stage of the configuration involves mapping modules to the Links in the migration project. To do it, follow these steps:
- Go to Configuration > Links.
- Select the check box next to a vault store/Exchange database/source link.
- Click Map Modules in the navigation bar.
- From the pop-up window, select appropriate modules from the drop-down lists, and then click Save.
Edit module mappings
Module mappings can be modified by following these steps:
- Go to Configuration > Links.
- Select the check box next to a vault store/Exchange database.
- Click Map Modules.
- Make desired changes to the current mapping for this link, and then click Save.
Shortly after module mappings have been added, the appropriate modules perform their tasks and the Number of Containers column updates to show the number of containers in the link.
For the modules that are performing export and import functions, it’s also important to set the staging area path. The corresponding modules need to be paired up to facilitate the flow of archived data. For example, the EV Export module path should correspond to the Exchange import path if the migration is needed to flow in that direction.
Setting up the staging area path
To configure the staging area path:
- Go to the Configuration > Links page.
- Select the checkbox next to a vault store/Exchange database/source link.
- Click Path and follow the prompts.
Repeat this step for each export and each import module. For the second and subsequent paths you define, the Staging Area Path is pre-populated with the path that was previously used. This makes it possible to quickly configure many modules with the same storage location.
The current export/import path and module mappings can be viewed on the Links page. Make sure all links are correctly defined with the appropriate export/import path before proceeding with the migration of any archived data.
It’s also possible to configure the Default Staging Area Path that all modules and links will use unless the setting is overridden on an individual link.
Validating the setup
Once the stages above have been performed and all necessary setup and configuration steps are complete, the archive migration is ready to begin.
At this point, a collection of links have been defined and mapped to modules that perform tasks on those links. The source and target environments have been defined within Journal Commander and all of the Journal Commander Modules are enabled and set to an appropriate schedule.
Note: Before proceeding with any migration of archived data, confirm that each stage has been performed.
Depending on the migration, additional steps may be required. These are described later in this guide.