Navigation
This version of the documentation is archived and no longer supported. It will be removed on EOL_DATE. To learn how to upgrade your version of MongoDB Ops Manager, refer to the upgrade documentation.
You were redirected from a different version of the documentation. Click here to go back.
This version of the manual is no longer supported. It will be removed on EOL_DATE.

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

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.

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

Uninstall the current version of Ops Manager.

To uninstall Ops Manager:

  1. Click the Start button.
  2. Click Control Panel.
  3. Click Programs and Features.
  4. Right-click MongoDB Ops Manager and select Uninstall.

Important

If you do not uninstall the previous version of Ops Manager, you receive an error message during the upgrade.

3

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 Microsoft Windows Server 2008 R2, 2012, 2012 R2 + 2016.

  3. From the Packages drop-down menu, click MSI.

  4. Click Download.

Note

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

4

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.

5

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

Restart all Ops Manager services.

7

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.