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 3.6 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
3.6.x Use this tutorial to upgrade from Ops Manager on 3.6.x to a more recent 3.6.x version.
3.4.x Use this tutorial to upgrade from Ops Manager 3.4.x to version 3.6.x.
2.x
  1. Upgrade from Ops Manager 2.0.x to version 3.4.x. For the specific upgrade path for your version, refer to v3.4 upgrade documentation.

  2. Ensure that your deployment has fully migrated to 3.4 before upgrading to 3.6. To verify:

    1. Click the Admin link in the top right corner of Ops Manager.
    2. Go to General > Ops Manager Config.
    3. Click Miscellaneous tab, and scroll to Ops Manager Data Migration section. If the displayed status is Migration is Complete, you may upgrade to 3.6

    For more information, see Ops Manager Data Migration.

  3. Use this tutorial to upgrade from Ops Manager 3.4.x to version 3.6+.

1.8.x or earlier
  1. Follow the appropriate upgrade path to upgrade your version to 2.0.x. For the specific upgrade path for your version, refer to v2.0 upgrade documentation.
  2. Upgrade from Ops Manager 2.0.x to version 3.4.x. For the specific upgrade path for your version, refer to v3.4 upgrade documentation.
  3. Use this tutorial to upgrade from Ops Manager 3.4.x to version 3.6+.

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.

Considerations

Advisories

  • MongoDB 2.6 is no longer allowed as a backing store. The Ops Manager Application Database and all Blockstore Snapshot Stores must be upgraded to at least MongoDB 3.0.8 before attempting the upgrade to Ops Manager 3.4.
  • As soon as the upgrade to Ops Manager 3.4 is complete, the system will begin a background migration of all monitoring data to a new schema. This migration requires significant free disk space. Before upgrading to Ops Manager 3.4 ensure that the data partitions for the Ops Manager Application Database have at least 50% free disk space.
  • The Automation endpoints for the API are now whitelist protected.
  • If you have modified the mms.conf file in your current installation, back up this file. This is not a regular practice as mms.conf contains platform and network administration settings for Java VM and Ops Manager network port settings. You must use the new mms.conf file the upgrade installs. Reapply any modifications from your backed up copy to the new mms.conf after completing the upgrade.

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. In a browser, go to http://www.mongodb.com and click on the Download button.
  2. Complete the form.
  3. On the MongoDB Download Center page, click on the Ops Manager tab.
  4. Select Ubuntu 12.04+ from the Platforms drop-down menu.
  5. Select DEB from the Packages drop-down menu.
  6. 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.