Upgrading to Analytics 5.x from Analytics 4.x

Analytics 5.x is fully compatible with Resource Manager 4.2.x and higher. However, Analytics 5.x upgrade is only officially supported on CentOS/RHEL 7.2. However, anecdotal evidence from the field strongly indicates that the system works without issue on CentOS/RHEL 5 and 6. Thus, an upgrade "in-place" is technically possible. That said, Zenoss strongly recommends you transition to using CentOS/RHEL 7.2 if possible as part of an Analytics 5.x upgrade since an in-place OS upgrade to CentOS/RHEL 7.2 is not recommended by CentOS/RedHat.

Zenoss recommends you consult our Professional Services if you are not able to deploy CentOS/RHEL 7.2 at your organization. We do not anticipate that condition from preventing you upgrading, but we want to make sure that you have a plan in place for an eventual move to CentOS/RHEL 7.2.

Upgrading from Analytics 4.x may involve moving a Analytics 4.x installation in CentOS/RHEL 5 or 6 to a new CentOS/RHEL 7.2-based server as part of the upgrade process or an in-place upgrade without movement.

At a high level, the upgrade process from Analytics 4.x to Analytics 5.x involves the following steps:
  • Preparing the old or new environment for upgrade
  • Taking an export of the Jaspersoft reporting capabilities in your current install
  • Copying/moving the database storage for the underlying data warehouse database to a CentOS/RHEL 7.2 server
  • Installing MariaDB 10.0.x on the new server
  • Removing any existing Java and replacing it with the Java OpenJDK
  • Installing the Analytics server software
  • Reimporting Jaspersoft reporting capabilities
  • Upgrading the ZenETL ZenPack on the Resource Manager master

You should contact Zenoss Professional Services to acquire assistance with this process. As a "one-time" event, this upgrade scenario does not warrant detailed legacy documentation. We are happy to assist you with the upgrade to ensure your success.

There are no data warehouse "schema" changes affecting your data with this upgrade scenario, so any existing reports are guaranteed to work without modification post upgrade and are transitioned to the new database as part of the upgrade.