Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space DEV and version r0682

D toc


D s company
 may publish updates to the software release that you have currently installed. The 
D s item
itemMaintenance Release Updater
 can be run from the
D s node
 to check for updates for the release of the platform that is currently installed on the node. If a maintenance release (e.g. Release x.y.1) is available, the script downloads the package and launches the update locally.

Support Matrix

This script can only be used for maintenance patches for the current release. For example, you cannot upgrade from Release 5.1 to Release 6.0 or any later release using this script.


NOTE: This script is not available in the GA release of any major release, since no maintenance release is yet available.

Below are some example upgrade paths.


NOTE: These are example upgrade paths. Some of these releases may not exist yet.

Example UpgradeSupported?
Release 6.0.1 → Release 6.0.2Supported
Release 6.1.1 → Release 6.1.2Supported
Release 6.1.1 → Release 7.0.0Not Supported
Release 6.0.0 → Release 6.2Not Supported
Release 6.0.1 Hot FixesNot Supported


  • The 
    D s platform
     must not be running when the Updater is executed.
  • Do not run this script using a scheduler. 


    NOTE: When the script is executed and new software is downloaded, the script automatically begins the update process, which can disrupt user operations and user data and may not work if the platform is running.



NOTE: You must acquire the script from the

D s item
itemdownload site
. Please use the credentials provided to you to connect to the download site.


NOTE: Before you begin, shut down the

D s platform
and perform backups of the deployment directory and
D s item

  • This script is supported by Centos/RHEL 6 or later. Ubuntu is not supported.

  • This script must be run as the root user on the node.
  • The 
    D s platform
     must be installed on the node and configured to run using the 
    D s defaultuser
  • To enable downloads of updates, CURL must be installed on the node.


Script Name:

Code Block


Prior to execution, the script should be placed somewhere other than the

D s item
iteminstall directory

  • /root or /tmp are acceptable locations.
  • The script must have execute permissions, if it doesn't already have them.

For each run of the script:

  • It creates a unique working directory under /opt/trifacta-upgrade-workdir
  • The working directory is where downloaded artifacts, backup artifacts, and log files are stored during execution.

Download and Install:

The following command checks for an update. If one is detected, it downloads the update and launches the updating process:

Code Block
 NOTE: The credentials asked by the script are only used to connect to the FTP site to check for and download installer artifacts. These credentials are not stored anywhere.

The package is downloaded by default to the following location:

Code Block

Install Downloaded Package:

If you have separately downloaded the update from 

D s company
, the following performs the update from the local package, which is specified by parameter:

Code Block
./ -i <path_to_downloaded_RPM>

Do not restart the platform at this time, in case there are necessary migrations for this update. See below.

Migrate Configurations

Even between maintenance releases, it's possible for some configuration settings to be updated or migrated into the Workspace Admin page. 


NOTE: For every upgrade or update, you should perform the steps to migrate any configurations that have changed. If there are no configurations to migrate, the process is harmless.

For more information, see Migrate Configurations.

Verify Update

After you have completed the update:

  1. Review any update documentation provided to you.
  2. Restart the platform. See Start and Stop the Platform.
  3. Verify operations. See Verify Operations.

More Help:

Code Block
./ -h