PingDirectory

Reverting an update

After the server has been updated, you can revert to the last version or one level back using the revert-update command.

About this task

The revert-update command accesses a log of file actions taken by the updater to put the file system back to its prior state. If you have run multiple updates, you can run the revert-update command multiple times to revert to each prior update sequentially. You can only revert back one level. For example, if you have run the update twice since first installing the server, you can run the revert-update command to revert to its previous state, then run the revert-update command again to return to its original state.

When starting up the server for the first time after a revert has been run, and the necessary extra steps have been completed, the server displays warnings about "offline configuration changes," but they are not critical and do not appear on subsequent start ups.

To revert to the most recent server version:

Steps

  • Run the revert-update command in the server root directory to revert back to the most recent version of the server.

    Example:

    $ PingDirectory-old/revert-update

Next steps

Depending on your installation and configuration, you might need to perform one or more of the following tasks:

  • Topology information such as server instances, instance and secret keys, server groups, and administrator users have moved to the topology portion of the configuration from the admin backend. As long as new servers are not added to the topology after this update, you can use the revert-update command to return to the previous version. However, if new servers are added, then the restored admin backend of this server does not contain information about the new servers, and the local server cannot communicate with any other servers in the topology. New servers should not be added to the topology if reverting this update is a possibility.

  • If new servers were added to the topology after the update, the new servers must be temporarily removed from the topology until all servers have been reverted to the previous version.

  • If the topology does not have a primary server when this command is run, the revert-update will not succeed. In this case, you must make one of the remaining updated servers in the topology the primary with the following command. This enables the chosen instance to run the revert-update command successfully.

    $ bin/dsconfig set-global-configuration-prop \
    --set force-as-master-for-mirrored-data:true