Navigation
You were redirected from a different version of the documentation. Click here to go back.

Upgrade Ops Manager on Microsoft Windows Server

This tutorial describes how to upgrade an existing Ops Manager installation on Microsoft Windows.

Upgrade Path

The version of your existing Ops Manager installation determines your upgrade path. The following table lists upgrade paths per version:

Existing Version Upgrade Path
2.0 or later Ops Manager supports direct upgrades from version 2.0.x. Use this tutorial to upgrade directly to 3.4.0.
1.8 or earlier
  1. Follow the appropriate upgrade path to upgrade your version to 2.0. For the specific upgrade path for your version, refer to v2.0 upgrade documentation.
  2. Once upgraded to 2.0.x, use this tutorial to upgrade to 3.4.0.

There are no supported downgrade paths for Ops Manager.

Important

It is crucial that you back up the existing conf-mms.properties file 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 (generally, not a customary practice), back up the file. You must use the new mms.conf file installed by the upgrade. You can reapply any modifications 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

There are no supported downgrade paths for Ops Manager.

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:

Important

If you are running OpsManager 1.8 or earlier, upgrade first to Ops Manager 2.0.x.

1

Shut down Ops Manager.

To shutdown Ops Manager:

  1. Click the Start button.
  2. Click Administrative Tools.
  3. Click Services.
  4. Right-click the MongoDB Ops Manager HTTP Service and select Stop.
  5. Right-click the MongoDB Ops Manager Backup Daemon Service and select 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 Windows Server 2008 R2+ from the Platforms drop-down menu.
  5. Select MSI from the Packages drop-down menu.
  6. Click Download.

Note

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

3

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

To install:

  1. Double click the MSI package.
  2. Follow the instructions in the Setup Wizard.
  3. During setup, the Configuration/Log Folder step prompts you to specify a folder where the configuration and log files will be stored.

The installation restricts access to the folder to users with the Administrator access privileges only.

4

Start Ops Manager on every server.

  1. To start the service, click the Start button.
  2. Click Administrative Tools.
  3. Click Services.
  4. In the Services list, right-click the MongoDB Ops Manager HTTP Service and select Start.
5

Restart all Ops Manager services.