Prerequisite
Before upgrading, make sure that you have downloaded the Hyperscale Compliance 5.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.x to 5.0.0.0 version:
-
Run
cd /<hyperscale_installation_path>/anddocker-compose downto stop and remove all the running containers. -
Run
docker rmi -f $(docker images -q)to delete all the existing images. -
Remove all files or folders from existing installation directories, except
docker-compose.yaml(Keep its backup outside the installation directory so that its not overridden while executing the next step). -
Untar the patch tar in your existing installation path.
tar -xzvf delphix-hyperscale-masking-5.0.tar.gz -C <existing_installation_path>Note: Below Unload/Load services for MSSQL are also bundled along with the tar, which however will only be activated/running if configured viadocker-compose.yamlfile. (By default docker-compose file is configured with Oracle services, and should not impact the upgrade).-
mssql-unload-service.tar
-
mssql-load-service.tar
-
-
Replace the
docker-compose.yamlsupplied with the bundle file as per the following:-
For users upgrading from 3.0.0.x: Use the
docker-compose.yamlfile supplied with the bundle and add the same ‘volumes’ and/or any other properties (if configured) for each container referencing the backed updocker-compose.yamlfrom step 3. -
For users upgrading from 4.0.0.x: Replace the
docker-compose.yamlfile supplied with the bundle with thedocker-compose.yamlfile that you created a backup at Step 3.
-
-
In the
.envfile supplied with the bundle, set the VERSION property as 5.0.0.0 (i.e VERSION=5.0.0.0). -
Run the below commands to load the images:
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 -
Run
docker-compose up -dto create containers. -
Make sure all your mount(s) are configured and accessible, before running a job.
-
Existing data remains intact after the patch installation.