This document will highlight some key aspects of the upgrade process of the current Opmantek Applications.
Requirements to upgrade
To be able to upgrade you need to have the following version installed on your system.
|NMIS 9||9.1.0G or earlier version|
|opCharts 4||4.1.3 or earlier version|
|opConfig 4||4.1.1 or earlier version|
|opEvents 3||3.1.0 or earlier version|
|opHA 3||3.1.2 or earlier version|
|opReports 4||4.1.1 or earlier version|
- Check our products release notes
opReports 4 release notes
opHA 3 release notes
NMIS 9 Release Notes
opEvents 3 Release Notes
opConfig 4 release notes
opCharts Release Notes
- Has anything been deprecated
- Check compatibility with other OMK apps
Please check our Product Compatibility Page (Product Compatibility)
- Has a dependency changed,
- Newer MongoDB version
- Test in a non production system
- Create a test environment
- Have you got custom modifications or template changes
- Have you got a test plan and steps to perform a rollback in your production environment
- Additional Notes:
- opHA 3 and Opcharts 4 Upgrade Notes
As always, we strongly recommend to keep a backup of the current installation. This is a recommended practice and it's an important step on any software installation or upgrade.
Verify a successful upgrade
The installer saves a log of all actions taken, files copied etc. in the installation directory as
install.log, ie. normally it'll be in
/usr/local/omk/install.log. Subsequent upgrades or installations of other Opmantek products will add to that logfile, so you may very well want to remove or clear the install.log file before upgrading or adding extra software.
Unless this is the very first installation of an Opmantek product on this system, the installer will offer taking a backup of all affected files before the installation commences. This backup will be saved in the
rootuser's home directory as omk-backup-YYYY-MM-DD.tgz. The backup includes:
- all the directories that the installer will later copy files to,
- the old software manifest,
- and the old install.log.
How to restore from a failed upgrade
All opModule installers create a backup of /usr/local/omk prior to the installer running PROVIDED you answered the following question early in the installation procedure in the affirmative:
- Do you want to perform a backup of your installation directory?
- Default answer for automated install is 'Yes'.
This is the process to use if you need to roll back from the installer using this backup:
You also need to run the installer for each previously application that was installed in order to downgrade properly and have the initd and systemd services restored too.
A couple things to remember -
- Each run of an opModule installer creates a new backup file. However, since they all use the same name only the most recent will be maintained. If you are installing several packages you should rename each backup before running the next.
- This process overlays the backup into the /usr/local/omk directory and DOES NOT replace it.
There is no need to request a license update, as the licenses are continuing to be valid with this upgrade.