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 Open Distro and ES MinIO

Before running the clean-up script, make sure your application data is migrated from Open Distro to OpenSearch. 

1. To remove the Open Distro and ES MinIO, run the following command:

   ./es-opensearch-migration.sh cleanup
2. You will be prompted to confirm if you want to delete the PVC used by migration MinIO, elasticsearch-events, and elasticsearch-logs.
   Type y.
   All data related to Open Distro and ES MinIO gets deleted.

To remove the PostgreSQL database version 12.9 

Before running the clean-up script, make sure your data is migrated to PostgreSQL database version 15.5. 

1. To remove PostgreSQL database 12.9 and the older version of PVC, run the following command:

   ./patroni-pg-migration.sh cleanup
2. You will be prompted to confirm if you want to delete the PVC used for the PostgreSQL database migration. 
   Type y. 
   The older version of the PVC gets deleted.
3. You will be prompted to confirm if you want to delete the older PostgreSQL database and associated pods.
   Type y. 
   The PostgreSQL 12.9 and the associated pods get deleted.

After the cleanup, you will get the following message:

The cleanup was completed successfully.