- Install Ops Manager >
- Upgrade Ops Manager >
- Upgrade Ops Manager with an
rpm
Package
Upgrade Ops Manager with an rpm
Package¶
On this page
This tutorial describes how to upgrade an existing Ops Manager
installation using an rpm
package.
Upgrade Path¶
The version of your existing Ops Manager installation determines the upgrade path you must take to upgrade to Ops Manager 4.0 or later.
Important
- You must follow the upgrade path for your existing version to perform necessary database migrations.
- To protect your data, Ops Manager refuses to start direct upgrades from versions 1.8.x and 2.0.x to version 3.4 or later.
- In high availability environments, you must shut down every Ops Manager application server before starting any Ops Manager application servers upgraded to the new version.
The following table lists upgrade paths for all versions:
Existing Version | Upgrade Path |
---|---|
4.0.x | Use this tutorial to upgrade from Ops Manager 4.0.x to a more recent 4.0.x version. |
3.6.x | Use this tutorial to upgrade from Ops Manager 3.6.x to version 4.0.x. |
3.4.x | Use the v3.6 upgrade tutorial to upgrade from Ops Manager 3.4.x to version 3.6.x. |
2.x or earlier | Use the v3.4 upgrade tutorial to upgrade from Ops Manager 2.x or earlier. |
There are no supported downgrade paths for Ops Manager.
Important
It is crucial that you back up the existing conf-mms.properties
and gen.key
files because the upgrade process will delete
existing data.
Advisories¶
Upgrading to Ops Manager 4.0¶
Before upgrading Ops Manager from 3.6 to 4.0, complete the following actions:
- Upgrade all backing databases to MongoDB 3.4 or later.
Prerequisites¶
Hardware and Software Requirements¶
Your servers must meet the Ops Manager System Requirements.
Warning
Failure to configure servers according to the Ops Manager System Requirements, including the requirement to read the MongoDB Production Notes, can lead to production failure.
Administrator Privileges¶
You must have administrator privileges on the servers on which you perform the upgrade.
Download Link¶
You must have the download link available on the customer downloads page provided to you by MongoDB. If you do not have this link, you can access the download page for evaluation at http://www.mongodb.com/download.
Platform Compatibility¶
Before you upgrade Ops Manager, make sure:
- The platform of the hosts serving Ops Manager is compatible with 4.0.
- The Automation Agents managing your MongoDB deployments are compatible with Ops Manager 4.0.
- The platform of the hosts serving the Ops Manager agents are compatible with the Agents.
If you had to upgrade the platform for the hosts that serve the Automation Agents, upgrade the Automation Agents before upgrading Ops Manager.
Procedure¶
Important
Before you perform the upgrade procedure, ensure that you have a current backup of the Ops Manager backing databases. To perform a full backup, see Shut Down and Back Up Ops Manager.
Download the latest version of the Ops Manager package.¶
Open your preferred browser to visit the MongoDB Download Center on MongoDB.com.
If you start on MongoDB.com instead of following the link above, click Get MongoDB, then select Ops Manager from the Tools menu.
From the Platforms drop-down menu, click one of the following options:
- Red Hat + CentOS 6, 7 / SUSE 12 / Amazon Linux
- Red Hat 7 (ppc64le)
From the Packages drop-down menu, click RPM for x86_64 architecture or RPM (PPC64LE) for ppc64le architecture (RHEL 7 only).
Click Download.
Note
The downloaded package is named
mongodb-mms-<version>.x86_64.rpm
, where <version>
is the
version number.
Install the Ops Manager package on each server being used for Ops Manager services.¶
Install the .rpm
package on each Ops Manager Application server by issuing the
following command, where <version>
is the version of the .rpm
package:
RPM Upgrade to 4.1+ modifies Ops Manager mms.conf
file
If you modified the ports or the
JVM settings that Ops Manager uses, you need to re-apply those
changes to the mms.conf
file after Ops Manager is upgraded.
The upgrade to Ops Manager 4.1 and 4.2 removed the -d64
flag from
the JAVA_MMS_UI_OPTS
parameter.
Update all Agents.¶
Once your upgrade has finished and you log into your Ops Manager instance, Ops Manager displays a banner that says One or more agents are out of date.
Click Update All Agents, then confirm the changes.