Upgrading the Hyperscale Compliance orchestrator (Docker compose)

Pre-requisite

Before upgrading, ensure you have downloaded the Hyperscale Compliance 17.0.0 tar bundle from the Delphix Download website.

How to upgrade the Hyperscale Compliance Orchestrator

Perform the following steps to upgrade the Hyperscale Compliance Orchestrator to the 17.0.0 version:

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

Run the below commands to delete all existing dangling images and hyperscale images:

docker rmi $(docker images -f "dangling=true" -q)
docker rmi $(docker images "delphix-hyperscale-masking-proxy" -q)
docker rmi $(docker images "delphix-controller-service-app" -q)
docker rmi $(docker images "delphix-masking-service-app" -q)
docker rmi $(docker images "delphix-*load-service-app" -q)

Remove all files or folders from existing installation directories, except docker-compose.yaml (Keep its backup outside the installation directory so it is not overridden while executing the next step).
Take backup of .env file and untar the patch tar in your existing installation path. tar -xzvf delphix-hyperscale-masking-17.0.0.tar.gz -C <existing_installation_path>
Replace the docker-compose.yaml supplied with the bundle file as per the following:
- For users upgrading from 3.0.0.x: Use the connector-specific docker-compose-sample.yaml file(e.g. docker-compose-oracle.yaml or docker-compose-mssql.yaml) 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.
- For users upgrading from 4.0.0.0 and above: 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.
- Similar to other services, make sure to add the volume binding for the staging area path under controller-service as well. For example,
  - /mnt/hyperscale:/etc/hyperscale
Apply the backed up .env file and set the VERSION property as 17.0.0 (i.e. VERSION=17.0.0).
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
```
- 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
- If upgrading from a Delimited Files connector setup (supported starting 12.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 delimited-unload-service.tar docker load --input delimited-load-service.tar
- If upgrading from a MongoDB connector setup (supported starting 13.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 mongodb-unload-service.tar docker load --input mongodb-load-service.tar
- If upgrading from a Parquet connector setup (supported starting 17.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 parquet-unload-service.tar docker load --input parquet-load-service.tar
Run docker-compose up -d to create containers.
Ensure all your mount(s) are configured and accessible, before running a job.

Existing data remains intact after the degradation.