Skip to main content
Version: 1.19.1

Upgrade LiveData Migrator

We recommend you regularly upgrade LiveData Migrator so you can take advantage of new functionality and other improvements. To upgrade, run a newer version of the LiveData Migrator installer. The installer upgrades your LiveData Migrator instance to the new version.

If you're running version 1.15.1 or lower, you need to upgrade to LiveData Migrator 1.16.0 before upgrading to any higher versions.

Before you upgrade#

Configuration files stay the same after upgrading, but configuration files from the new version are also added into the same folder on an RPM installation. These new configuration files have the extension .rpmsave, and are ignored by LiveData Migrator by default. You may compare them and copy changes across accordingly, or use the new files.

The upgrade automatically overwrites shell scripts (such as with the newer versions.


Do not change the value of the encrypted database password value for the UI in If the key changes, the LiveData UI will fail to start. When prompted on an Ubuntu system to keep the old file or use the new one from the installer, choose to keep the existing file to prevent this.


Upgrading to LiveData Migrator 1.19 - Critical steps for Hive Migrator

Large Hive Migrator databases may take up to thirty minutes to optimize. This process is automatic and occurs when you first start Hive Migrator after upgrading LiveData Migrator 1.19. An interruption of the Hive Migrator service during this optimization may result in unrecoverable corruption of the database.

We strongly recommend that you:

  • Back up the Hive Migrator database before running a reset (purge) of all the metadata migrations.
    The default location of the database is here:

  • Reset all metadata migrations. You can do this through the Swagger-based REST API documentation, using the /migration/reset/all command. This command purges the Hive Migrator database as well as clearing the statistics and checksums for all migrations.

    The API call for doing metadata migration resets:

    curl -X 'POST' \  '' \  -H 'accept: application/json' \  -H 'Content-Type: application/json' \  -d '{  "forceStop": true}'

    A successful reset will produce the following output, including a "Success." for each migration:

    [  {    "migrationName": "MetaMigration1",    "status": "OK",    "errorCode": 0,    "message": "Success."  },  {    "migrationName": "MetaMigration2",    "status": "OK",    "errorCode": 0,    "message": "Success."  }]
  • Ensure that the Hive Migrator service is not interrupted when it is first started after the upgrade.

Obtain a new installer and upgrade LiveData Migrator#

To upgrade to the latest version of LiveData Migrator, download and run a new LiveData Migrator installer in the same way you do to install for the first time.

Upgrading to a newer version won't affect your filesystems or migrations. Any migrations that are in progress simply continue transferring data as normal.


You can check the component versions of your current installation by running the command livedata-migrator --version on your LiveData Migrator host machine.

System and custom users for upgrades#

If you want to run the installer using a default user, run the following command:


The default system user for the LiveData Migrator and LiveData UI services is hdfs, and the default system user for the Hive Migrator service is hive.

If you don’t enter a custom user and group, then the pre-existing user and group are used from the following files:

  • /opt/wandisco/hivemigrator/
  • /opt/wandisco/livedata-migrator/vars.env
  • /opt/wandisco/ui/vars.env

If any of these files don’t exist, the default user for that component is used instead.

If you want to upgrade the product using a custom user and custom user group, run the following commands:

Thin installer
./ --user <custom user> --group <custom group>
Fat installer
./ -- --user <custom user> --group <custom group>

This sets the custom user and custom user group for all services and their respective directories.

For more information about configuring custom users, go to Configure system users.

Install components using RPM/DEB#

If you're installing our product components individually using RPM/DEB, you can enter a custom user or group by adding a properties file with the custom user and group.



When you install using RPM/DEB, the properties file containing the custom user names and group names are used, and set the user and group of the service and its respective directories.

If you upgrade a single component without using a properties file, then the RPM/DEB checks for the pre-existing user and group in /opt/wandisco/hivemigrator/, /opt/wandisco/livedata-migrator/vars.env, and /opt/wandisco/ui/vars.env. If any of these files don't exist, the installer uses the default user for that component.


This applies to the hivemigrator-remote-server installer.

If you don't enter a custom user or group to the installer when you upgrade, the existing vars.env/ for each component of the product is retained, and existing property values are inserted into the new vars.env/ provided by the component packaging.

We don't currently retain previous custom properties when you upgrade with a custom user or group.

Next steps#

Continue migrating data as before. Learn how to get started.