|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
- Review the application release notes for specific requirements, deprecated dependencies or new dependencies. For example: Newer MongoDB version
Test in a non production system
- Prior to upgrade, it is recommended to test the upgrade in a test environment that matches you current setup on production.
- Create a test environment
Have you got custom modifications or template changes
- Review any custom modification applied to you applications and consider that they may not work after upgrade and they may need adjustments.
Have you got a test plan and steps to perform a rollback in your production environment
- Additional Notes:
- opHA 3 and Opcharts 4 Upgrade NotesIt is recommended to have a plan of action in case the upgrade process doesn't work as expected.
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
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 -