A.2 Restoring the Orchestration Server If the Upgrade Fails

If you use ZENworks Linux Management in your network, you can use it to restore an older version of the Cloud Manager Orchestration Server if an upgrade has failed. This section contains information that can help you roll back a failed upgrade of Cloud Manager Orchestration Server 3.1.5 back to Cloud Manager Orchestration Server 3.1.4.

A.2.1 Requirements

This scenario requires that you have already installed the Cloud Manager 2.1.4 ISO. That is, the 3.1.4 version of the Orchestration Server should be running with exactly the same packages you originally installed and configured.

The scenario also requires that you have a Cloud Manager 2.1.5 ISO on hand. It is important that you enable rollback through ZENworks Linux Management before you actually execute the rollback. ZENworks Linux Management records the changes you make to the RPM database when you enable rollback.

Rollback works only if you previously installed 3.1.4 packages using ZENworks Linux Management. ZENworks Linux Management records data about each package that it installs, deletes, or upgrades.

For more information about using ZENworks Linux Management for rollback, see Reverting to a Previously Installed Software Configuration State in the ZENworks 7.3 Linux Management Administration Guide.

A.2.2 Rollback Procedure Using the rug Command

Use the following steps to roll back a Cloud Manager Orchestration Server 3.13.1.5 upgrade to Cloud Manager Orchestration Server 3.1.4 on SLES 11x machines where the ZENworks Linux Management Daemon is also installed.

  1. Use the following command to make sure that you have the ZENworks Management Daemon installed, with rollback tools enabled.

    rug get rollback

  2. Check repositories to ensure that they are disabled. You want only 3.1.5 upgrades.

    1. Run the following command to list the repositories:

      rug sl

    2. Run the following command to list the catalogs of subscribed repositories:

      rug ca

    3. Run the following command to unsubscribe from each subscribed repository:

      rug unsub “<name_of repository>”

  3. Add a Cloud Manager Orchestration Server 3.1.4 ISO as a repository.

    1. Run the following command, followed by the local path of the ISO, the ftp or http addresses, or the path to the CD or DVD media where the installation source of Cloud Manager Orchestration Server 3.1.4 currently resides.

      rug sa -t zypp <installation_source_of_Orchestration_Server_3.1.5> cmos314

      This command adds the Orchestration Server 3.1.4 repository to the ZENworks Management Daemon. The daemon uses the RPMs in the repository to roll back the server to its former state. For this reason, the repository (the cmos314 shown in the example) must have the same RPM package versions as Orchestration Server 3.1.4.

      For more information about adding repositories, see the ZENworks 7.3 Linux Management Administration Guide.

    2. Run the following command to list and confirm existing repositories:

      rug sl

    3. Run the following command to list and confirm the catalogs of subscribed repositories:

      rug ca

  4. Subscribe to the cmos314 repository.

    1. Run the following command to subscribe to the cmos314 repository:

      rug sub cmos314

    2. Run the following command to list the catalogs and confirm the catalogs of subscribed repositories:

      rug ca

      The new repository shows Yes in the Sub’d (subscribed) column.

    3. Run the following command to list and confirm updates:

      rug lu

      The message, No updates are available, is displayed, which indicates that no new updates to the repository are available–the RPMs match those in the ncm20 catalog.

  5. Add a Cloud Manager 2.1.5 ISO as a repository.

    1. Run the following command, followed by the local path of the ISO, the ftp or http addresses, or the path to the CD or DVD media where the installation source of Cloud Manager 2.1.5 currently resides.

      rug sa -t zypp <installation_source_of_Cloud Manager_2.1.5_Orchestration_Server> cmos315

      This command adds the Orchestration Server 3.1.5 repository to the ZENworks Management Daemon. The daemon uses the RPMs in the repository to roll back the server to its former state. For this reason, the repository (the cmos315 shown in the example) must have the same RPM package versions as Orchestration Server 3.1.5.

      For more information about adding repositories, see the ZENworks 7.3 Linux Management Administration Guide.

    2. Run the following command to list and confirm existing repositories:

      rug sl

    3. Run the following command to list and confirm the catalogs of subscribed repositories:

      rug ca

  6. Subscribe to the cmos315 repository.

    1. Run the following command to subscribe to the cmos315 repository:

      rug sub cmos315

    2. Run the following command to list the catalogs and confirm the catalogs of subscribed repositories:

      rug ca

      The new repository shows Yes in the Sub’d (subscribed) column for both the cmos314 and cmos315 repositories.

    3. Run the following command to list and confirm the updated Orchestration Server 3.1.x packages:

      rug lu

  7. Run the following command to verify that the 3.1.4 Server and the 3.1.4 Agent are in a running state:

    ps ax | grep java

  8. Run the following command to perform the package upgrade (while the server is in a running state).

    rug up

    The upgrade scripts of the Orchestration Server 3.1.5 RPM packages stop the Orchestration Server 3.1.4 and the 3.1.4 Agent before the upgrade, then take a snapshot of the 3.1.4 Server that is required for the upgrade.

  9. When the package upgrade is complete, run the following command to launch the configuration script to upgrade the 3.1.4 Server.

    /opt/novell/zenworks/orch/bin/config

    NOTE:For details on running the configuration script, see Configuring Cloud Manager Orchestration Components in the NetIQ Cloud Manager 2.1.5 Orchestration Installation Guide.

    If the upgrade configuration fails, error information is displayed in the terminal.

    Because of the configuration upgrade failure, you need to use the ZENworks Management Daemon to roll back to the former (that is, the Orchestration Server 3.1.4) running state without losing data.

  10. Run the following command to confirm that Cloud Manager Orchestration Server 3.1.5 packages are installed:

    rpm -qa | grep zos

    Because the Orchestration Server 3.1.5 packages are installed but not configured, you cannot use them to start the Orchestration Server.

  11. Run the follow command to confirm that an instance of the Orchestration Server was created:

    ls /var/opt/novell/zenworks/zos/

    The /agent, /server and /server.save folders should be listed.

  12. Run the following command to launch the ZENworks Linux Management (that is, the ZENworks Management Daemon) for rolling back to Orchestration Server 3.1.4:

    rug ro 1 hour ago

    NOTE:The rollback parameter, 1 hour ago, is conditional: it specifies the state of the packages on the SLES server at a given time in the past. You need to specify the time when you are sure that 3.1.4 packages were installed and running so that you can roll back the current Orchestration Server 3.1.5 packages to Orchestration Server 3.1.4 packages.

  13. Run the following commands to confirm that the system has been rolled back to version 3.1.4 and that a server instance exists:

    rpm -qa | grep zos

    ls /var/opt/novell/zenworks/zos/

  14. Run the following command to start the Orchestration Agent:

    /etc/init.d/netiq-cmosagent start