Upgrade considerations

  • Peer setup and clustered configuration are deprecated and will be removed in PingDataGovernance 9.0. If you plan to upgrade to PingDataGovernance 8.0 at some point, consider using server profiles to manage server configuration. Introduced in PingDataGovernance 8.0, server profiles support deployment best practices such as automation and Infrastructure-asCode (IaC). For more information about server profiles, see the PingDataGovernance Server Administration Guide for PingDataGovernance 8.0 or later

  • If you are updating a multi-server topology from PingDataGovernance 7.0.x to, you must use the --skipMirroredSubtreeUpdateTask option for the updater or the update fails. Alternatively, you can uninstall all but one of the servers to retain the base configuration, update the standalone server, install fresh servers on the new version, and add them back to the topology with the peer options. However, using the --skipMirroredSubtreeUpdateTask option is the recommended path.

Resolved issues

The following issues have been resolved with this release of PingDataGovernance Server:

Ticket ID Description

To support multiple trace loggers, each trace logger now has its own resource key, which is shown in the "Resource" column in the output of "status". This key allows multiple alarms, due to sensitive message types for multiple trace loggers.


Allows users who were migrated from the admin backend to the topology to manage the topology. Migrated users are granted the "manage-topology" privilege if they do not already have it.


Fixed an issue where the server was attempting to connect by an IP address rather than a hostname when DNS lookup was successful.


Added a --duration argument to collect-support-data. When used, only the log files covering the specified duration before the current time are collected.


Fixed an issue that stopped new extensions from being installed.