Contents

 

Upgrade Considerations

 

 

Downloading Installer Files

The most recent up.time Installer packages are available from the Downloads page on the uptime Support site (login required). Note that the up.time 7.2 release uses the same package for both new installations and upgrades.

 

Upgrade FAQ

 

Supported Upgrade Paths

To upgrade to up.time 7.2, you must be running either up.time 7.0 or 7.1. If you are still running an earlier version of up.time, please refer to Upgrading to up.time 7.1 or Earlier and complete your upgrade to up.time 7.0 before proceeding.

 

Version-Specific Upgrade Advisories

up.time 7.0 and Windows: If you are running up.time 7.0 on a Windows Monitoring Station platform, you will need to perform several upgrade steps related to the up.time 64-bit architecture. Please refer to Upgrading a Windows Monitoring Station. in the up.time 7.1 release notes.

up.time 7.0 and Red Hat Enterprise Linux 5.8: up.time 7.0 was not officially supported on Red Hat Enterprise Linux 5.8. However, it is possible that you manually added 64-bit libraries to the RHEL 5.8 Monitoring Station to establish compatibility. If this scenario applies to you, do not attempt to upgrade directly from version 7.0 to 7.2; instead first upgrade to up.time 7.1 before proceeding.

 

Applying up.time Installers

  1. Download the Installer file from the up.time 7.2 Monitoring Station Installer Files (includes up.time Controller) section of the Support site. The current names of the up.time Installer files are listed below

    Note: On earlier up.time versions, there were separate installers for RedHat & SUSE, as well as separate packages for upgrading vs. a full installation. Going forth is now a single installer that covers both versions of Linux, as well both upgrades and full installs.

     

    up.time VersionPlatform & Installer Files
    7.2Windows: up.time-7.2.0-windows.exe
    Linux: up.time-7.2.0-linux.bin.gz
  2. Copy the 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. 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.

    Note: To guarantee full retention of historical performance data, perform a full database backup prior to upgrading using one of the options from the “Backing up & Recovering up.time” KB article.

  5. 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.
  6. Stop the up.time services before executing the Installer.

    For Linux 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"

     

  7. If you've previously installed the separate “up.time Controller” while running up.time 7.1, you will need to manually un-install this before proceeding as the up.time Controller is now integrated into up.time 7.2 and later Installer packages.

    Uninstalling the up.time Controller on Windows:

     1. Open the Programs and Features Control Panel
 2. Select the up.time Controller.
 3. Click Uninstall.
 4. Follow the on-screen prompts.

    Uninstalling the up.time Controller on Linux:

     1. Navigate to the /controller/uninstaller directory
 ( The default up.time install directory is /usr/local/uptime/ )
 2. Run the uninstaller.sh shell script.
  8. Continue to apply the up.time upgrade.
  9. Depending on your specific environment you may need to re-apply certain changes to the config files that were backed up as part of Step #4. Do not just directly re-apply the backed up copies though, as there is various changes to these config files between versions. If you are unsure of what changes to do after the upgrade, please contact up.time Support directly, and provide the PR taken before the upgrade.
  10. If any custom files have been removed, copy them back to their respective folders (e.g. plug-in monitors reside in the uptime scripts folder). Do not overwrite any files that already exist within the scripts directory after the upgrade. Because like the config files, there are intended changes to these files between up.time versions. If you are unsure of what scripts to re-apply after the upgrade, please contact up.time Support directly, and provide of the PR taken before the upgrade.
  11. If your up.time deployment includes a UI instance, please review the additional steps required for Gadgets/Dashboards to work correctly across both instances as outlined in the Release Notes here.