- Install Ops Manager >
- Upgrade Ops Manager >
- Upgrade Ops Manager with
debPackages
Upgrade Ops Manager with deb Packages¶
On this page
Overview¶
This tutorial describes how to upgrade an existing
Ops Manager Application and Backup Daemon
using deb packages.
Ops Manager supports direct upgrades from version 1.5 and later. If you have an earlier version, you must first upgrade to version 1.5.
Prerequisite¶
You must have administrative access on the machines on which you perform the upgrade.
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.
Procedures¶
Upgrade the Ops Manager Application¶
The version of your existing Ops Manager installation determines your upgrade path. The following table lists upgrade paths per version:
| Version | Upgrade Patch |
|---|---|
| 1.5 or later | Use this procedure to upgrade directly to the latest release. |
| 1.3 or 1.4 |
|
| 1.2 or earlier | Use Upgrade from Version 1.2 and Earlier. |
There are no supported downgrade paths for Ops Manager.
To upgrade:
Recommended. Take a full backup of the Ops Manager database before beginning the upgrade procedure.¶
Shut down Ops Manager.¶
For example:
If you are running Ops Manager Backup, shutdown the Ops Manager Backup Daemon.¶
The daemon may be installed on a different server. It is critical that this is also shut down. To shut down, issue a command similar to the following:
Save a copy of your previous configuration file.¶
For example:
Download the package.¶
Download the latest version of the package by issuing a curl command with
the download link available on the customer downloads page provided to you
by MongoDB.
Install the new package.¶
For example:
Edit the new configuration file.¶
Fill in the new configuration file at
/opt/mongodb/mms/conf/conf-mms.properties using your old file as a
reference point.
Start Ops Manager.¶
For example:
Update all Monitoring Agents.¶
See Install Monitoring Agent for more information.
Update the Backup Daemon and any Backup Agent, as appropriate.¶
If you are running Backup, update the Backup Daemon package and any Backup Agent.
See Install Backup Agent for more information.
Upgrade the Backup Daemon¶
Stop the currently running instance.¶
Download the latest version of the Backup Daemon.¶
Download the new version of the Backup Daemon package by issuing a
curl command with the download link available on the customer
downloads page provided to you by MongoDB.
Install the new Backup Daemon package.¶
For example:
Point the Backup Daemon to the Ops Manager Application Database.¶
Open the /opt/mongodb/mms-backup-daemon/conf/conf-daemon.properties file
with root privileges and set the mongo.mongoUri value to the
servers and ports hosting the Ops Manager Application Database. For example:
Copy the gen.key file.¶
Ops Manager uses the gen.key file to encrypt data at rest in the
Ops Manager Application Database and the
Backup Database. If the Ops Manager Application and Backup
Daemon run on different servers, you must copy the gen.key from the
Ops Manager Application’s server to the daemon’s server.
Use scp to copy the gen.key file from the /etc/mongodb-mms/
directory on the Ops Manager Application server to the /etc/mongodb-mms/
directory on the Backup Daemon.
If you installed the Ops Manager Application from an archive instead of an rpm
package, the gen key is located in the ${HOME}/.mongodb-mms/ directory.
Start the back-end software package.¶
To start the Backup Daemon run:
If everything worked the following displays:
If you run into any problems, the log files are at /opt/mongodb/mms-backup-daemon/logs.
Open Ops Manager and access the Backup configuration page.¶
Open the Ops Manager home page and log in as the user you first registered when installing the Ops Manager Application. (This user is the global owner.) Then click the Admin link at the top right of the page. Then click the Backup tab.
Enter configuration information for the Backup Database.¶
Enter the configuration information described below, and then click Save. Ops Manager uses this information to create the connection string URI used to connect to the database.
Warning
Once the connection string is saved, any changes to the string require you to restart all the Ops Manager instances and Backup Daemons. Clicking Save is not sufficient. Ops Manager will continue to use the previous string until you restart the components.
<hostname>:<port>: Enter a comma-separated list of the fully qualified domain names and port numbers for all replica set members for the Backup Database.
MongoDB Auth Username and MongoDB Auth Password: Enter the user credentials if the database uses authentication.
Encrypted Credentials: Check this if the user credentials use
the Ops Manager credentialstool. For more information, see
Encrypt MongoDB User Credentials.
Use SSL: Check this if the MongoDB database uses SSL. If you select this, you must configure SSL settings for both the Ops Manager Application and Backup Daemon. See Ops Manager Configuration Files.
Connection Options: To add additional connection options, enter them using the MongoDB Connection String URI Format.