Updating Container Backup Support

You can update an existing configuration of Container Backup Support or upgrade the Helm chart for Container Backup Support.

Before you begin

Ensure that you set up the installation variables in the baas-values.yaml file. For instructions, see Setting up installation variables in the baas-values.yaml file.

About this task

For Kubernetes or OpenShift®: To update Container Backup Support at the command line, modify the parameters in the baas-values.yaml file as required for your environment. Then, run the baas-upgrade.sh script to begin the update.

For OpenShift: To update Container Backup Support from the OpenShift web console, modify the parameters in the baas-values.yaml file as required for your environment. Then, log in to the OpenShift web console to complete the update.

Restriction: The baas-upgrade.sh script cannot upgrade the Helm chart from a Helm 2 chart, nor does it upgrade the product from Version 10.1.6 to V10.1.7. The V10.1.6 software cannot be upgraded to V10.1.7 by using the Helm 3 chart. To upgrade from V10.1.6, you must uninstall V10.1.6, and then install V10.1.7 by using the configuration values from V10.1.6. In V10.1.6, the configuration values were set up in the baas-config.cfg file.

The following procedure contains examples for how to change the logging level for Container Backup Support at the command line and from the OpenShift web console.

Procedure

Use one of the following methods to change the logging level for Container Backup Support from INFO to DEBUG.

  • For Kubernetes or OpenShift: Update Container Backup Support by using the command line. This method works in both airgap and online environments.
    1. Edit the baas-values.yaml file that you customized and modify the productLoglevel statement as follows:
      productLoglevel: DEBUG

      Save the file.

    2. Change to the installation directory (~/installer/ibm-spectrum-protect-plus-prod/ibm_cloud_pak/pak_extensions/install).
    3. Copy your custom baas-values.yaml file to the installation directory:
      cp ~/install_vars_dir/baas-values.yaml .
      where install_vars_dir is the directory where you saved your custom baas-values.yaml files.
    4. Issue the following command to update Container Backup Support:
      ./baas-upgrade.sh
    5. After the update is completed, verify the values that you specified by issuing the following command:
      helm3 get values -n baas
      You can also show the revision history by issuing the following command:
      helm3 history ibm-spectrum-protect-plus-prod -n baas
      The output is similar to the following example:
      REVISION  UPDATED                   STATUS      CHART                                 APP VERSION  DESCRIPTION
      1         Mon Nov  9 09:05:11 2020  superseded  ibm-spectrum-protect-plus-prod-1.1.0  10.1.7       Install complete
      2         Tue Nov 10 10:30:12 2020  deployed    ibm-spectrum-protect-plus-prod-1.1.0  10.1.7       Upgrade complete
  • For OpenShift: Update Container Backup Support by using the OpenShift web console. This method works only in an online environment.
    1. Edit the baas-values.yaml that you customized and modify the productLogLevel statement as follows:
      productLoglevel: DEBUG

      Save the file.

    2. Log on to the OpenShift web console as the cluster administrator.
    3. From the Developer perspective in the OpenShift web console, click Helm.
    4. On the Helm Releases page, ensure that the baas project is selected. Then, click the ibm-spectrum-protect-plus-prod release.
    5. On the ibm-spectrum-protect-plus-prod Helm release details page, click Details > Action > Upgrade.
    6. On the Upgrade Helm Release page, paste the contents of the updated baas-values.yaml file to the YAML editor.
    7. Click Upgrade.
    8. Verify that the update has completed by clicking Revision History on the ibm-spectrum-protect-plus-prod release details page.
    9. After the update is completed, go to the command line. At the installation directory (~/installer/ibm-spectrum-protect-plus-prod/ibm_cloud_pak/pak_extensions/install), run the following command to delete any obsolete data mover containers:
      ./baas-delete-dm.sh