- Platform Release 6.5
- Privacera Platform Installation
- Privacera Platform User Guide
- Privacera Discovery User Guide
- Privacera Encryption Guide
- Privacera Access Management User Guide
- AWS User Guide
- Overview of Privacera on AWS
- Configure policies for AWS services
- Using Athena with data access server
- Using DynamoDB with data access server
- Databricks access manager policy
- Accessing Kinesis with data access server
- Accessing Firehose with Data Access Server
- EMR user guide
- AWS S3 bucket encryption
- Getting started with Minio
- Plugins
- How to Get Support
- Coordinated Vulnerability Disclosure (CVD) Program of Privacera
- Shared Security Model
- Privacera Platform documentation changelog
Upgrade Privacera Manager
Your installation of Privacera Manager can be upgraded as new versions are released. To learn how to upgrade an air-gapped install, click here.
Release versions
Release versions are in this format: rel_X.X.X.X, for example: rel_6.2.0.1
To get the new version, contact your Privacera Sales Account Manager. To see what has been added for each release you can view that version's release notes.
Prerequisites
Backup the Apache Ranger and Portal databases before upgrading Privacera Platform (which includes data for PEG and Discovery). It will also help to save logs from all applications; the saved logs can be removed following a successful upgrade.
How to upgrade
Open the
pm-env.shfile to add the new release version for the Privacera Manager packages.vi ~/privacera/privacera-manager/config/pm-env.sh
Update the version for the following variables with the new release version.
PRIV_MGR_PACKAGE: update the release version in the path of the URL/privacera/rel/rel_X.X.X.X/.PRIV_MGR_IMAGE: update the release version in the URL/privacera-manager:rel_X.X.X.X.
Open the
vars.privacera.ymlfile to add the new release version for the Privacera product packages. This includes Portal, Solr, Discovery, etc.vi ~/privacera/privacera-manager/config/vars.privacera.yml
Update the version for the following variables with the new release version.
PRIVACERA_BASE_DOWNLOAD_URL: update the release version in the path of the URL,/rel/rel_X.X.X.X/cloud.PRIVACERA_IMAGE_TAG: update the release version.
Run the upgrade with following command:
cd ~/privacera/privacera-manager ./privacera-manager.sh upgrade-manager
This upgrades the Privacera Manager packages.
Then update the Privacera product packages with the following command:
./privacera-manager.sh update
Zookeeper upgrade issues
If you are facing problems with Zookeeper service when upgrading from 4.x to 5.x, see Unable to upgrade from 4.x to 5.x or 6.x due to Zookeeper snapshot issue.