article Upgrading to up.time 7.1 or Earlier

Contents

Note: This KB article only applies if you are upgrading to up.time version 7.1 or earlier. If you are upgrading to up.time 7.2 or later, please refer to Upgrading to up.time 7.2 or Later

Upgrade Considerations

NOTE: If you are upgrading to up.time 7.1, your monitoring station platform must be a 64-bit architecture with a 64-bit Operating System. Please refer to Supported Monitoring Station Platforms in up.time for a list of officially supported platforms.

NOTE: If you are upgrading to up.time 7.1 and running the up.time Monitoring Station on a Windows server, please refer to Upgrading a Windows Monitoring Station in the up.time 7.1 Release Notes.

NOTE: If you are upgrading to up.time 7.1 and using the uptime Plug-in Manager, you will also need to upgrade the Plug-in Manager. Please visit the Plug-in Manager page on the uptime Grid for details.

NOTE: When upgrading from 5.x to 6.x or 6.x to 7.0, you must retrieve a new license key from the license portal. When upgrading to 7.0, you must retrieve your license key prior to attempting your upgrade.

NOTE: up.time Virtual Appliance upgrades are not currently supported.

Please contact uptime Support prior to attempting an upgrade if any of the following conditions applies:

  • You are attempting to upgrade to up.time 6.x and your deployment utilizes an MDC configuration.
  • You are attempting to upgrade to up.time 6.x or 7.x and you have configured DataStore table partitioning.
  • You are attempting to upgrade to up.time 6.x and are using up.time to monitor VMware virtual machines without also having added the corresponding ESX host(s) to up.time.
  • You are attempting to upgrade to up.time 5.3 or later from a deployment that has previously been upgraded from up.time 4.x.

Downloading Upgrade Files

The most recent up.time upgrade package is available from the download section of the Support site (login required).

NOTE: Ensure that you download your service pack upgrade from the Upgrade Installer section and not a full monitoring station installation package.

Please contact the uptime Support team if you require older versions of up.time service packs.

Upgrade FAQ

  • Q: Do I need to upgrade my agents? A: Agent updates are generally not required unless specifically noted in the version release notes.
  • Q: Can I roll back an upgrade? A: No, upgrades are not designed for rollback capability. Upgrade failures are rare but it is very important to stop all up.time services and backup your configuration before proceeding with any upgrade.
  • Q: How long will an upgrade take? A: Upgrades can generally be applied in less than 30 minutes.
  • Q: Do I need to install each service pack in order or do up.time upgrades include all previous updates? A: Upgrades include all previously released functionality; however, there is a specific list of supported upgrade paths. Please review the following section for further details on the correct order to install service packs.
  • Q: Can I install a test environment prior to upgrading my production environment? A: Yes, this process is recommended. To retrieve a test license key, login to the License Portal and click the Test Drive link for your deployment.

Supported Upgrade Paths

The officially supported up.time upgrade paths are listed below. Please note that the general rule is that you should not skip more than one point release when applying service packs. For example, upgrading from up.time 5.2 to 5.4 is possible but upgrading from up.time 5.2 to 5.5 is not supported.

  • 5.2 -> 5.3
  • 5.2 -> 5.4
  • 5.3 -> 5.4
  • 5.3 -> 5.5
  • 5.4 -> 5.5
  • 5.4 -> 6.x
  • 5.5 -> 6.x
  • 6.x -> 7.0
  • 7.0 -> 7.1

Applying up.time Upgrades and Service Packs

  1. Download the upgrade or service pack file from the Upgrade Installer section of the Support site. The current up.time upgrade installer file names are listed below (please contact uptime Support if you require an older service pack version to facilitate an interim upgrade).
    Service PackPlatform & Filename
    7.1 Windows: up.time-7.1.0-windows.exe
    Red Hat: up.time-7.1.0-rhes-upgrade.bin.gz
    SuSE: up.time-7.1.0-sles-upgrade.bin.gz
    Solaris: up.time-7.1.0-solaris-sparc-upgrade.bin.gz
  2. Copy the upgrade installer file to your monitoring station. If using FTP, ensure you use binary mode.
  3. Review the version release notes for any specific upgrade instructions.
  4. If you are upgrading to a new major release version (e.g. from 5.x to 6.x or from 6.x to 7.0), you will need to retrieve a new license key from the License Portal (login required). To complete this process, login to the License Portal, identify the Deployment that you plan to upgrade, select the "Upgrade my Deployment link" and follow the instructions.
  5. Back up your current up.time deployment. We recommend at least the following steps, which will back up the configuration information but not the historical performance data. Please review Backing up & Recovering up.time for additional backup suggestions.
    • Generate a Problem Report by navigating to the Config -> Problem Reporting tab. This will generate a copy of your configuration.
    • Copy <install_dir>/wrapper.conf (Windows systems only)
    • Copy <install_dir>/uptime.conf
    • Copy <install_dir>/uptime.lax (all non-Windows systems)
    • Copy <install_dir>/mysql/my.ini (if running on the default MySQL DataStore)
    • Copy <install_dir>/apache/conf/httpd.conf
    • Copy <install_dir>/apache/conf/php.ini
    • Back up any scripting files related to plug-in monitors, custom actions, custom alerts or custom monitors.
  6. Note: To guarantee full retention of historical performance data, perform a full database backup prior to upgrading.

  7. Log out of the up.time User Interface before proceeding with the upgrade. Note that if this step is not followed, you may receive a Database is Not Responding error when attempting to restart up.time after the upgrade.
  8. Stop the up.time services before executing the Service Pack.

    For Red Hat, SUSE, and Solaris installations, run the following:

    # /etc/init.d/uptime_httpd stop
    # /etc/init.d/uptime_core stop
    # /etc/init.d/uptime_datastore stop

    For Windows installations, run the following:

    > net stop "up.time Web Server"
    > net stop "up.time Data Collector"
    > net stop "up.time Data Store"
  9. Continue to apply the up.time upgrade.
    • For Red Hat, SUSE and Solaris installations, run the following commands.
      Note that this example assumes a 7.1 Red Hat upgrade so substitute your file name as appropriate.
      # cd /to/your/upgrade/file/path
      # gunzip -d up.time-7.1.0-rhes-upgrade.bin.gz
      # chmod +x up.time-7.1.0-rhes-upgrade-bin
      # ./up.time-7.1.0-rhes-upgrade.bin

      Follow the directions presented during the upgrade script.

    • Windows installations; double click on the service pack upgrade executable and follow the instructions on screen.
  10. Depending on your specific environment you may need to reapply certain changes to the httpd.conf, wrapper.conf, php.ini and/or uptime.conf files. Confirm that these files are correct by comparing to your backup copies.
  11. Note that after upgrading to up.time 7.0, users should update the global SNMP settings found on the Config panel (please refer to the Release Notes for further details).
  12. Note that several new parameters were added or moved to the uptime.conf file in the 5.5 release to simplify and facilitate tuning of performance parameters. If these parameters were previously modified in your wrapper.conf or uptime.lax file, you will need to reapply those changes to the uptime.conf file after upgrading to the 5.5 (or later) release.
  13. If any custom files have been removed, copy them back to their respective folders (e.g. plug-in monitors reside in the uptime core folder). Ensure that any custom monitors, custom alerts, custom actions, or plug-in service monitors are compatible with the new service pack.

Related Articles


Upgrading to up.time 7.2 and 7.3

RatingViews
article

By: uptime Support | Date Created: 10-25-2005 | Last Modified: 5-20-2014 | Index: 033

  22607

Login screen returns Database not responding error after upgradin...

RatingViews
article

If you did not log out of the up.time UI before upgrading to up.time 6.0.1 (refer to step 6 of Upgrading and Applying up.time Service Packs), you may see the following error after attempting to...

By: uptime Support | Date Created: 12-21-2011 | Last Modified: 8-14-2013 | Index: 572

  1640

'Default up.time data store' monitor crit after adding a vCenter ...

RatingViews
article

As part of the initial install of up.time, the Monitoring Station itself is setup as an element within up.time. This sample element is initially setup to use localhost as it's hostname, along...

By: uptime Support | Date Created: 3-8-2013 | Last Modified: 3-8-2013 | Index: 592

  1893

Integrating up.time NetFlow with up.time

RatingViews
article

Learn how to configure up.time to point to your Scrutinizer instance to enable click-through graphing, as well as an integrated Scrutinizer view from Global Scan.

By: uptime Support | Date Created: 7-8-2010 | Last Modified: 2-8-2013 | Index: 459

  4549

Monitoring WebSphere with up.time

RatingViews
article

Use up.time to monitor the performance and health of Java applications running on WebSphere servers.

By: uptime Support | Date Created: 12-20-2006 | Last Modified: 7-26-2011 | Index: 108

  4764

User Comments



No comments have been posted.

Copyright © 2016 IDERA, Inc.   Legal   Privacy Statement