...
- NMIS 9.4.0
- opAddress 2.2.0
- opCharts 4.4.0
- opConfig 4.4.0
- opEvents 4.2.0
- opHA 3.5.0
- opReports 4.4.0
Note: opReports and Open-AudIT do not use MongoDB.
...
Table of Contents
The Process
The process is structured as follows:
- Prerequisites
- Upgrade Preparation
- Upgrade from MongoDB 3.4 to MongoDB 4.2
- Services Restart
- Clean-up
Prerequisites for Upgrading MongoDB 3.4 to MongoDB 4.2
...
This command does not do anything however, the output will show us the running shell and server that is running.
|
Result will look like below, we are looking for the two version numbers to be 3.4.x
If the versions do not match there may be an issue with your running installation and you should not proceed until this is resolved.
|
MongoDB Storage Engine
Verify storage engine by running
|
The "name" line should have "wiredTiger" in order to proceed.
|
If this mongo cli command does not work you can try the following to determine the storage engine in use
|
Example correct log output - notice the log entry declares the storage engine to be using "wiredTiger"
|
If the system is not using wiredTiger the data migration process should follow a different process. Refer to the following link.
...
An example of the update/upgrade cycle for Ubuntu Linux is as follows:
|
Check for any errors and address as required.
...
The following commands are used to complete this task
|
These commands offer minimal feedback, confirm that the nmis9d process has halted as follows:
Example Command and Output
|
Upgrade from MongoDB 3.4 to MongoDB 4.2
...
The following commands are used to complete this task
|
You can now browse to your instance of NMIS:
...