Cluster rollback behavior

When…	Actions...	The result…
Normal behavior.	The installer replaces current files with previous backup.	Success, cluster reverts to previous state.
The patch history is missing (files are not found in the directory defined by the parameter PATCH_HISTORY_DIR in patch.conf)	Without the history, the installer cannot determine which backups to use. Since there is nothing to replace them with, the installer does not remove the current files.	No rollback, cluster remains in same state. Error presented on screen and logged
You did not specify the most recent patch.	The history indicates that the patch is not the newest backup. The installer must use the most recent backup to roll back.	No rollback, cluster remains in same state. Error presented on screen and logged
The backups are missing (expected files are not found in the directory defined by the parameter PATCH_BACKUP_DIR in patch.conf).	Since there is nothing to replace them with, the installer does not remove the current files.	No rollback, cluster remains in same state. Error presented on screen and logged
The installer is partway through the roll back when there is a problem. The cluster contains some older files and some newer files.	If the installer cannot complete, it reverses the rollback actions, removing the older files and returning the newer ones.	No rollback, cluster remains in same state. Error presented on screen and logged