Quick start guide: upgrading to latest version of BMC Helix IT Operations Management


Overview

Upgrading BMC Helix IT Operations Management ensures access to the latest features, security enhancements, and performance optimizations. This guide provides a detailed, step-by-step approach to upgrading an existing deployment of BMC Helix ITOM in an on-premises environment.

Scenario

A system administrator at Apex Global is responsible for maintaining the BMC Helix ITOM environment. To improve performance, security, and compatibility, the administrator needs to upgrade from version 24.4 or 25.1 to version 25.2 while ensuring minimal disruptions and a validated rollback strategy.

The following video (3:05) describes how you can upgrade the BMC Helix IT Operations Management on your premises from older version latest version.

icon_play.pnghttps://youtu.be/sJhSPxjOQIo


Process Overview

The upgrade of BMC Helix ITOM follows a structured approach. The process consists of the following key steps:

1741240660842-559.png

Plan the Upgrade

Before proceeding with the upgrade, ensure the following:

  • Assess System Requirements: Confirm that the existing infrastructure meets the requirements for version 25.2. For more information, see System Requirements.
  • Review Release Notes: Understand changes, deprecated features, and new enhancements. For more information, see Release notes and notices.
  • Develop a Rollback Plan: Define rollback procedures in case of upgrade failure. For more information, see Preparing for upgrade.
  • Verify Licensing and Entitlements: Ensure the appropriate licenses are available for the upgraded version. For more information, see License entitlements.

Prepare for Upgrade

  1. Validate the Current Deployment: Identify the installed version and check system health. For more information, see Deployment Overview.
  2. Backup Important Data:
    • Take a full backup of PersistentVolumeClaim (PVC) data and configuration files.
    • Export database configurations and integrations. For more information, see Restoring data on the standby site.
  3. Upgrade Dependencies:
    • Update Kubernetes and OpenShift to supported versions.
    • Upgrade the NGINX Ingress Controller to a compatible version.
    • Update Helm to the latest supported version.
      For more information, see Upgrading Nginx Ingress Controller.
  4. Prepare Configuration Files:
    • Use the Upgrade Configuration Utility to automatically update infra.config, deployment.config, and secrets.txt. For more information, see Configuration file settings.

Execute the Upgrade

  1. Deploy the Upgrade Package:
    • Download the latest upgrade package from the BMC portal.
    • Extract the package and review the release notes.
  2. Run the Upgrade Script:
    ./deployment-manager.sh
    For more information, see Upgrading BMC Helix IT Operations Management.

  3. Monitor the Upgrade Process:
    • Track upgrade logs for errors and warnings using:
      kubectl logs -f <pod-name>
    • Verify pod statuses using:
      kubectl get pods -n <namespace>
      For more information, see Troubleshooting upgrade issues.

Perform Post-Upgrade Validation

  1. Verify System Health:
  2. Confirm ITOM Service Functionality:
  3. Restore Configurations:
  4. Ensure User Access and Security:
    • Validate role-based access control (RBAC) settings.
    • Ensure all integrations and automation rules function as expected. For more information, see product roles and permissions.

Optimize and Monitor

  • Fine-Tune Configurations: Adjust system settings for optimal performance.
  • Monitor System Performance: Use BMC Helix Dashboards to track system health.
  • Update Documentation: Ensure internal teams are informed about changes.
  • Train Users: Educate administrators and operators about new features and functionality.

By following these steps, System Administrators can efficiently upgrade BMC Helix ITOM with minimal disruptions and maximum efficiency.

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Helix IT Operations Management deployment 25.3