Rolling back after the failed installation or upgrade

If the fresh installation or upgrade of BMC Release Package and Deployment (RPD) failed, you can roll back the changes. Depending on whether you installed or upgraded RPD, 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 RPD Apache, API, deployment engine, and dispatcher services with the version that you were installing. For more information, see Starting-or-stopping-product-services.

   Note

   If the product services are absent, then the installer failed before the services were created and you can skip step 2.

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

4. Restore an empty database.

   Note

   For information about 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 RPD Apache, API, deployment engine and dispatcher services with the version that you were installing. For more information, see Starting-or-stopping-product-services.

   Note

   If the product services are absent, then the installer failed before the services were 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 information about 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 RPD Apache, API, deployment engine, and dispatcher services with the new version that you were installing and previous version from which you were upgrading. For more information, see Starting-or-stopping-product-services.

   Note

   If the product 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 information about how to restore the database, refer to the documentation for your corresponding database.

Now, you can perform the fresh installation of the previous version of RPD.