Upgrading a Multi-Manager configuration

This topic describes how to install a new version of the Manager software on a BMC Database Automation (BDA) environment with several Managers.

Before you begin

You must have previously performed the steps in Preparing-for-upgrade.

Note

Beginning with version 8.6, a feature has been added to the configure/deconfigure megamesh scripts to validate the passwords that are input. This requires that the pg_hba.conf file is set up to allow connections to the postgres from the local host as the megamesh and megamesh_config users.

To ensure that the pg_hba.conf file for each Satellite manager meets these requirements, see step 7b.iv on the Installing-the-Manager-software-in-a-Multi-Manager-configuration topic and make the necessary modifications before upgrading.

To upgrade a Multi-Manager configuration

  1. Perform the following steps on each Satellite Manager in your environment:
    1. Navigate to the directory in which you downloaded the new version .zip file and extract the files.
    2. Use the ps utility to confirm that the following dependent services are running and visible in the process table:
      • postgresql
      • dmanager
      • mtd
      • httpd
    3. Run the following commands:
      export LD_LIBRARY_PATH=/app/clarity/lib
      service mtd stop
      service dmanager stop
      rm /app/clarity/lib/libgcc_s.so.1
    4. Using the remote shell connection to the Satellite Manager, navigate to the directory in which you extracted the new version files and run the upgrade script:
      ./update.sh
      All Satellite Managers must be updated before updating the Content Manager.
  2. Perform the following steps on the Content Manager in your environment:
    1. Navigate to the directory in which you downloaded the new version .zip file and extract the files.
    2. Use the ps utility to confirm that the following dependent services are running and visible in the process table:
      • postgresql
      • dmanager
      • mtd
      • httpd
    3. Run the following commands:
      export LD_LIBRARY_PATH=/app/clarity/lib
      service mtd stop
      service dmanager stop
      rm /app/clarity/lib/libgcc_s.so.1
    4. Using the remote shell connection to the Content Manager, navigate to the directory in which you extracted the new version files and run the upgrade script:
      ./update.sh
  3. Complete the following steps. You will be prompted with instructions for entering password information.
    1. Run /app/clarity/manager_scripts/bin/deconfigure_megamesh on each of the satellites.
    2. Run /app/clarity/manager_scripts/bin/deconfigure_megamesh on the Content manager.
    3. Run /app/clarity/manager_scripts/bin/configure_megamesh on the Content manager.
    4. Run /app/clarity/manager_scripts/bin/configure_megamesh on each of the satellites.

Where to go next

If necessary, update your agents with the latest software.

If necessary, upgrade your Command Line Tools with the latest software.

Related topic

Performing-the-upgrade

 

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