Upgrading BMC Helix Platform services version from 22.2.01 to 23.2.02

BMC Helix Platform services upgrade is a pre-requisite for BMC Helix Service Management upgrade. BMC Helix Service Management uses the following services provided by BMC Helix Platform:

• Infrastructure services
• Common services
• BMC Helix Dashboards
• BMC Helix ITSM Insights

Upgrade BMC Helix Platform services from version 22.2.01 to 23.2.02 before you upgrade BMC Helix Service Management.

The following image shows the upgrade process:

Before you begin

• Make sure that you upgrade Helm to version 3.11
• Create a new working directory.
  For example, 23.2.02. 
• Download the deployment manager helix-on-prem-deployment-manager-23.2.02.sh file in the new working directory.
  To download the deployment manager from EPD, see Downloading-the-installation-files.
• Download the Cleanup_Bmchelixlogging.shscript.

• Back up all the PersistentVolumeClaim (PVC) data. 

  Important

  BMC does not have a recommendation for this step. You can use your preferred method to back up the PVC data.

• Run the upgrade configuration utility.
• Uninstall BMC Helix Logging.

To run the upgrade configuration utility

The upgrade configuration utility updates the infra.config and deployment.config files by performing the following tasks:

• It uses the values that you had set during the deployment of BMC Platform services to configure the infra.config and deployment.config files. 
  You need not manually configure any parameter that you had configured previously.
• It lists the configuration parameters whose names have been modified in the current release and updates their values automatically.
• It lists the configuration parameters that were added in the current release.

Perform the following steps to run the upgrade configuration utility:

1. Go to helix-on-prem-deployment-manager/utilities/upgrade.

2. Run the following command to provide execution permission to upgrade-configuration.sh: 

   $chmod a+x ../helix-on-prem-deployment-manager/utilities/upgrade/upgrade-configuration.sh

3. Run the upgrade configuration utility by using the following command:

   ./upgrade-configuration.sh <namespace>

   <namespace> is the name of the namespace that you used to deploy BMC Helix Platform services.
   
   The utility updates the infra.config and deployment.config parameters, updates the modified parameters, and if there are any new additions, it prompts you to enter values.
   After the utility has completed updating the infra.config and deployment.config files, you will get a confirmation message. 

   Important

   The infra.config and deployment.config files are configured based on the values that you had set during the previous installation of BMC Helix Platform services. Make sure that you review the files before upgrading.

To uninstall BMC Helix Logging

In BMC Helix Platform services 23.2.02, BMC Helix Logging (Elasticsearch, Fluent Bit, and Kibana) is deployed in the BMC Helix Platform namespace, and not in a separate namespace. You must clean up the old EFK and deploy the new EFK during the upgrade.

1. Back up logs from Kibana into an a Microsoft Excel file.
   
   1. On the Kibana home page, click .
   2. In the Analytics area, click Discover.
   3. Use a filter to refine your search, click Refresh query.
      
   4. Save your search.
   5. Select Share > CSV Reports.
      
      
   6. Click Generate CSV.
      The system displays a similar message:
      
      
   7. When prompted, click Download report and save the report.
      
      
2. Uninstall BMC Helix Logging.
   
   1. Log in to the system from where you installed BMC Helix Platform services earlier.

   2. Export helm and Kubectl binary path.
      For example:

      export HELM_BIN=/usr/local/bin/helm
      export KUBECTL_BIN=/usr/bin/kubectl
   3. Copy the Cleanup_Bmchelixlogging.sh file to the system.

   4. Clean up the bmc-helix-logging namespace by using the following command: 

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

      <bmc-helix-logging namespace> is the name of the bmc-helix-logging namespace that you used in the 22.2.01 version.

Task 1: To migrate data from Bitnami PostgreSQL to Patroni PostgreSQL

1. Make sure that you have the exec permission on the existing Bitnami PostgreSQL pods.

1. In the configs/deployment.config file, update the following parameters:

   Parameter	Value
   INSTALL_MODE	upgrade
   _PTPOSTGRESS	yes
   INFRA	yes

   Important

   Retain all other values as no in this file.

2. In the commons/certs/secrets.txt file, update the default values of the parameters.
   These values can be the same as added in the previous deployment.

3. Deploy the Patroni PostgreSQL server by running the following command:

   ./deployment-manager.sh

4. On the system where you deployed the Patroni PostgreSQL server, navigate to the utilities/migration directory by using the following command:

   cd helix-on-prem-deployment-manager/utilities/migration
5. In the dbmigration.sh script, specify the Bitnami PostgreSQL password and Patroni PostgreSQL password.
   Bitnami PostgreSQL password is your base PostgreSQL database password and Patroni PostgreSQL password is your new PostgreSQL database password.
   The following image shows an example:
   

1. Run the following command to start the migration:

   ./dbmigration.sh

2. (Optional) View the data migration logs by running the following command:

   ls helix-on-prem-deployment-manager/utilities/migration/logs

   Example output:

   migration.log                 migration.log.20230105122017  migration.log.20230105122415  migration.log.20230105122440  migration.log.20230105123110
   migration.log.20230105121719  migration.log.20230105122308  migration.log.20230105122432  migration.log.20230105122949  migration.log.20230105123850

To troubleshoot migration failure

If the migration fails, perform the following steps:

1. Delete the Patroni PostgreSQL server by running the following command:

   helm delete bmc-pg-ha -n <namespace>

2. Delete the pgdata-postgres-bmc-pg-ha-* PVCs by running the following command:

   kubectl  delete pvc pgdata-postgres-bmc-pg-ha-0 pgdata-postgres-bmc-pg-ha-1 pgdata-postgres-bmc-pg-ha-2 -n <namespace>
3. Rerun the database migration.

Task 2: To upgrade BMC Helix Platform services

1. Navigate to your working directory.

2. In the configs/deployment.config file, make sure that the parameters have following values:

   Parameter	Value
   DEPLOYMENT_SIZE	itsmcompact or itsmsmall If you are installing BMC Helix Platform services in a nonproduction environment, specify the value as itsmcompact. If you are installing BMC Helix Platform services in a production environment, specify the value as itsmsmall.
   INSTALL_MODE	upgrade
   _INFRA	yes
   _PTPOSTGRES	yes
   _KAFKA	yes
   _REDIS	yes
   _RSSO	yes
   _VICTORIAMETRICS	yes
   _ELASTICSEARCH	yes
   _MINIO	yes

3. From the working directory, run the deployment manager to upgrade BMC Helix Platform services by using the following command:

   ./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

Step 4: To scale down the Bitnami PostgreSQL pods

After the upgrade is complete, scale down the Bitnami PostgreSQL pods by using following commands:

Where to go from here

Upgrading-BMC-Helix-IT-Service-Management-to-21-3-06