A directory administrator may wish to revert to a previous version of the Directory Server even though the revert-update cannot perform the process completely.Running the update tool from a specific software distribution allows you to upgrade the software and configuration of an existing PingDirectory installation to the distribution's version. After an update, you can often use revert-update to undo that update.revert-update uses a log of file system operations to return the file system back to the previous state. For some updates, revert-update cannot completely undo the update and additional steps must be performed to restore the Directory Server. Examples include:1. When a change has been made to the data storage implementation such as the backend library version, changes in the implementation of composite indexes, and the compaction of JSON objects2. The introduction of the topology registry in PingDirectory 7When revert-update might require additional actions on the part of the administrator, the update tool will warn the administrator before the update is applied. For example:
$ ./update --serverRoot /prod/ds6/ds1 --licenseKeyFile $HOME/Downloads/PingDirectory7.2.licWarning: The updated server version includes database changes that are not compatible with the current server version. If you wish to later revert to an older version, then you will need to export the data to LDIF before performing the reversion, and then re-import the data after the revert process has completed. In addition, the changelogDb/ and db/changelog/ directories in the reverted server root must be deleted after the revert has completed.This warning can be ignored when upgrading from version 7.0.x. If you cancel now, the server will be left in its original state. Continue? (yes / no) [no]: yes
This document provides a walk-through of an update from 6.0 to 7.2 and the additional steps necessary to revert the update.