...
| Status | ||||
|---|---|---|---|---|
|
Summary
Some new installers handle upgrading In this guide we will migrate the data from NMIS8 compatible and OMK applications Applications to NMIS9 compatible OMK apps automatically. Therefore, please start from one of the applications which are automated; you will then be able to upgrade the remaining products without any issues. If none of your applications are in the "Automated Upgrade process" list please follow the "Step by Step upgrade process" below.
If you are installing OMK apps without access to an automated upgrade (those not listed in "Automated Upgrades process"), the installer will prevent you from installing the application, unless you follow the "Step by Step" process below or until you have completed the upgrade with an Automated Upgrade Process application.
| Info | ||
|---|---|---|
| ||
Once you install your first NMIS9 compatible application any of your original applications will no longer operate until they are upgraded as well. (none of your current data is destroyed). |
Automated Upgrade process
Complete Install of NMIS9 HERE
Install any of the OMK apps which have automated upgrade; the current apps with Auto Upgrade are:
- opEvents-3.2.1 or higher
- opConfig-4.2.1 or higher
- opCharts-4.2.1 or higher
- More coming soon...
nmis9 and OMK Applications.
- Server: uburnto (ubuntu 18) → deb-n-burn (debian 10)
- nmis 8.7.2 → nmis 9.2
- opCharts 2.5.1 → opCharts 3
- opConfig 3.5.2 → opConfig 4
- opEvents 2.6.3 → opEvents 3
- opHA 2.2.2 → opHA 3
- opReports 3.4.2 → opReports 4
Options
- Use a VM for the nmis9 server: We would need to run additional steps to migrate the data.
- Install the apps one the data is migrated: The installers will upgrade the data to the new format.
Upgrade process: Using nmis9 VM
Prerequisites
- NMIS 9 and OMK apps are installed on the server.
Step 1. Stop all daemons
...
Step 2. Move and adapt NMIS configuration file
...
Step 3. Move and adapt OMK configuration files
...
Convert to JSON
Step 4. Copy RRDs
...
Run script to adapt names
Step 5. Move Database
...
Step 6. Import Nodes
...
OMK Applications considerations
opEvents
...
opConfig
...
opReports
NMIS8 opReports and NMIS9 opReports work the same way:
- Report Schedules are stored in /usr/local/conf/schedule
- Reports caching is stored in /usr/local/omk/var/opreports
- Reports are stored in /data/omk/var/reports (unless otherwise specified by the user)
If you followed the instructions above, your Report Schedules are back in place, as you've copied over the entire omk-old/conf directory in step five. The /data/omk/var reports directory should still be where it was at the beginning of the upgrade, as it was never changed.
We recommend coping the ./opreports/known_reports_cache directory and the ./opreports/selftest.json file into the new application.
| Code Block |
|---|
cp -rf /usr/local/omk-old/var/opreports/known_reports_cache /usr/local/omk/var/opreports
cp /usr/local/omk-old/var/opreports/selftest.json /usr/local/omk/var/opreports |
opHA
..After installing any of the above you can continue to install any other NMIS9 compatible applications by simply running their installer.
Step by Step Manual Upgrade Process
...