Configuring after upgrade

To enable disaster recovery

Perform the following tasks after upgrading the primary site:

1. If you have enabled disaster recovery, you will be prompted to re-enable it.
   Type y to enable disaster recovery.
   Wait for the first backup to be complete.
2. After the first backup is complete, scale up the standby site

   If you have scaled down the standby site, perform the following steps to scale it up:

   1. Navigate to helix-on-prem-deployment-manager/utilities/disaster-recovery/dr-scale

   2. Run the following command:

       ./product_scale.sh  up 
3. Upgrade the standby site 

   1. In the new_working_directory/ configs/deployment.config file, update the following values:
      1. Set the values of the following services to yes.
         • _INFRA
         • _PTPOSTGRES
         • _KAFKA
         • _REDIS
         • _RSSO
         • _VICTORIAMETRICS
         • _ELASTICSEARCH
         • _MINIO
      2. For all the BMC Helix ITOM applications 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 the value of MONITOR to yes. 
           Optionally,
           • To use AIOps, set AIOPS_SERVICES to yes.
           • To use Log Analytics, set INTELLI_INT_SERVICES to yes.

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

           Best practice
           To see your licensed product services, navigate to the configs/deployment.config file in the previously deployed version of BMC Helix ITOM.

   2. 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, you will get the following message:
       Completed Helix On-prem Installation.

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

      tail -f logs/deployment.log
4. (Optional) Scale down the standby site 

   After configuring disaster recovery, you can scale down the application pods and keep only the data lake components running on the standby site to save resources. 

   Perform the following steps:

   1. Navigate to helix-on-prem-deployment-manager/utilities/disaster-recovery/dr-scale

   2. Run the following command:

      ./product_scale.sh  down

      Data from the primary site MinIO continues to be replicated onto the standby site MinIO but the applications will not run.

To change the namespace pod security admission to restricted

After the upgrade, the namespace pod security admission must be changed to restricted.

To change the cluster-level pod security admission, run the following command:

Replace <namespace> with the namespace where you deployed BMC Helix IT Operations Management.

To remove the ES MinIO

An ES MinIO is created to save the OpenSearch 1.x data before upgrading to OpenSearch 2.x. For more information, see Backing-up-the-OpenSearch-1-x-data

Perform the following tasks to remove the ES MinIO and other resources used during the OpenSearch upgrade:

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

2. Run the following script to delete the backed ES MinIO data:

   ./es-opensearch-migration.sh cleanup
3. You will be prompted to confirm if you want to delete the PVC used for the OpenSearch migration. 
   Type y. 
   The PVC gets deleted.
   You will get a confirmation message after the MinIO data is cleaned up.

4. To verify that a MinIO is deleted, run the following command:

   kubectl -n <ITOM namespace> get pod | grep minio

   
   Note that the es-minio is deleted, and all the resources used for the OpenSearch upgrade were released.

(Optional) To switch to enterprise F5 NGINX Plus Ingress Controller

Starting with BMC Helix IT Operations Management (BMC Helix ITOM)   version 24.3, we support the enterprise edition of the F5 NGINX Plus Ingress Controller.

You can use either the enterprise edition of the F5 NGINX Plus Ingress Controller or the open-source version.

To switch to the enterprise edition of F5 NGINX Plus Ingress Controller, see Switching-to-enterprise-F5-NGINX-Plus-Ingress-Controller.

To learn more about the F5 NGINX Plus Ingress Controller, see NGINX Ingress Controller.