This article describes how to upgrade an Journal Commander migration environment from Journal Commander 1.x.
We strongly advise you read through this article in its entirety before performing any kind of production environment upgrade.
There are three components that will be upgraded:

  • Journal Commander Core: An MSI will be run to perform this upgrade.
  • Journal Commander Modules: An MSI will be run to perform this upgrade.
  • Journal Commander databases: Journal Commander Core will upgrade the Journal Commander Directory Database, and each Item Database when the Windows services start, following the upgrade.

Note: See the Source/Target Compatibility Matrix to determine what version of .Net is required for the Journal Commander Core server.

Getting ready

We recommend that, whenever possible, you perform the upgrade in a lab environment first. This gives you some familiarity of the upgrade process and allows you to fine-tune the upgrade steps to suit the particular customer, environment, policies, and procedures.
Having access to a lab environment also enables the exploration of the new features that are delivered in the newer version of Journal Commander. More information relating to the new features is available in the Release Notes and the Revision Notes.
Before starting the upgrade, it is essential to have the following:

  • New Journal Commander 1.0 Core MSI
  • New Journal Commander 1.0 Modules MSI
  • Access to the username/passwords used during the installation for the Journal Commander Core and Modules

Note: Any username used during the original installation is remembered. However, the password must be re-entered.
In order for the upgrade to succeed, we recommend that there is sufficient free space on the SQL server locations for both the database and log files. The space available should be as follows:

Database/Log Space
Journal Commander Directory 2x current size of database
Journal Commander Directory Logs 1x current size of log file
Journal Commander Item Database 2x current size of database
Journal Commander Item Database Logs 1x current size of log file

Sufficient time should also be allocated to the upgrade. Upgrading a large Journal Commander Item Database can take several hours. We recommend you monitor the Core log files after deployment to verify the process has completed when working with large deployments.
If a problem is encountered when upgrading the Journal Commander database, there are manual steps that can be performed to resume the upgrade. These are available from Quadrotech Support.

Performing the upgrade

We advise you to perform the upgrade on the Journal Commander environment when migration activity is not actively running. Prior to performing the steps below, we recommend that you disable the Journal Commander modules that have been deployed and then allow some time to pass for the modules to complete their queued work before proceeding.
We also advise you to review the Journal Commander Dashboard. If the needles on the activity gauges are showing 0, then exports and imports are not currently running. Other background activity might still be in progress, so it is advised to perform the step of disabling the modules and reviewing the module log files to ensure work has stopped.
The following steps should be performed in order to upgrade the environment:

  1. Stop the Journal Commander Modules on all servers.
  2. Stop the Journal Commander Core service on the Journal Commander Core Server.
  3. Perform a full SQL database backup of:
    • Journal Commander Directory Database, and
    • Every Journal Commander Item Database
  4. Run the new Journal Commander 1.0 Core MSI on the Journal Commander Core Server.
  5. Verify that the installation/upgrade completes without errors. When the installation has been completed, open the Journal Commander Admin Interface and navigate to some of the pages.
  6. Run the Journal Commander 1.0 Module MSI on each server which have modules installed.

Note: If the migration target is Exchange or Office 365 and the server running the ingestion module is Windows 2008 R2, there is an additional Microsoft component to install:
Note: If the Office 365 Leavers functionality is to be used within Journal Commander, then there are additional requirements described in this link:
Note: For the Office 365 module to process licensing for Leavers, the PowerShell execution policy needs to be set to RemoteSigned or Unrestricted.
Verify that the installation/upgrade completes without errors. After the installation the Journal Commander modules page in the Admin Interface should show all modules without a red background. This indicates that they are properly communicating with the Journal Commander Core.
Note: If any changes have been made with regards to the logging levels for the Journal Commander Core or Modules, those changes will need to be implemented again once the upgrade has completed.
When the upgrade has been completed, perform the following post upgrade checks and ensure the step relating to Environment Sync is performed.

Post upgrade checks

Following the installation and upgrade of the migration environment, verify the upgrade by performing the followings tasks:

  1. Open the Journal Commander administration page, and verify that the page opens without errors.
  2. Verify the build number in the lower left hand corner of the administration page. It should be: 0.0.0.NNNNN (NNNNN will be five digits indicating the exact build number)
  3. Go to the EV Environment page, and perform a Sync All EV Environments operation. This will take a few minutes to run, and is an essential post-upgrade step.
  4. Open the Modules page from the Journal Commander administration page, and verify that all of the modules are accessible (none should show red, indicating that the Journal Commander Core has had issues contacting the module).
  5. Verify that all the Journal Commander services are started using the Windows Service Control Manager on each server in the environment.
  6. In each of the Journal Commander databases (Directory Database, and each Item Database) there is a table called SchemaVersion. The versions reported should be as follows:
    • Journal Commander Directory Database:
    • Journal Commander Item Database:

Note: If the SchemaVersion tables do not show these versions, contact Quadrotech Support.
We also recommend that you perform another full database backup prior to using Journal Commander for further archive migrations.

Print Friendly, PDF & Email