Upgrading BMC Helix IT Operations Management from version 22.4 to 23.1.02

The following image displays the upgrade process at a glance:

Before you begin

Make sure that you have performed all the steps listed in the Preparing-for-upgrade topic.

To uninstall BMC Helix Logging

Unlike earlier versions of BMC Helix ITOM, which required a separate namespace to deploy BMC Helix Logging, starting with version 23.1.02, both BMC Helix ITOM and BMC Helix Logging (Elasticsearch, Fluent Bit, and Kibana) are deployed in the same namespace. Because of the single namespace, you must clean up the old Elasticsearch, Fluentd, and Kibana (EFK) and deploy the new EFK during the upgrade. 

Perform the following steps only if you had deployed BMC Helix Logging:

1. Back up logs from Kibana into a Microsoft Excel file.
   See To export logs to a csv file.
2. Perform the following steps to uninstall BMC Helix Logging (Elasticsearch, Fluentd, and Kibana):
   

   1. Export the Helm and Kubectl binary path:

      export HELM_BIN=/usr/local/bin/helm
      export KUBECTL_BIN=/usr/bin/kubectl
   2. Download the Cleanup_Bmchelixlogging.shscript to clean up the bmc-helix-logging namespace.
      The Cleanup_Bmchelixlogging.sh script deletes the PVC, pods, and jobs from the bmc-helix-logging namespace.
      
      

   3. Run the command to clean up the bmc-helix-logging namespace:

      ./Cleanup_Bmchelixlogging.sh <bmc-helix-logging namespace>

      <bmc-helix-logging namespace> is the name of the bmc-helix-logging namespace that you used in BMC Helix ITOM 22.4 version.
      
      

3. Perform the task listed in the Preparing to collect logs by enabling BMC Helix Logging topic.

To upgrade BMC Helix IT Operations Management

1. In the new_working_directory/configs/deployment.config file, make sure that your deployment size is the same as your previous deployment size; for example, small, compact, medium, or large.
   To confirm your deployment size, see the value set for the DEPLOYMENT_SIZE parameter in the configs/deployment.config file in BMC Helix ITOM version 22.4.
2. In the new_working_directory/configs/deployment.config file, update the following values:
   1. Set the value of INSTALL_MODE to upgrade.
   2. Set the values of the following infrastructure services to yes.
      • _INFRA
      • _PTPOSTGRES
      • _KAFKA
      • _REDIS
      • _RSSO
      • _VICTORIAMETRICS
      • _ELASTICSEARCH
      • _MINIO
   3. For the product services for which you are licensed, set the value to yes; for all other services, set the value to no.
      For example, if you are only licensed to use BMC Helix Operations Management and BMC Helix Continuous Optimization:
      • To use BMC Helix Operations Management, set value of AIOPS_SERVICES, MONITOR, and INTELLI_INT_SERVICES to yes.

      • To use BMC Helix Continuous Optimization, set the value of OPTIMIZE to yes. 

        Best practice
        To see the product services for which you are licensed, see the configs/deployment.config file in BMC Helix ITOMversion 22.4.

3. From the new working directory (new_working_directory) run the deployment manager to upgrade BMC Helix IT Operations Management:

   ./deployment-manager.sh

   After the upgrade is complete, you will get the following message:
   Completed Helix On-prem Installation.

4. (Optional) To view the logs during the upgrade, run the following command:

   tail -f logs/deployment.log
5. If you had deployed BMC Helix IT Operations Management in a multitenant environment, follow the steps to restore the smart-graph-tenant-config configmap and its content:
   1. Copy the contents from the smart-graph-tenant-config configmap file that you backed up before the upgrade.

   2. Run the command to open the smart-graph-tenant-config configmap:

      kubectl -n <namespace> edit cm smart-graph-tenant-config

   3. Paste the contents that you copied from the backed-up smart-graph-tenant-config configmap file in the new smart-graph-tenant-config configmap and save it.

   4. Run the following command to restart the smart graph controller pod: 

      kubectl rollout restart deploy/smart-graph-controller -n <namepsace>

Performing post upgrade task

(Optional) Upgrade your orchestration platform. 
To know more about the supported versions of the orchestration platform, see System requirements.