Upgrade Hyperic Server

Topics marked with * relate to features available only in vFabric Hyperic.

About this page...

This page has instructions for upgrading the Hyperic Server to 4.6. Before performing the steps on this page, see Hyperic Upgrade Processes for information about upgrade options and other steps in the upgrade process.

If you plan to also upgrade your Hyperic Agents to 4.6, and to configure the server and agents for user-managed keystores, see the information in the Upgrade Server and Agent with User-Managed Keystores section of Hyperic Upgrade Processes.

What Happens During Server Upgrade

You upgrade the Hyperic Server using the Hyperic installer, using the upgrade option. (The installer does not upgrade the Hyperic Agent.)

The installer installs a new version of Hyperic Server; it obtains the configuration information from your previous server installation configuration files and configures the new server instance accordingly.

New Properties in vFabric Hyperic 4.6.5

In Hyperic 4.6.5, there are two new properties in server.conftomcat.maxthreads and tomcat.minsparethreads.

If you use Hyperic's internal database, the installer creates a new database instance that contains the data from the existing instance. The new instance has an updated schema, but the PostgreSQL server itself in not upgraded to a new version.

If you use an external database, the installer updates the existing instance.

Upgrade Hyperic Server on Unix-Based Platforms

  1. Stop the current server instance. For example:

    /opt/hyperic/server-4.5.0/bin/hq-server.sh stop
  2. If you use an external Hyperic database, back it up before proceeding.

  3. Archive your old Hyperic Server directory, so that if you want, you can revert to the previous version. For example:

    tar -zcvf hq-server-4.5.0-archive.tgz hq-server-4.5.0-EE
  4. Run the Hyperic installer in upgrade mode. For example:

    /opt/hyperic/hyperic-hq-installer/setup.sh -upgrade
  5. You are prompted to acknowledge the VMware license agreement.

  6. The installer prompts for the path to the previous Hyperic Server instance. Enter the path, for example:

    /opt/hyperic/server-4.5.0
  7. The installer prompts for the path to the new server instance. Enter the path to the directory under which the new server instance will be installed. For example, to install the new instance under your existing Hyperic home directory:

    /opt/hyperic
    • The installer will finish the upgrade.

  8. Start the new server instance. For example:

    /opt/hyperic/server-4.6.0/bin/hq-server.sh start
  9. In vFabric Hyperic, you can set a variety of sizing properties by running the installer with the -updateScale option. For more information, see Scaling Hyperic Server in vFabric Hyperic 4.6.5.

Upgrade Hyperic Server on Windows Platforms

  1. Stop the existing server instance using the Windows Services Control Panel.

  2. Follow the instructions that apply, depending on whether you use the Hyperic built-in database or an external database:

    • If you use the built-in Hyperic database, the upgrade process will migrate your database schema to the latest edition. Note that PostgreSQL itself is not upgraded to the latest version that ships with Hyperic. The database server remains the one installed when you first installed Hyperic Server.

    • If using an external database, back it up.

  3. Archive your previous Hyperic Server directory so that if you wish you can revert to the previous version.

  4. Run the Hyperic installer in upgrade mode:

    c:\hyperic\hyperic-hq-installer\setup.bat -upgrade
  5. You are prompted to acknowledge the VMware license agreement.

  6. The installer prompts for the path to the previous Hyperic Server instance. Enter the full path to your existing server installation, for instance:

    c:\hyperic\server-4.5.0
  7. The installer prompts for the path where the upgrade version should be installed. Enter the path to the directory that will contain the new server installation. For instance, to install the new instance under your existing Hyperic home directory:

    c:\hyperic\
    • The installer will finish the upgrade.

  8. Update the Windows Service with the new version information:

    c:\hyperic\server-4.5.0\bin\hq-server.bat install
  9. Start the upgraded Hyperic Server using the Windows Services Control Panel.

  10. In vFabric Hyperic, you can set a variety of sizing properties by running the installer with the -updateScale option. For more information, see Scaling Hyperic Server in vFabric Hyperic 4.6.5.

Scaling Hyperic Server in vFabric Hyperic 4.6.5

Available only in vFabric Hyperic

Starting in vFabric 4.6.5, you can set an installation profile that sets the values of key server properties to tune the Hyperic Server based on the size of your environment. For information about the effect of setting an installation profile, see About Sizing Profiles in vFabric Hyperic. For instructions on how to set the installation profile for Hyperic Server after installation or upgrade, see Change vFabric Hyperic Server Sizing Profile.

If you manage more than 50 platforms, and have previously tuned the server properties whose values are set by changing the sizing profile, rather than update the server's sizing profile, you may wish to manually change the values of the server properties that are new in Hyperic 4.6.5 — in an upgrade installation tomcat.maxthreads and tomcat.minsparethreads are added to server.conf with values appropriate for managing less than fifty platforms.

Solving Problems with Upgraded Servers with an Oracle Database

If you are upgrading an Hyperic installation with an Oracle backend and you experience any of the following errors during upgrade, follow the steps below to resolve the problem.

Error updating EAM_SERVICE.SERVICE_TYPE_ID: java.sql.SQLException: ORA-02296: cannot enable (HQDBUSER.) - null values found
Error executing statement desc=null SQL=[
ALTER TABLE eam_stat_errors DROP CONSTRAINT rt_errs_fk_rstat CASCADE
] java.sql.SQLException: ORA-02443: Cannot drop constraint - nonexistent constraint

Fix this with these steps:

  1. Restore your database from backup.

  2. Execute this SQL:

    DELETE FROM EAM_SERVICE WHERE SERVICE_TYPE_ID IS NULL;
  3. Re-run the upgrade.