1. Installation Guide
  2. Restoring a Prior Installation and Configuration

Restoring a Prior Installation and Configuration

This task is part of Uninstalling Siebel CRM.

Where you installed Siebel CRM as an update from a prior release, you can uninstall the software on a single computer or operating system instance and restore your prior release's installation and configuration.

Do one of the following, according to your requirements:

  • Restore a prior installation (Siebel CRM 21.2 or later) that uses the new installer.

  • Restore a prior installation (Siebel CRM 21.1 or earlier) that does not use the new installer.

Before you install Siebel CRM, it is strongly recommended to do the following:

  • Back up the Siebel database. Back up the Siebel database so that, after installing Siebel CRM as described in Installing Siebel CRM in an Update Installation, allowing the PostInstallDBSetup utility to run, and optionally running RepositoryUpgrade, if you decide to roll back the installation and restore your prior release, as described in this topic, then you can use this backup to restore the Siebel database to its prior state.

  • Back up the Siebel Gateway registry (ZooKeeper). Back up the Siebel Gateway registry so that, after installing Siebel CRM as described in Installing Siebel CRM in an Update Installation, if you decide to roll back the installation and restore your prior release, as described in this topic, then you can use this backup to restore the Siebel Gateway registry to its prior state. Where possible, you can restore the Siebel Gateway registry from backup files created by the installer. Otherwise, restore from backups you made manually. For more information about backing up and restoring the Siebel Gateway registry, see Siebel System Administration Guide.

    Note: As noted in Siebel System Administration Guide, an updated version of Apache ZooKeeper is provided for the Siebel Gateway registry. This new version introduced changes in the files and directories used by ZooKeeper. You must take these changes into account when restoring the Siebel Gateway registry as part of restoring your prior release.

Restoring a Prior Release That Uses the New Installer (Siebel CRM 21.2 or Later)

Note: This uninstallation case applies where you have installed the current release of Siebel CRM as an update for Siebel CRM 21.2 and later decide to restore Siebel CRM 21.2.

You can restore a prior Siebel CRM release that uses the new installer (Siebel CRM 21.2 or later). When you perform an update installation from a prior release that supports the new installer, custom files in the installation directory are backed up, along with configuration files like server.xml and properties files, because the installer replaces these files due to product changes. You specify the backup directory location when you install the new release. By default, the backup directory location is SIEBEL_ROOT\mde_backup.

Within the backup directory, the version-specific backup subdirectory might be named SIEBEL_ROOT_22.x, such as SIEBEL_CRM_22.x (for an installation directory of SIEBEL_CRM). This directory contains only configuration files that might be used when restoring the prior release of Siebel CRM that supports the new installer.

The backup directory contains version-specific subdirectories containing the files that you might need to restore when you restore a prior version. You can restore required files only or all files. You must determine which files you require after the restore, based on whether the customizations and configurations are backward compatible.

To restore a prior release that uses the new installer (Siebel CRM 21.2 or later)

  1. Verify that the current installation and installation history are qualified for performing this task.

  2. Manually stop all of the services, as follows:

    • (Windows) Stop the services for Siebel Gateway, Siebel Server, and Apache Tomcat (for external and internal application containers).

    • (UNIX) Stop the services for Siebel Gateway and Siebel Server and the processes for Apache Tomcat (for external and internal application containers).

    Note: Do not remove any configurations previously created using Siebel Management Console.

  3. Uninstall the current release of Siebel CRM using the OUI (Oracle Universal Installer) uninstaller function of the Siebel CRM installer, as follows for your operating system:

    • (Windows) SIEBEL_ROOT\oui\bin\setup.exe

    • (UNIX) SIEBEL_ROOT/oui/bin/runInstaller.sh -invPtrLoc inventory_file_location

    Note: Do not delete the installation directory or the files it contains, which include the backup directory.

  4. Verify that the external and internal services exist after uninstallation and they are still in a stopped state.

  5. Reinstall the prior release of Siebel CRM 21.2 or later to the same installation directory.

    Note: Do only the installation task; do not select configuration tasks.

  6. Restore the Siebel database from the backup you made before performing the update installation.

  7. Restore the Siebel Gateway registry from the backup you made before performing the update installation.

  8. Manually start all of the services, as follows:

    • (Windows) Start the services for Apache Tomcat (for external and internal application containers), Siebel Gateway, and Siebel Server.

    • (UNIX) Start the processes for Apache Tomcat (for external and internal application containers) and the services for Siebel Gateway and Siebel Server.

  9. Validate that the Siebel CRM application URLs work as expected and verify the application version.

  10. Validate that your application customizations are retained. These customizations were preserved in the backup directory described at the start of this topic. You can manually apply the customizations that you require.

Restoring a Prior Release That Does Not Use the New Installer (Siebel CRM 21.1 or Earlier)

You can restore a prior Siebel CRM installation that does not use the new installer (Siebel CRM 21.1 or earlier). When you updated this prior installation to the current release of Siebel CRM, the backup directory was created with a name like SIEBEL_ROOT_pre22.x.0.0.0, such as SES_pre22.x.0.0.0, for example. This directory, which contains the complete installation, was created at the same level as the existing SIEBEL_ROOT directory. Follow the detailed steps for how to roll back to your prior release.

Note: For a prior installation of Siebel Web Client (from Siebel CRM 20.8 through Siebel CRM 21.1), the backup that was created might be fairly large, because it also includes a full copy of Oracle Database SE2.

To restore a prior release that does not use the new installer (Siebel CRM 21.1 or earlier)

  1. Stop the services for the current release.

  2. Remove the home directories for the current release.

  3. Rename the backup directories to actual home folders. (Backup directories were created as a complete backup when you installed the current release of Siebel CRM to update a prior release.)

  4. As needed, recreate the services for prior versions of Tomcat.

  5. Restore the Siebel database from the backup you made before performing the update installation.

  6. Restore the Siebel Gateway registry from the backup you made before performing the update installation.

  7. Start the services for the prior release.

Related Topics

Siebel CRM Download and Installation

Verifying Installation for Siebel CRM

About Uninstalling Siebel CRM

Process of Removing Configuration Data

Related Books

Siebel System Administration Guide