Migrating Legacy TrueCommand to Version 1.2 and Newer
3 minute read
Starting with TrueCommand 1.2, TrueCommand is built and offered as a Docker container to drastically reduce system overhead and simplify TrueCommand updates. Migrating data can be done before or after installing the Docker container version of TrueCommand. The procedure is similar in both situations, with just a couple extra steps when the Docker container version of TrueCommand is already installed.
Preparing an existing container
- Turn off the container
- Wipe the container database
Migrating a previous TrueCommand Configuration
- Find/Create local system directory to store TrueCommand Docker container data
- Copy existing TrueCommand configuration files to new directory
ixdb.sqland move .sql into container database directory
Preparing an Existing Container for Migration
Overwrite WarningMigrating the configuration from a previous version of TrueCommand will overwrite any existing configuration! Migrating the configuration before installing the Docker container is recommended, or as soon as possible after installing to prevent making and then losing any new configuration settings.
Migrating a previous configuration into an existing TrueCommand Docker container installation requires wiping the existing database from the container and replacing with the
ixdb.sql database from the previous version of TrueCommand.
Make sure the container is turned off.
Open the directory you specified to use for managing the container and find the
Remove all existing files from this directory.
The container is ready for data migration from the previous version of TrueCommand.
Follow the steps in the next section to transfer the certificate, license, and database files into the existing container configuration directory.
Migrating a Previous TrueCommand Configuration
To move an existing TrueCommand 1.1 or earlier configuration to a Docker container version, follow these migration steps:
Create a local system directory for Docker container data. This step is only needed when the Docker container version of TrueCommand is not already installed. This directory will contain all the TrueCommand docker container data, including configuration files. For the rest of these instructions, this directory will be referred to as
localhostdirectory/. When the Docker container is already installed, find the existing
localhostdirectory/you specified during container installation.
Find and copy any existing TrueCommand 1.1 or earlier configuration files to the new
localhostdirectory/. Using a command like
rsyncis recommended. The Docker container will read these files and apply the existing configuration to the container when it is installed. The table lists the default location and required destination for all the different configuration files TrueCommand 1.1 or earlier can create. Only files that already exist need to be copied to the new TrueCommand
|Files from TrueCommand 1.1 and earlier||Copy destination in local host directory||Description|
|Custom SSL certificate or key that was imported into TrueCommand.|
|Directory tree of NAS configuration backups.|
|License and signature for the license.|
- For the TrueCommand 1.1
pg_dump ixdb > ixdb.sqlto transform the database into a single .sql file. Then move
localhostdirectory/for the TrueCommand Docker container.
You’re now ready to install or start the TrueCommand Docker container. Be sure to specify the
localhostdirectory/ during container installation for TrueCommand to load the migrated data.
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.