Upgrading and Applying up.time Service Packs

Contents

• Downloading Upgrade Files
• Upgrade FAQ
• Upgrade Considerations
• Supported Upgrade Paths
• Applying up.time Upgrades and Service Packs

Note: You do not need to install a service pack if you have downloaded and installed the latest up.time version from the Support site Downloads page. All service pack updates are included in the current up.time version.

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

Upgrade Considerations

NOTE: Please contact uptime Support prior to attempting an upgrade to 6.0 if your deployment utilizes an MDC configuration.

NOTE: Please contact uptime Support prior to attempting an upgrade to 6.0 if you have configured datastore table partitioning.

NOTE: Please contact uptime Support prior to attempting an upgrade to 6.0 if you are using up.time to monitor virtual machines without also having added the corresponding ESX host(s) to up.time.

NOTE: Please contact uptime Support if attempting to upgrade to up.time 5.3 or later from a deployment that has previously been upgraded from up.time 4.x.

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

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.1 to 5.3 is possible but upgrading from up.time 5.0 to 5.3 is not supported.

• 4.6 -> 5.0 (officially supported until March 1, 2012
• 5.0 -> 5.1
• 5.0 -> 5.2
• 5.1 -> 5.2
• 5.1 -> 5.3
• 5.2 -> 5.3
• 5.2 -> 5.4
• 5.3 -> 5.4
• 5.3 -> 5.5
• 5.4 -> 5.5
• 5.4 -> 6.0
• 5.5 -> 6.0

Applying up.time Upgrades and Service Packs

1. Download the upgrade or service pack installer from 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
   6.0	Windows: up.time-6.0.0-windows.exe RedHat: up.time-6.0.0-rhes-upgrade.bin.gz SuSE: up.time-6.0.0-sles-upgrade.bin.gz Solaris: up.time-6.0.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 4.x to 5.0 or from 5.x to 6.0), you will need to retrieve a new license key from the License Portal (login required).
5. Back up your current up.time deployment. We recommend at least the following steps:
   • 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. 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.
7. 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"

8. Continue to apply the up.time upgrade.
   • Red Hat, SUSE and Solaris installations; run the following commands.
     Note that this example assumes a 6.0 Red Hat upgrade so substitute your file name as appropriate.

     # cd /to/your/upgrade/file/path
     # gunzip -d up.time-6.0.0-rhes-upgrade.bin.gz
     # chmod +x up.time-6.0.0-rhes-upgrade-bin
     # ./up.time-6.0.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.
9. 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.
10. 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.
11. 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

---

up.time startup hangs on Win 2003 R2 after applying Microsoft pat...		Rating	Views
	Symptom You are running up.time on a Windows 2003 R2 platform and receive the following error message after applying Microsoft Patch kb2229593: Uptime GUI Error – Data collector is unavailable... By: uptime Support | Date Created: 7-7-2011 | Last Modified: 8-11-2011 | Index: 534	-	178

Upgrading an up.time installation with a reporting instance		Rating	Views
	This article outlines how to safely upgrade an up.time installation with a separate reporting instance. By: uptime Support | Date Created: 11-2-2006 | Last Modified: 7-28-2011 | Index: 100		1226

Upgrading to up.time 5.0 from up.time 4.x		Rating	Views
	Full instructions for upgrading up.time version 4.x to 5.0. By: uptime Support | Date Created: 5-26-2008 | Last Modified: 6-28-2011 | Index: 232		5645

Login screen returns Database not responding error after upgradin...		Rating	Views
	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: 12-22-2011 | Index: 572	-	347

Creating Custom Service Monitors in up.time		Rating	Views
	By: uptime Support | Date Created: 5-15-2006 | Last Modified: 12-16-2011 | Index: 066		13002

User Comments

---

---

No comments have been posted.

Home About uptime software uptime Blogs uptime Webinar Site Map Contact Privacy Policy Terms of Use

© Copyright 2012 uptime software inc.