Upgrade

From ITOM Practitioner Info
Jump to: navigation, search

These are the steps to perform an upgrade from OBA 3.03 to OBA 3.04.

Upgrading from OBA 3.00/3.02 to 3.04 is not supported. You must first upgrade older systems to OBA 3.03 as described in the OBA 3.03 Install section, and then upgrade 3.03 to 3.04.

To upgrade from OBA 3.03 to OBA 3.04, do the following:

  1. Prepare for the upgrade

    With the upgrade to OBA 3.04, database changes are required. To minimize the downtime, a temporary table is created and the data is migrated.

    1. Make sure that all OBA processes are running.

    2. Copy the OBA installation files to the OBA application servers and collectors.

    3. Extract the installation file OBA_3.04_Analytics_Installation.zip to <tmp>. <tmp> can be any directory you choose.

    4. As the root user, execute the following commands on the OBA application server host:

      Make sure that the database preparation is done only once.

      cd <tmp>/Analytics_Installation
      

      Install the new Vertica Client.

      rpm -U packages/vertica-client-8.1.1-0.x86_64.rpm

      Start the upgrade.

      ./upgrade_oba303_to_oba304.sh -h <DATABASE_HOST_NAME> -p 5433 -u dbadmin -w <DATABASE_PASSWORD> -n opsadb prepare
      

      Wait until the script execution has finished.

  2. Shut down all processes

    With the following steps, the OBA downtime starts.

    1. As the root user, shut down all OBA processes on the OBA application server and all OBA collectors:

      /opt/HP/opsa/bin/opsa stop
      
    2. Verify that the processes were successfully stopped by running the following command:

      /opt/HP/opsa/bin/opsa status
      
    3. As root user, stop the Operations Agent on the OBA application server and all OBA collectors:

      /opt/OV/bin/opcagt -stop
      /opt/perf/bin/ovpa stop
      /opt/perf/bin/ttd -k
      /opt/OV/bin/ovc -kill
      
    4. Verify that the processes were successfully stopped by running the following commands:

      /opt/OV/bin/opcagt -status
      /opt/OV/bin/ovc -status
      

      Continue when all processes are shown as stopped. You may need to use the kill command, or even kill -9, to ensure all processes have fully exited.

      Vertica must be up and running for the next upgrade steps.

  3. Upgrade to OBA 3.04

    1. As the root user, execute the following commands on the OBA application server:

      cd <tmp>/Analytics_Installation
      
      ./upgrade_oba303_to_oba304.sh -h <DATABASE_HOST_NAME> -p 5433 -u dbadmin -w <DATABASE_PASSWORD> -n opsadb upgrade
      
    2. Run the following command on the OBA application server:

      ./upgrade_oba303_to_oba304.sh -h <POSTGRES_HOST> pg_upgrade
      

      The <POSTGRES_HOST> is 'localhost' on the OBA application server.

      Enter the passwords for the PostgreSQL users. The set passwords are used by OBA processes to access the PostgreSQL configuration database.

    3. As the root user, execute the following commands on all OBA collectors:

      cd <tmp>/Analytics_Installation
      
      ./upgrade_oba303_to_oba304.sh -h <DATABASE_HOST_NAME> -p 5433 -u dbadmin -w <DATABASE_PASSWORD> -n opsadb upgrade
      
  4. Complete the upgrade

    With the following steps, the OBA downtime ends.

    Run the following commands first on the OBA server and then on all OBA collectors.

    1. As the root user, start all Operations Agent processes:

      /opt/OV/bin/ovc -start
      /opt/OV/bin/opcagt -start
      /opt/perf/bin/ovpa start
      
    2. Verify that the Operations Agent processes were successfully started by running the following command:

      /opt/OV/bin/opcagt -status
      

      The perfalarm process might not run. This is normal and can be ignored.

    3. As the root user, restart all OBA processes:

      /opt/HP/opsa/bin/opsa start
      
    4. Verify that the processes were successfully started by running the following command:

      /opt/HP/opsa/bin/opsa status
      
    5. When all processes are shown as running, execute the same steps on all OBA collectors.

  5. Resubmit the Storm Topology

    Due to improvements in OBA 3.04 and to ensure product reliability, you have to resubmit the Storm Topology.

    As the opsa user, run the following command on the OBA application server:

    /opt/HP/opsa/sbin/opsa-storm-resubmit-topology.sh
    

    Ignore the error for opsa-anomaly-detection if it occurs. This can be ignored and has no consequences.

    Wait until the script execution has finished.

  6. Refresh the Browser cache

    On the client side, refresh the browser cache to make sure that the UI is shown correctly.

    In the browser:

    1. On the OBA login screen, refresh the browser by pressing 'Ctrl + F5'

    2. After the login, refresh the browser again by pressing 'Ctrl + F5'

  7. Validate the upgrade

    Ensure that the OBA collections are all working and that the functionality inside the OBA UI works as expected. If you experience any issues with OBA 3.04, contact support.

  8. Perform the upgrade clean-up

    A roll back to OBA 3.03 is not possible after you complete the clean up.

    After everything has been validated and the system is running fine, clean up the obsolete database tables. As the root user, run the following commands on an OBA application server:

    cd <tmp>/Analytics_Installation
    
    ./upgrade_oba303_to_oba304.sh -h <DATABASE_HOST_NAME> -p 5433 -u dbadmin -w <DATABASE_PASSWORD> -n opsadb cleanup