- On Prem MMS Monitoring >
- Getting Started with On Prem MMS Monitoring >
- Update On-Prem MongoDB Management Service
Update On-Prem MongoDB Management Service¶
On this page
Update the Monitoring Agent¶
Update the Agent on UNIX/Linux¶
To update the Monitoring agent on UNIX/Linux systems:
- Stop the agent processes.
- Download the latest Monitoring agent from the Settings page of the MMS console, in the Monitoring Agent section.
- Restart the Monitoring agent.
Update the Agent on Windows¶
To update the agent on Windows systems:
Download the latest Monitoring agent from the “Settings” page of the MMS console in the Monitoring Agent section).
From a command shell, issue the following:
This should stop and uninstall On Prem MMS Monitoring.
Confirm that the service no longer exists. Issue the following command:
This operation will return a message that resembles the following:
When you have successfully uninstalled the Monitoring agent, you can use
mongommsinstall.bat
to reinstall On Prem MMS Monitoring.Restart the agent.
Upgrade MMS Packages¶
Upgrading an RPM-Based Installation¶
Please contact MMS to receive the download location of the latest MMS server release.
Shutdown the On-Prem MMS server and take a backup of your existing configuration:
Perform an RPM upgrade:
Reconcile any changes in configuration files.
At this point the upgrade is complete. However you may need to reconcile changes in your configuration with new configuration options available in the latest release.
During the
rpm
operation, if you saw the following output, you have changes to reconcile:Compare your current configuration to the updated version, with the following sequence of operations:
Edit your configuration to resolve any conflicts between the old and new versions, being sure to take any new changes from
conf-mms.properties.rpmnew
as appropriate. Changes tomms.centralUri
, email addresses, and MongoDB are the most common configuration changes.Repeat the above reconciliation for
mms.conf
if the upgrade indicates a conflict.Note
The upgrade from beta versions 1.0.1 to 1.0.2 changed several paths to make the MMS server completely self contained. In 1.0.2 all logs, configuration, and working files are in the
/opt/10gen/mms/
hierarchy. This changes the following paths from 1.0.1:- New logs path: <install_dir>/logs/
- New tmp path: <install_dir>/tmp/
Finally, you may also need to re-symlink your startup script:
Restart the On-Prem MMS server.
Upgrading a tgz
/zip
Installation¶
To upgrade a tarball installation, backup configuration and/or logs, and then re-install the On-Prem MMS server.
Important
It is crucial that you back up the existing configuration because the upgrade process will delete existing data.
In more details:
Shutdown the MMS server and take a backup of your existing configuration and logs.
Remove your existing MMS server installation entirely and extract latest release in its place:
Similar to the RPM upgrade path above, compare and reconcile any changes in configuration between versions:
Edit your configuration to resolve any conflicts between the old and new versions, being sure to take any new changes as appropriate.
Note
Changes to
mms.centralUri
, email addresses, and MongoDB are the most common configuration changes.Restart the On-Prem MMS server.