If you use ZENworks Linux Management in your network, you can use it to restore an older version of the ZENworks Orchestrator Server if an upgrade has failed. This section contains information that can help you roll back a failed upgrade of PlateSpin Orchestrate 2.0 back to ZENworks Orchestrator 1.3.
This scenario requires that you have already installed the ZENworks Orchestrator 1.3 ISO. That is, the 1.3 version of the Orchestrator Server should be running with exactly the same packages you originally installed and configured.
The scenario also requires that you have a PlateSpin Orchestrate 2.0 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 ZENworks Orchestrator 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.2 Linux Management Administration Guide.
Use the following steps to roll back a PlateSpin Orchestrate 2.0 upgrade to ZENworks Orchestrator 1.3
Make sure that you have the ZENworks Management Daemon installed, with rollback tools enabled.
rug get rollback
Check repositories to ensure that they are disabled. You want only ZENworks Orchestrator upgrades.
Run the following command to list the repositories:
rug sl
Run the following command to list the catalogs of subscribed repositories:
rug ca
Run the following command to unsubscribe from each subscribed repository:
rug unsub “<name_of repository>”
Add a ZENworks Orchestrator 1.3 Server ISO as a repository.
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 ZENworks Orchestrator 1.3 currently resides.
rug sa -t zypp <installation_source_of_Orchestrator_1.3_Server> zos13
This command adds the Orchestrator 1.3 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 zos13 shown in the example) must have the same RPM package versions as ZENworks Orchestrator 1.3.
For more information about adding repositories, see the ZENworks 7.2 Linux Management Administration Guide.
Run the following command to list and confirm existing repositories:
rug sl
Run the following command to list and confirm the catalogs of subscribed repositories:
rug ca
Subscribe to the zos13 repository.
Run the following command to subscribe to the zos13 repository:
rug sub zos13
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.
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 zos12 catalog.
Add a PlateSpin Orchestrate 2.0 Server ISO as a repository.
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 PlateSpin Orchestrate 2.0.2 currently resides.
rug sa -t zypp <installation_source_of_PS_Orchestrate_2.0.2_Server> pso20
This command adds the PlateSpin Orchestrate 2.0 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 pso20 shown in the example) must have the same RPM package versions as PlateSpin Orchestrate 2.0.2.
For more information about adding repositories, see the ZENworks 7.2 Linux Management Administration Guide.
Run the following command to list and confirm existing repositories:
rug sl
Run the following command to list and confirm the catalogs of subscribed repositories:
rug ca
Subscribe to the pso20 repository.
Run the following command to subscribe to the pso20 repository:
rug sub pso20
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 zos13 and pso20 repositories.
Run the following command to list and confirm the updated PlateSpin Orchestrate 2.0.2 packages:
rug lu
Run the following command to verify that the Orchestrator Server and the Orchestrator Agent are in a running state:
ps ax | grep java
Run the following command to perform the package upgrade (while the server is in a running state).
rug up
The upgrade scripts of the PlateSpin Orchestrate 2.0 RPM packages stop the Orchestrator Server and the Orchestrator Agent before the upgrade, then take a snapshot of the Orchestrator Server that is required for the upgrade.
When the package upgrade is complete, run the following command to launch the configuration script to upgrade the Orchestrator Server.
/opt/novell/zenworks/orch/bin/config
NOTE:For details on running the configuration script, see Installation and Configuration Steps
in the PlateSpin Orchestrate 2.0 Installation and Configuration 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 ZENworks Orchestrator 1.3) running state without losing data.
Run the following command to confirm that PlateSpin Orchestrate 2.0 packages are installed:
rpm -qa | grep zos
Because the 2.0.2 packages are installed but not configured, you cannot use them to start the Orchestrate Server.
Run the follow command to confirm that an instance of the Orchestrate Server was created:
ls /var/opt/novell/zenworks/zos/
The agent, server and server.save folders should be listed.
Run the following command to launch the ZENworks Linux Management (that is, the ZENworks Management Daemon) for rolling back to ZENworks Orchestrator 1.3.
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 Orchestrator 1.3 packages were installed and running so that you can roll back the current Orchestrate 2.0 packages to Orchestrator 1.3 packages.
Run the following commands to confirm that the system has been rolled back to version 1.3 and that a server instance exists:
rpm -qa | grep zos
ls /var/opt/novell/zenworks/zos/
Run the following command to start the ZENworks Orchestrator and ZENworks Orchestrator Agent:
/etc/init.d/novell-zosagent start