Skip to main content

Upgrade LiveData Migrator

LiveData Migrator for Azure comes with an update shell script, which can be found at /opt/wandisco/ by default. You can run the script on your HDFS edge node to check for available package updates or to install them.

Check for updates

To check for available updates to LiveData Migrator packages:

  1. Perform a dry run of the update shell script by running it with the -d parameter:

    /opt/wandisco/ -d
  2. Check the output. For example:

    [DRY RUN] No changes will be made

    Checking for packages to upgrade
    Updates available for the following packages
    livedata-gateway.noarch 0.2.19~SNAPSHOT-1 fusion-repo.wandisco.com_fusion-internal-yum_rhel

    In this example, there are updates available for the packages listed. If there are no updates available, no packages will be listed.

Update LiveData Migrator for Azure


Check the status of your metadata migrations following upgrade. If after upgrading to the latest version of Live Data Migrator for Azure all existing metadata migrations display as failed, complete the following steps to get your metadata migrations running again:

  1. Sign in to the UI.
  2. Navigate to the Metadata Migrations panel.
  3. Click Start for the first failed migration.
  4. Wait until the migration has the "Running" status, then start the next failed migration.
  5. Repeat until all failed metadata migrations are running.

If upgrading from LiveData Migrator for Azure version 1.23.7 to version 1.25.3 and currently using Data Transfer Agents, additional steps are required to start the DTA service. See the Known Issue for steps and more info.


Upgrading Data Migrator for Azure if using a Databricks agent

You must replace the Databricks JDBC driver. Data Migrator for Azure doesn't support Databricks JDBC driver version 2.6.22 or earlier. To upgrade to JDBC driver version 2.6.25 or higher and continue using Databricks agents with Data Migrator, please download the appropriate version of the driver and delete the previous version. See Before you start for more information on applying the Databricks driver.

If you have failing migrations after a product upgrade, upgrade the JDBC driver and restart migrations to get the migrations working again.

To perform all available package upgrades for your LiveData Migrator for Azure instance:

  1. Run the update shell script:


    Follow these steps to upgrade as a custom user.

  2. When asked "Are you sure you want to upgrade these packages? y/N", enter "y" and submit.


    For any conflicts reported between your existing and an upgraded version of a configuration file, select "N" or "0" to keep the current version. After the upgrade, manually edit the configuration file to add any new properties.

  3. Check the service is running. For example:

    Service is running
    # systemctl status livedata-migrator
    ● livedata-migrator.service - WANdisco LiveData Migrator
    Loaded: loaded (/opt/wandisco/livedata-migrator/livedata-migrator.service; enabled;
    Active: active (running) since Tue 2022-11-29 16:20:48 UTC; 6 days ago
    Main PID: 4992 (java)

    If the service isn't running, start it with:

    systemctl start livedata-migrator
  4. Optionally, check for updates again to ensure the update was successful and no further updates are available.


    You must update to version 1.16 of LiveData Migrator for Azure before you can update to later versions. If you're running a previous version, run /opt/wandisco/ to update to 1.16, and then run it again to update to the latest version.

Next steps

When you've updated LiveData Migrator for Azure, you can continue migrating data as normal.