articleUpgrading to up.time 7.2 and 7.3


Upgrade Considerations

  • Verify that your monitoring station can access the following page so it will be able to install new plugins and upgrade existing plugins:
  • If you are upgrading from up.time 7.0, the Monitoring Station may not be a 64-bit platform. Please refer to Supported Monitoring Station Platforms in up.time for a list of officially supported platforms. If you are upgrading from up.time 7.1, you are already on a 64-bit platform.
  • If you are upgrading from up.time 7.0 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.
  • up.time Virtual Appliance upgrades are not currently supported.

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 up.time 7.2 and later releases use the same package for both new installations and upgrades.

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, Installers 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 up.time Installer in order or do they include all previous updates? A: Upgrades include all previously released functionality; however, there is a specific list of supported upgrade paths. Please review the Supported Upgrade Paths section below for further details on the correct order to install up.time packages.
  • Q: Can I install a test environment prior to upgrading my production environment? A: Yes, this process is recommended. Please contact uptime Support to request a test license key.

Supported Upgrade Paths

The officially supported up.time upgrade paths are listed below:

  • 7.1 -> 7.2
  • 7.1 -> 7.3
  • 7.2 -> 7.3

If you are running up.time 6.x or earlier, 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.

up.time 7.3 and the 'Enhanced Alert Profile Variables': As part of the new features added in up.time 7.3, the 'Enhanced Alert Profile Variables' plugin is no longer needed, and will need to be removed after the upgrade. See the up.time 7.3 Release Notes -Upgrade Notices for more details.

Applying up.time Installers

  1. Download the Installer file from the up.time 7.3 Monitoring Station Installer Files 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 installer packages for RedHat & SUSE, as well as separate packages for upgrading and new installation. There is now a single installer that covers both versions of Linux, as well both upgrades and new installs.

    up.time VersionPlatform & Installer Files
    7.3 Windows: up.time-7.3.0-windows.exe
    Linux: up.time-7.3.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.
    • Generate a Problem Report with full configuration data.
      • From within the up.time web UI, navigate to the Config tab & select ‘Problem Reporting’ from the left side menu.
      • Make sure the box for “Include configuration and service monitor status history for the past” is checked.
      • Change the default option of 3 months of configuration data to 120 months.
      • Click ‘Generate Report’ and wait for the Problem Report to complete.
      • Download and make a copy of the resulting .zip file somewhere other than the Monitoring Station.
    • The problem report will make a copy of all the various config files & configuration data used by up.time. But you should also back up the following files/directories as these may be overwritten during the upgrade process.
      • Any Scripts or Plugin Monitors configured on the Monitoring Station. These are typically located in subdirectories in the <uptime_dir>/scripts/ directory (e.g. <uptime_dir>/scripts/MonitorLogScanner).
      • Any custom Dashboards downloaded from the Grid, which are typically located as sub-directories in the <uptime_dir>/GUI/ directory (e.g. <uptime_dir>/GUI/mobile or <uptime_dir>/GUI/world_map).
      • If you made any customizations to the <uptime_dir>/logging.conf file, this will needed to be backed up, as the file has been revised in up.time 7.3.

    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_controller stop
    # /etc/init.d/uptime_datastore stop

    For Windows installations, run the following:

    > net stop "up.time Web Server"
    > net stop "up.time Controller"
    > net stop "up.time Data Collector"
    > net stop "up.time Data Store"
  7. If you have previously installed the separate up.time Controller while running up.time 7.1, you will need to manually un-install it before proceeding as the up.time Controller is now integrated in 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 shell script.
  8. Continue to apply the up.time upgrade.
    • For Linux installations, run the following commands.
      Note: On earlier up.time versions, there were separate installers for Redhat & SUSE, as well as separate packages for upgrading and new installation. There is now a single installer that covers both versions of Linux, as well both upgrades and new installs.
      # cd /to/your/upgrade/file/path
      # gunzip -d up.time-7.3.0-linux.bin.gz
      # chmod +x up.time-7.3.0-linux.bin
      # ./up.time-7.3.0-linux.bin

      Follow the directions presented during the upgrade script.

    • Windows installations; Right click on the installer, and click on Run As Administrator. This will ensure that the installer runs as a local administrator account and has the required permissions.
  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 as there are various changes to these config files between versions. If you are unsure of which changes to apply 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 as there are intended changes to these files between up.time versions. If you are unsure of which scripts to re-apply after the upgrade, please contact up.time Support directly, and provide 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.

Related Articles

Upgrading to up.time 7.1 or Earlier


By: uptime Support | Date Created: 8-9-2013 | Last Modified: 8-12-2013 | Index: 599


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


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


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


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


Integrating up.time NetFlow with up.time


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


Monitoring WebSphere with up.time


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


User Comments

No comments have been posted.

Copyright © 2021 IDERA, Inc.   Legal   Privacy Statement