- Install Ops Manager >
- Upgrade Ops Manager >
- Upgrade Ops Manager with a
deb
Package
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 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 |
|
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.
Release Advisories for Ops Manager 3.4¶
Before upgrading Ops Manager from 2.0.x to 3.4, complete the following actions:
Upgrade backing databases to at least MongoDB 3.0.8. MongoDB 2.6 is no longer allowed as a backing store.
Ensure the data partitions for the Ops Manager Application Database have at least 50% free disk space.
Once the Ops Manager upgrade to 3.4 completes, Ops Manager begins migrating of all monitoring data to a new schema in the background. This migration requires significant free disk space.
Add necessary IP addresses or CIDR blocks for to the whitelists for any API clients connecting to the Automation configuration endpoints.
Back up the
mms.conf
file in your current installation if you have modified it.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 newmms.conf
file the upgrade installs. Reapply any modifications from your backed up copy to the newmms.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:
Important
If you are running OpsManager 1.8 or earlier, upgrade first to Ops Manager 2.0.x.
Stop all existing Ops Manager services.¶
Shut down the Ops Manager Application:
Download the latest version of the Ops Manager package.¶
- In a browser, go to http://www.mongodb.com and click on the Download button.
- Complete the form.
- On the MongoDB Download Center page, click on the Ops Manager tab.
- Select
Ubuntu 12.04+
from the Platforms drop-down menu. - Select
DEB
from the Packages drop-down menu. - Click Download.
Note
The downloaded package is named mongodb-mms-<version>.x86_64.deb
,
where <version>
is the version number.
Install the Ops Manager package on each server being used for Ops Manager.¶
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: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/
.
Start Ops Manager on every server.¶
Issue the following command: