This documentation site is no longer maintained. For the latest Delphix product documentation, please visit help.delphix.com
Hyperscale Compliance
Breadcrumbs

Upgrading the Hyperscale Compliance Engine

Prerequisite

Before upgrading, make sure that you have downloaded the Hyperscale Compliance 6.0.0.0 tar bundle from the Delphix Download website.

How to upgrade the Hyperscale Compliance Engine

Perform the following steps to upgrade the Hyperscale Compliance Engine from 3.0.0.x/4.0.0.0/4.1.0.0/5.0.0.0/5.0.0.1 to 6.0.0.0 version:

  1. Run cd /<hyperscale_installation_path>/ and docker-compose down to stop and remove all the running containers.

  2. Run docker rmi -f $(docker images -q) to delete all the existing images.

  3. Remove all files or folders from existing installation directories, except docker-compose.yaml (Keep its backup outside the installation directory so that it is not overridden while executing the next step).

  4. Untar the patch tar in your existing installation path. tar -xzvf delphix-hyperscale-masking-6.0.0.0.tar.gz -C <existing_installation_path>

  5. Replace the docker-compose.yaml supplied with the bundle file as per the following:

    1. For users upgrading from 3.0.0.x: Use the docker-compose.yaml file supplied with the bundle and add the same ‘volumes’ and/or any other properties (if configured) for each container referencing the backed-up docker-compose.yaml from step 3.

    2. For users upgrading from 4.0.0.0/4.1.0.0/5.0.0.0/5.0.0.1: Replace the docker-compose.yaml file supplied with the bundle with the docker-compose.yaml file that you created as a backup at step 3.

  6. In the .env file supplied with the bundle, set the VERSION property as 6.0.0.0 (i.e. VERSION=6.0.0.0).

  7. Run the below commands to load the images(will configure Oracle-based unload/load setup):

    docker load --input controller-service.tar
    docker load --input unload-service.tar
    docker load --input masking-service.tar
    docker load --input load-service.tar
    docker load --input proxy.tar
    
    1. If upgrading from an MSSQL connector setup(supported starting 5.0.0.0 release), instead of running the above commands for load/unload services setup(which are for Oracle), run the below commands(rest remains same for the controller, masking, and proxy services):

      • docker load --input mssql-unload-service.tar

      • docker load --input mssql-load-service.tar

  8. Run docker-compose up -d to create containers.

  9. Make sure all your mount(s) are configured and accessible, before running a job.

Existing data remains intact after the upgradation.