Rolling back the upgrade on Linux

Follow these steps if you are using IBM® Spectrum Symphony on Linux®. Note that you should consider rolling back to the upgraded 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.

• Follow these steps when your cluster is installed to a local file system:
  1. Log on to your primary host as root, or as the cluster administrator with root access (by setting egosetsudoers.sh to grant root privileges to the cluster administrator), ensure that your cluster has started, and source the upgrade environment (especially if you plan to upgrade the host after rollback):
     • (csh) source $EGO_TOP/upgrade/conf/cshrc.upgrade
     • (bash) . $EGO_TOP/upgrade/conf/profile.upgrade
  2. Run the cluster rollback command:

     egoupgrade rollback cluster [-f] [-u user_account] [-x password]

     For syntax usage and details, see ../reference_sym/egoupgrade.html#reference_gxz_5nk_pw.
  3. Source the environment:
     • (csh) source $EGO_TOP/cshrc.platform
     • (bash) . $EGO_TOP/profile.platform
  4. Complete this step only to remove IBM Spectrum Symphony 7.3.2 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 user account that you used to upgrade IBM Spectrum Symphony, source the upgrade environment, 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 ../reference_sym/egoupgrade.html#reference_gxz_5nk_pw.
     2. Source the environment:
        • (csh) source $EGO_TOP/cshrc.platform
        • (bash) . $EGO_TOP/profile.platform
     3. Repeat steps 3a and 3b on your management hosts. Log on to the host using the same user account that you used to upgrade IBM Spectrum Symphony.
     4. Repeat steps 3a and 3b on your primary candidate hosts. Log on to the host using the same user account that you used to upgrade IBM Spectrum Symphony.
     5. Repeat steps 3a and 3b on your primary host. Log on to the host using the same user account that you used to upgrade IBM Spectrum Symphony.
• Follow these steps when your cluster is installed to a shared file system (installing on a shared file system is supported on Linux):
  1. Log on to your primary host as root, or as the cluster administrator with root access (by setting egosetsudoers.sh to grant root privileges to the cluster administrator), ensure that your cluster has started, and source the upgrade environment:
     • (csh) source $EGO_TOP/upgrade/conf/cshrc.upgrade
     • (bash) . $EGO_TOP/upgrade/conf/profile.upgrade
  2. Run the cluster rollback command:

     egoupgrade rollback cluster [-f] [-u user_account] [-x password]

     For syntax usage and details, see ../reference_sym/egoupgrade.html#reference_gxz_5nk_pw.
  3. If you must completely remove the configuration for your upgraded version, log on to any compute host in your cluster, source the upgrade environment, and run the host rollback command:

     egoupgrade rollback host [-f]

     For syntax usage and details, see ../reference_sym/egoupgrade.html#reference_gxz_5nk_pw.
  4. Source the environment:
     • (csh) source $EGO_TOP/cshrc.platform
     • (bash) . $EGO_TOP/profile.platform
  5. Restart EGO on the local host:

     egosh ego shutdown
     egosh ego start

  6. On all other compute hosts in your cluster, complete these steps:
     1. Source the environment:
        • (csh) source $EGO_TOP/cshrc.platform.comp
        • (bash) . $EGO_TOP/profile.platform.comp
     2. Restart EGO on the host:

        egosh ego shutdown
        egosh ego start

     Note: If you have more than one shared locations (for example, a separate share for management hosts and another for compute hosts), you manually updated the profile.platform.comp (or cshrc.platform.comp file when using CSH) on compute hosts. After you rollback your upgrade, before you source the environment, you must also edit the profile.platform.comp (cshrc.platform.comp) file to use the upgraded product version.
  7. Repeat steps 4 and 5 on all management hosts in your cluster.
  8. Repeat steps 4 and 5 on the primary host in your cluster.