View Source

Prerequisites to upgrading

Check the products 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

Verify a successful upgrade

Check the app logs

Licences

There is no need to request a license update, as the AB2 licences are compatible with AB4.

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:

# send email to optek@ompantek.com with advance warning before restoring from backup

service opeventsd stop
service opconfigd stop
service opchartsd stop
service omkd stop

# confirm that the required Opmantek services have stopped
/usr/local/omk/bin/checkomkdaemons.sh status

cd ~
mkdir temp
tar -xvf omk-backup-YYYY-MM-DD.tgz -C ~/temp
unalias cp
cp -R ~/temp/* /usr/local/omk

# at this point this error may occur:
#   cp: cannot create regular file '/usr/local/omk/bin/opchartsd.exe': Text file busy
#   cp: cannot create regular file '/usr/local/omk/bin/opflowd.exe': Text file busy
# if this happens: do
#       mv /usr/local/omk/bin/opchartsd.exe /usr/local/omk/bin/opchartsd.exe.old
#       mv /usr/local/omk/bin/opflowd.exe /usr/local/omk/bin/opflowd.exe.old
# and then: do
# cp -R ~/temp/* /usr/local/omk

service opeventsd start
service opconfigd start
service opchartsd start
service omkd start

# confirm that the Opmantek services are all running
/usr/local/omk/bin/checkomkdaemons.sh status

Ref: Restore Backup after Install

IMPORTANT STEP:

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.