- Install Ops Manager >
- Upgrade Ops Manager >
- Upgrade Ops Manager with a
deb
Package
Upgrade Ops Manager with a deb
Package¶
On this page
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.8.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 3.6¶
Before upgrading Ops Manager from 3.4 to 3.6, complete the following actions:
Upgrade all backing databases to MongoDB 3.2 or later.
Wait for Ops Manager to finish upgrading the monitoring schema.
To monitor the schema upgrade:
Click Admin.
Click Ops Manager Config.
Click the Miscellaneous tab.
The progress should be shown before the Default Monitoring Data Retention heading.
Change
mms.minimumTLSVersion
if you must support older TLS versions.Ops Manager Application supports TLS 1.2 only by default.
To re-enable ciphers which have been disabled, change
mms.disableCiphers
.Warning
Consider the security implications carefully before doing this.
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:
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 14.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: