Page History

...

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 Pack	Platform & 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.
   1. Generate a Problem Report by navigating to the Config -> Problem Reporting tab. This will generate a copy of your configuration.
   2. Copy <install_dir>/wrapper.conf (Windows systems only)
   3. Copy <install_dir>/uptime.conf
   4. Copy <install_dir>/uptime.lax (all non-Windows systems)
   5. Copy <install_dir>/mysql/my.ini (if running on the default MySQL DataStore)
   6. Copy <install_dir>/apache/conf/httpd.conf
   7. Copy <install_dir>/apache/conf/php.ini

   8. Back up any scripting files related to plug-in monitors, custom actions, custom alerts or custom monitors.

      Note
      title

...

1. 1. Note

      To guarantee full retention of historical performance data, perform a full database backup prior to upgrading.

2. 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.
3. Stop the up.time services before executing the Service Pack.

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

   Code Block
   language text
   # /etc/init.d/uptime_httpd stop  # /etc/init.d/uptime_core stop  # /etc/init.d/uptime_datastore stop

   For Windows installations, run the following:

   Code Block
   language vb
   > net stop "up.time Web Server"  > net stop "up.time Data Collector"  > net stop "up.time Data Store"

5. Continue to apply the up.time upgrade.

   1. 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.

      Code Block
      language text
      # 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.

   2. Windows installations; double click on the service pack upgrade executable and follow the instructions on screen.
      
      
6. 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.
   
   
7. 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).
   
   
8. 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.
   
   
9. 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.