Rolling back after the failed installation or upgrade

If the fresh installation or upgrade of BMC Release Process Management (RPM) or BMC Release Lifecycle Management Requester UI (now called Release Process Management - Requester UI, 5.0.03.001 onward) (RLM Requester UI (now called RPM Requester UI, 5.0.03.001 onward)) failed, you can roll back the changes.

• • Rollback for BMC Release Process Management
  • Rollback for BMC Release Lifecycle Management Requester UI (now called Release Process Management - Requester UI, 5.0.03.001 onward)

Rollback for BMC Release Process Management

Depending on whether you installed or upgraded RPM, follow one of the procedures to perform a rollback:

• Rolling back after a failed fresh installation
• Rolling back after a failed upgrade to a new folder
• Rolling back after a failed upgrade to the same folder

Rolling back after a failed fresh installation

1. Go to RLMhome/UninstallBMCBRLM, and then try to run the uninstall.sh (Linux) or uninstall.cmd (Windows) file. If the file is absent, proceed to step 2.

2. Stop and remove the RPM service with the version that you were installing.

   Note

   If the RPM service is absent, then the installer failed before the service was created and you can skip step 2.

3. Delete the RLMhome folder and all of its content.

4. Restore an empty database.

   Note

   For the details on how to restore the database, refer to the documentation for your corresponding database.

Now, you can run the installation again.

Rolling back after a failed upgrade to a new folder

This method of rollback requires a backup of your database before the upgrade.

1. Go to RLMhomeNew/UninstallBMCBRLM, and then try to run the uninstall.sh (Linux) or uninstall.cmd (Windows) file. If the file is absent, proceed to step 2.

2. Stop and remove the RPM service with version that you were installing.

   Note

   If the RPM service is absent, then the installer failed before the service was created and you can skip step 2.

3. Delete the RLMhomeNew folder and all of its content.

4. Restore the database from the backup.

   Note

   For the details on how to restore the database, refer to the documentation for your corresponding database.

Now, you can run the upgrade again.

Rolling back after a failed upgrade to the same folder

This method of rollback requires a backup of your database before the upgrade.

1. Go to RLMhomeNew/UninstallBMCBRLM, and then try to run the uninstall.sh (Linux) or uninstall.cmd (Windows) file. If the file is absent, proceed to step 2.

2. Stop and remove the RPM services with the new version that you were installing and previous version from which you were upgrading.

   Note

   If the RPM services for a new and old versions are absent, then you can skip step 2.

3. Delete the RLMhome folder and all of its content.

4. Restore the database from the backup.

   Note

   For the details on how to restore the database, refer to the documentation for your corresponding database.

5. Run the upgrade again with the Skip database modification check box selected.
6. Stop the RPM service if it started.

7. In the terminal, run the following commands:

   <RLMhome>/bin/setenv.sh (Linux) or <RLMhome>/bin/setenv.bat (Windows)
   cd <RLMhome>/releases/<productVersion>/RPM
   jruby -S rake db:migrate
8. Start the RPM service.

1. Go to RLMUIhome/uninstall, and then try to run the uninstall.bin (Linux) or uninstall.cmd (Windows) file. If the file is absent, proceed to step 2.

2. Stop and remove the RLM Requester UI (now called RPM Requester UI, 5.0.03.001 onward) service as follows:

   • After a failed fresh installation, service with the version that you were installing.
   • After a failed upgrade to the same folder, service with the previous version from which you were upgrading.

   Note

   If the RPM service is absent, then the installer failed before the service was created and you can skip step 2.

3. Delete the RLMUIhome folder and all of its content.

Now, you can run the installation again.