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.
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
start.sh) with the newer versions.
Do not change the value of the encrypted database password value for the UI in
application-prod.properties. If the key changes, the LiveData UI will fail to start. When prompted on an Ubuntu system to keep the old
application-prod.properties file or use the new one from the installer, choose to keep the existing file to prevent this.
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.
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
If you don’t specify a custom user and group, then the pre-existing user and group are used from the following files:
- /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 command:
./livedata-migrator.sh -- --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.
If you're installing our product components individually using RPM/DEB, you can specify a custom user or group by adding a properties file with the custom user and group.
/opt/wandisco/tmp/ldm.properties: USERNAME="custom" GROUPNAME="custom"
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/vars.sh, /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 provide a custom user or group to the installer when you upgrade, the existing vars.env/vars.sh for each component of the product is retained, and existing property values are inserted into the new vars.env/vars.sh provided by the component packaging.
We don't currently retain previous custom properties when you upgrade with a custom user or group.
Continue migrating data as before. Learn how to get started.