...
| Info |
|---|
Make sure you have enough space before attempting to upgrade to Uptime Infrastructure Monitor 7.8.x. You should have at least 40% free space before beginning the upgrade. |
Upgrade Preparation Steps
| Anchor | ||||
|---|---|---|---|---|
|
The Uptime Infrastructure Monitor 7.8.x data collector includes a maxpermgen size of 160. This is up from 128 MB in Uptime Infrastructure Monitor 7.7 and earlier. Users who require custom or higher settings can reference the old config file stored at c:\uptime\config-backup\[prior uptime version]\uptime (Windows) or uptime/config-backup/[prior uptime version]/uptime/uptime.jcnf (Linux) and restore the settings after the upgrade. A data collector restart is required. Otherwise the customizations may be lost.
STEP 2: Make necessary Apache configuration changes.
Upgrading the Uptime Monitoring Station will upgrade Apache, PHP, and OpenSSL. This will overwrite the Apache configuration and PHP configuration files. For users who have modified the uptime\apache\conf\httpd.conf or uptime\apache\php\php.ini, the old files will be available in the uptime\config-backup\[old uptime version]\apache\conf and php folders. When the upgrade is complete, customizations can be copied over to the new files. There are several changes in these new configuration files so please do not simply overwrite the file.
STEP 3: Back up the Certificate Store.
The WebLogic Service Monitor is updated to support SSL in Uptime Infrastructure Monitor 7.8.x. Also, email round trip service monitors using or any other service using self-signed certificates manually added to the trusted store will be overwritten upon upgrade and must be reinstalled after the upgrade is complete. For more information about this process, see the Application Monitors section about WebLogic. Because this is a pain, and you may not be aware this was ever done, it is a good idea to back it up and restore it after an upgrade. Simply back up the uptime/jre/lib/security/cacerts file prior to upgrade. Post upgrade, shut down the Uptime Data Collector (uptime core service in Linux) and Uptime Controller (Win and Linux) services, copy your old cacerts file back into that folder, and start the service up again.
...
- Stop your Uptime services.
- In uptime/mysql/my.ini, comment out table_cache=256. This must be commented out because the MySQL 5.7 version is named table_open_cache.
- Search for and, if present, comment out innodb_buffer_pool_instance. This must be commented out because the MySQL 5.7 version is named innodb_buffer_pool_instances.
- Back up uptime/mysql/my.ini.
- Run the Uptime Infrastructure Monitor 7.8.x installer. Note that the upgrade of tables to the new database engine may take from minutes to several hours to complete depending on database size.
- Replace uptime/mysql/my.ini with the backed up version.
Other Upgrade Considerations
Upgrade paths
You can only upgrade directly to Uptime Infrastructure Monitor 7.8.x if your currently installed version is version 7.7.x or 7.6.x. Users on version 7.1 must upgrade to version 7.3, then 7.5 before upgrading to 7.7.3, then 7.8.x. Upgrades are possible across only two minor releases. Users who are running version 6.0 or 6.0.1 must upgrade to 7.0 > 7.1 > 7.3 > 7.5 > 7.7.3 > 7.8.x. For more information, see Upgrading to Uptime Infrastructure Monitor 7.6 and later.
Users who are running version 5.5 or earlier must upgrade to 6.0 or 6.0.1 as a starting point. (Refer to the Uptime Infrastructure Monitor Knowledge Base for specific version upgrade paths.) If you are eligible for a direct upgrade path, you can upgrade using the installer for your Monitoring Station’s operating system. The upgrade process installs new features, and does not modify or delete your existing data.
Refer to one of the following topics if your current version is older than the version required for a direct upgrade:
- Upgrading to Uptime Infrastructure Monitor 7.6 and later
- Upgrading to Uptime Infrastructure Monitor 7.2 through 7.5
- Upgrading to Uptime Infrastructure Monitor 7.1 or earlier
Clustered environment considerations
Users who have a clustered environment should continue using the Uptime 7.7.3 agent. A change in how the UUID is formatted in Uptime 7.8.x causes issues when monitoring clusters. For more information about how SQL Server cluster monitoring works in Uptime Infrastructure Monitor, see the IDERA Community article, Monitor MS-SQL Clusters and Always-On Availability Groups.
Apache/PHP/OpenSSL upgrade considerations
Users who manually updated Apache/PHP/OpenSSL in previous Uptime Infrastructure Monitor release using these instructions and who want to upgrade to Uptime Infrastructure Monitor 7.8.2 or later, must perform the following steps before upgrading:
- Open
uptime/conf/httpd.conf - Change
Listen UIMHTTP
toListen [port on which you want the web server to respond]i.e.Listen 9999 - Save the file.
- Upgrade to Uptime Infrastructure Monitor 7.8.x.
For more information about manually updating Apache/PHP/OpenSSL, see Manually Update Apache and PHP on Windows and Manually Update Apache and PHP on Linux.
MSSQL jdbcDB backend users upgrade considerations
Users upgrading from Uptime Infrastructure Monitor 7.8.0 to 7.8.2 or later who use MSSQL as a database backend should check their [uptime install folder]\uptime.conf and take note of the drivers used. If the sqljdbc4.jar driver is not being used, nothing needs to be done. Look for:
#To use the sqljdbc4.jar instead of the default jtds jar, uncomment the following two lines, place the jar file in the uptime/core folder and restart the collector service.
If dbDriverClass is uncommented, you should comment it out prior to running the upgrade. If you wish to continue using the MSSQL native JDBC driver, you should copy sqljdbc4.jar out of the [uptime install folder]\core folder prior to upgrading as it will get removed during the upgrade. If this task is not performed, you will notice that the upgrade program fails to reinstall the MSSQL JDBC driver and the upgrade will break.
You must download the sqljdbc4.jar driver for MSSQL (https://www.microsoft.com/en-us/download/details.aspx?id=11774 and put it in the uptime/core directory after the upgrade, uncomment the line we commented prior, and restart Uptime data collector (core in Linux) service to pick up the change.
New and Improved Features in Uptime 7.8.5
...
A complete, first-time deployment of Uptime Infrastructure Monitor and its agents is a straightforward process. Refer to the Installation and Quick Start Guide for complete instructions on performing a first-time installation.
Other Upgrade Considerations
Upgrade paths
You can only upgrade directly to Uptime Infrastructure Monitor 7.8.x if your currently installed version is version 7.7.x or 7.6.x. Users on version 7.1 must upgrade to version 7.3, then 7.5 before upgrading to 7.7.3, then 7.8.x. Upgrades are possible across only two minor releases. Users who are running version 6.0 or 6.0.1 must upgrade to 7.0 > 7.1 > 7.3 > 7.5 > 7.7.3 > 7.8.x. For more information, see Upgrading to Uptime Infrastructure Monitor 7.6 and later.
...
- Upgrading to Uptime Infrastructure Monitor 7.6 and later
- Upgrading to Uptime Infrastructure Monitor 7.2 to 7.5
- Upgrading to Uptime Infrastructure Monitor 7.1 or earlier
Clustered environment considerations
Users who have a clustered environment should continue using the Uptime 7.7.3 agent. A change in how the UUID is formatted in Uptime 7.8.x causes issues when monitoring clusters. For more information about how SQL Server cluster monitoring works in Uptime Infrastructure Monitor, see the IDERA Community article, Monitor MS-SQL Clusters and Always-On Availability Groups.
Apache/PHP/OpenSSL upgrade considerations
Users who manually updated Apache/PHP/OpenSSL in previous Uptime Infrastructure Monitor release using these instructions and who want to upgrade to Uptime Infrastructure Monitor 7.8.2 or later, must perform the following steps before upgrading:
...