Rolling back the upgrade on Windows

Follow these steps if you are using IBM® Spectrum Symphony on Windows. Note that you should consider rolling back to the previous version only if you encounter serious issues (for example, if key functionality is broken or if your applications fail to work). If possible, try changing the application to fix the issue rather than rolling back the upgrade.

Before you begin

Before rolling back your upgrade, ensure you stop all workload.

About this task

During a roll back, the order of the rolling upgrade process is reversed. You roll back your cluster-level upgrade and then the host-level upgrade. Typically, you may not need to roll back the upgrade on your hosts as well. If you must do this, first roll back the cluster, then roll back the individual hosts in reverse order of the upgrade.

Procedure

  1. Log on to your primary host using the same installation user operating system account that you used to upgrade IBM Spectrum Symphony and run the cluster rollback command: 
    egoupgrade rollback cluster [-f] [-u user_account] [-x password]
    For syntax usage and details, see egoupgrade.
  2. Complete this step only to remove the upgraded version of IBM Spectrum Symphony from your hosts. Typically, after upgrading your hosts, you test that your host works properly before upgrading the cluster-level configuration. Therefore, it is unlikely that you need to roll back the hosts to your previous version of IBM Spectrum Symphony. However, if you must completely remove your upgraded version of IBM Spectrum Symphony from each host, complete these steps:
    1. Log on to each of your compute hosts using the same installation user operating system account that you used to upgrade IBM Spectrum Symphony, and run the host rollback command: 
      egoupgrade rollback host [-f]
      Note: If you run this command to roll back the upgrade on the local compute host, be aware that IBM Spectrum Symphony applications that require updated features cannot run on the compute host.
      For syntax usage and details, see egoupgrade.
    2. Repeat step 2a on your management hosts. Log on to the host using the same installation user operating system account that you used to upgrade IBM Spectrum Symphony.
    3. Repeat step 2a on your primary host. Log on to the host using the same installation user operating system account that you used to upgrade IBM Spectrum Symphony.

Results

The upgraded IBM Spectrum Symphony configurations (including users and custom user roles, consumers, resource groups, resource plans, or custom reports; and enabled features) are rolled back to your previous IBM Spectrum Symphony environment.

What to do next

Once you have rolled back the cluster, to continue to use the WEBGUI service on your previous version of IBM Spectrum Symphony, copy the wsm.exe file from the IBM Spectrum Symphony 7.3.2 environment to the previous environment:
  1. Back up the Installation_top\previous_EGO_version\etc\wsm.exe file.
  2. Copy the Installation_top\4.0\etc\wsm.exe file to the Installation_top\previous_EGO_version\etc directory (to replace the old wsm.exe file).
  3. Restart the WEBGUI or the REST service: 
    egosh service stop WEBGUI
egosh service start WEBGUI
    egosh service stop REST
egosh service start REST
Note that if you will run rerun the 7.3.2 upgrade on the primary host, first run:
set ENTITLEMENTFILE=entitlement_file_path
This command specifies the path of the entitlement file for the upgraded version; you can then rerun the host upgrade command:
egoupgrade host [-f]