Page History

...

To be able to upgrade you need to have the following version installed on your system.

• 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
  • Has licensing been updated

• 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

Recommendation

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 root user'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 conf directory,
  • the old software manifest,
  • and the old install.log.
  Check the app logs

How to restore from a failed upgrade

...