Operating Systems

This section lists software applications that are compatible with Journal Commander Core.

Software Version Journal Commander
Major Service Pack
Windows Server 2003 x86 RTM, SP1, SP2 N
2003 x64 RTM, SP1, SP2 N
2008 x86 RTM, SP1, SP2 N
2008 x64 RTM, SP1, SP2 N
2008 R2 RTM, SP1 Y
2012 RTM Y
2012 R2 RTM Y
2016 RTM Y
2019 RTM Y
Azure SQL Database P
.NET Framework 3.5 and earlier N
4 Client Profile RTM N
4 Full Profile RTM N
4.5 Full Profile RTM N
4.5.2 RTM Y
4.6 RTM Y
4.6.1 RTM Y
4.6.2 RTM Y
4.7 RTM Y
4.7.1 RTM Y
4.7.2 RTM Y

1 Although Enterprise Edition of Microsoft SQL Server is recommended, Standard Edition may be used if the SQL instance uses the recommended (not minimum) resources associated with the size of migration you are performing. Planning for additional time will be required to accommodate regularly required offline maintenance.
2 Requires SQL Server on Windows. Linux is NOT supported.

SQL

Please note that SQL is only relevant within your environment when installing Core. If you are installing within the cloud, Quadrotech maintains SQL for you.

SQL Server Version

The following versions of SQL Server are supported with Journal Commander:

Version Supported?
SQL Server 2005 No
SQL Server 2008 No
SQL Server 2008 R2 No
SQL Server 2012 Yes
SQL Server 2014 Yes
SQL Server 2016 Yes
SQL Server 2017 Yes

Note: Having the latest service pack installed is recommended.

SQL Editions

Although Enterprise Edition of Microsoft SQL Server is recommended, Standard Edition may be used if the SQL instance uses the recommended (not minimum) resources associated with the size of migration you are performing. Planning for additional time will be required to accommodate regularly required offline maintenance.

Hardware requirements for SQL Server

Journal Commander requires a number of SQL databases:

  • The Journal Commander Directory database holds the configuration information.
  • Each Journal Commander Item database holds item information for a link. For every source link, there needs to be an item database.

The SQL Server that manages these databases must reside on a separate server than the Journal Commander core and modules. The only exception is for a non-production pilot/demonstration system. It’s also recommended that it has a dedicated SQL Server instance that’s not shared with other applications.
The table below indicates the requirements for SQL Server for a small Journal Commander migration (less than 5 TB).

Component Configuration
Processors (cores) Minimum 4, Recommended 8
Memory Minimum 16 GB, Recommended 32 GB
Hard disk Disks should be configured as per Microsoft SQL Server best practices with TempDB, databases and logs on separate disks.
Virtualization Supported, however performance may be impacted if resources mentioned above are not dedicated

The table below indicates the requirements for SQL Server for a medium Journal Commander migration (less than 20 TB).

Component Configuration
Processors (cores) Minimum 8, Recommended 16
Memory Minimum 32 GB, Recommended 64 GB
Hard disk Disks should be configured as per Microsoft SQL Server best practices with TempDB, databases and logs on separate disks.
Virtualization Supported, however performance may be impacted if resources mentioned above are not dedicated.

The table below indicates the requirements for SQL Server for a large Journal Commander migration (more than 20 TB).

Component Configuration
Processors (cores) Minimum 16, Recommended 32
Memory Minimum 64 GB, Recommended 128 GB
Hard disk Disks should be configured as per Microsoft SQL Server best practices with TempDB, databases and logs on separate disks.
Virtualization Not normally supported. Contact Quadrotech if virtualization is the only possibility.

Journal Commander keeps track of every item it exports/imports for auditing purposes. It places a reliance on SQL Server for this task. An adequately prepared SQL Server that meets the recommended specification is essential for a fast migration.
Note: Performance of the migration will be impacted if the SQL Server environment is not sufficient for the needs of the migration.

Disk

Disk information related to Journal Commander can be found here.

Sizing Considerations

Journal Commander uses a single Directory Database, and potentially multiple Item databases (depending on the number of source environment Vault Stores that are configured to migrate).
The Directory Database size requirement is 500 MB. However, to allow for temporary transaction log growth, it is recommended to ensure at least 2 GB is available for the database and logs.
Each item database has an initial storage requirement of 2 GB; 1 GB for the data file, and 1 GB for the transaction log.
The Journal Commander Item databases will grow depending on the items that are being migrated. A basic sizing guide for each item database is 1024 – 1500 bytes for each item collected plus 1 GB for static data, transaction logs and temporary data fluctuations.

Component Configuration
Directory Database 500 MB
Each Item Database 2 GB

In an environment when many source environment Vault Stores are considered for migration, we recommend that you configure the SQL Server setting relating to the default database and transaction log location to a drive or folder with sufficient storage space. We also recommend that all of the Journal Commander databases (Directory, and Item databases) have the SQL autogrowth feature enabled. Further, in this type of environment, we recommend that you move the databases and transaction logs for the Item Databases to separate storage areas, per the table in the previous section.

Planning for the Databases

Journal Commander uses the following databases:

  • Journal Commander Directory database: There is just one of these. It hosts all configuration and non-item based metadata.
  • Journal Commander Item database(s): There is one of these for each source Link (e.g. one per Vault Store). These databases do not have to be on the same SQL Server as the Journal Commander Directory database. Each Item Database can be on a separate SQL Server, if required.

Microsoft SQL Server must be installed and set up before you install Journal Commander. The collation requirement for the SQL Server installation must be case-insensitive, accent-sensitive (CI, AS); case-sensitive and accent-insensitive installations are not supported.
Microsoft SQL Server must be on a dedicated server, either physical or virtual. It is not supported to have it on the same server as the Journal Commander Core server. It is not supported to have the Microsoft SQL Server shared with any other software, for production use.
Before installing the Journal Commander Core Components, make sure the account that will be used has “dbcreator” rights in Microsoft SQL Server.

Storage Requirements for SQL Databases

Storage is required for the following SQL databases:

  • Journal Commander Directory database
  • Journal Commander Item databases

The Directory Database size requirement is 500 MB. However, to allow for temporary transaction log growth, it is recommended to have at least 5 GB is available for the database and logs.
Each item database has an initial storage requirement of 2 GB; 1 GB for the data file, and 1 GB for the transaction log.
The Journal Commander Item databases will grow depending on the items which are being migrated. As a guideline, each item in the item database about 3000 bytes.

License

Overview of Journal Commander licensing

Journal Commander uses a license file that is bound to the domain name where the Journal Commander Core Server is installed. A license file must be obtained that covers the features and user/data amounts that are to be migrated.
The following types of Journal Commander license are available:

  • Production license: This license has no time limits associated with it and has the amount of user licenses / data extraction licenses that have been purchased.
  • Trial license: This license is time limited and allows testing the full functionality of Journal Commander for a limited time only. When the license expires, the software continues to run in a restricted, read-only mode, which allows for many Journal Commander activities to be performed except export/import of data.

Note: Only a Journal Commander license will be accepted with Journal Commander. An Archive Shuttle license is NOT interchangeable with a Journal Commander license, and vice versa.

Obtaining a license file

License files are issued by email, from Quadrotech, upon purchase. If a trial license is needed, please contact Quadrotech Support.

Installing Journal Commander license files

The license file has to be installed on the Journal Commander Core Server.
The license file is requested during the Journal Commander Core installation.

Obtaining the software

A download link will be provided by Quadrotech.

Installing Journal Commander Core Server

Note: Before installing Journal Commander, check that all prerequisites for the planned installation have been fulfilled
To install Journal Commander:

  1. Log in to the designated Journal Commander Core Server.
  1. Double-click the JournalCommander.xx-x.x.xxxx.x.msi file to start the installation.

Note: Setup scans the server to determine whether it meets the prerequisites and displays a report. Install any missing prerequisites and restart setup.

  1. Install the required Journal Commander components for this computer.

The requirements for a Journal Commander Core server are as follows:

  • Core Service: Installs the Journal Commander Service that periodically executes Journal Commander tasks.
  • Web Service: Installs the Journal Commander Web Services. These communicate with the Journal Commander modules by HTTP(S).
  • Web Interface: Install the Journal Commander Web Interface. This is a web-based interface that enables administrators to manage Journal Commander.

4. Enter the account under which the components to be installed should run.
5. Enter the Journal Commander SQL Instance where the Journal Commander databases will be created. This can be:

Default instance: mySqlServerName.MyDomain.com

Named instance: mySqlServerName.MyDomain.com\MyInstanceName

6. Enter the folder where the Journal Commander logs should be stored.

7. Select the Journal Commander license file.
Note: It is essential to verify that the license information is correct. Otherwise, Journal Commander functionality may be disabled.

Print Friendly, PDF & Email