Navigation

Upgrade Ops Manager with a deb Package

This tutorial describes how to upgrade an existing Ops Manager installation using a deb 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 Refer to the v3.6 upgrade documentation to upgrade from Ops Manager 3.4.x to version 3.6.x.
2.x or earlier For the specific upgrade path for your version, refer to v3.4 upgrade documentation.

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.

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.

To upgrade Ops Manager:

1

Stop all existing Ops Manager services.

Shut down the Ops Manager Application:

sudo service mongodb-mms stop
2

Download the latest version of the Ops Manager package.

  1. 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.

  2. From the Platforms drop-down menu, click one of the following options:

    • Ubuntu 14.04, 16.04 + 18.04
    • Ubuntu 16.04 (ppc64le)
  3. From the Packages drop-down menu, click DEB for x86_64 architecture or DEB (PPC64LE) for ppc64le architecture (Ubuntu 16.04 only).

  4. Click Download.

Note

The downloaded package is named mongodb-mms-<version>.x86_64.deb, where <version> is the version number.

3

Install the Ops Manager package on each server being used for Ops Manager.

  1. Install the .deb package on each Ops Manager Application server and each Backup Daemon server by issuing the following command, where <version> is the version of the .deb package:

    sudo dpkg -i mongodb-mms_<version>_x86_64.deb
    
  2. When prompted whether to overwrite the currently installed version of conf-mms.properties, type N, to keep the currently installed version.

The installer preserves the existing conf-mms.properties configuration file and names the new configuration file conf-mms.properties.dpkg-dist. Both are located in /opt/mongodb/mms/conf/.

4

Start Ops Manager on every server.

Issue the following command:

sudo service mongodb-mms start
5

Restart all Ops Manager services.