- Install Ops Manager >
- Upgrade Ops Manager >
- Upgrade Ops Manager from a
tar.gz
orzip
Archive
Upgrade Ops Manager from a tar.gz
or zip
Archive¶
On this page
Overview¶
This tutorial describes how to upgrade an existing Ops Manager installation using a tar.gz or zip file. Ops Manager supports direct upgrades from version 1.6 and later.
Considerations¶
- Backup Database
- There are data migrations that touch the various backup data stores that make up the Backup Data Storage. The data stores must all be online when you upgrade. Any data stores that are no longer in use should be deleted through the Ops Manager UI before upgrading.
- Backup Daemon
Beginning with Ops Manager 2.0, there is no separate Backup Daemon package. The Ops Manager package also installs the Backup Daemon. When started, the Ops Manager package automatically starts two services: the Ops Manager Application and the Backup Daemon. You choose on which servers to “activate” the Backup Daemon. The daemon always runs, but it performs no operations unless activated.
After upgrade, a server that runs only the Ops Manager Application continues to do so but now also runs a “dormant” Backup Daemon service. The Backup Daemon remains dormant as long as you do not activate it.
A server that runs only a Backup Daemon runs Ops Manager with an “activated” Backup Daemon and a “dormant” Ops Manager Application. The Ops Manager Application remains dormant as long as you do not direct HTTP traffic to it.
- Backup HTTP Service
Beginning with Ops Manager 2.0, there is no Backup HTTP Service on port 8081. Any Backup Agents that are managed by Automation will be automatically updated to use the new port, 8080. For Backup Agents that were installed manually, you must edit the agent’s configuration file, as described in the procedure below. You must have access to the servers running any manually installed Backup Agents.
Warning
You must configure the new port for any manually installed Backup Agents, or the agents will have no access to Ops Manager.
- Agent Updates
- Do not update the agents before upgrade. If you use Automation, Ops Manager prompts you to update the agents after you upgrade. Follow the prompts to update the agents through the Ops Manager UI. Do not update the agents manually.
- conf-mms.properties
- Beginning in 2.0, Ops Manager stores global configuration settings
in the Ops Manager Application Database and stores only local
settings in the Ops Manager server’s
conf-mms.properties
file. The upgrade procedure uses the existingconf-mms.properties
file to connect to the Ops Manager Application Database before replacing the existing file with the new, smaller 2.0 file. - Restore properties
The following properties no longer apply and are replaced by settings specified when initiating a restore:
mms.backup.restore.linkExpirationHours
mms.backup.restore.linkUnlimitedUses
- mms.conf
- If you have modified the
mms.conf
file in your current installation (which is not typical), back up the file. You must use the newmms.conf
file installed by the upgrade. You can redo any modifications once the upgrade is complete.
Prerequisite¶
- Hardware and Software Requirements
Your servers must meet the Ops Manager Hardware and Software Requirements.
Warning
Failure to configure servers according to the Ops Manager Hardware and Software 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.
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 |
---|---|
1.6 or later | Use this procedure to upgrade directly to the latest version. |
1.5 |
|
1.4 or earlier |
|
There are no supported downgrade paths for Ops Manager.
Important
It is crucial that you back up the existing configuration because the upgrade process will delete existing data.
Procedure¶
To upgrade 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.
Stop all existing Ops Manager services.¶
Shut down the Ops Manager Application:
If you are upgrading from a pre-2.0 Ops Manager Application, and you are also running a Backup Daemon on the machine, shut down the Backup Daemon service:
On each Ops Manager server, back up your existing configuration files and logs to a directory other than the install directory.¶
The following example backs up the configuration files and logs to the server’s home directory:
Important
You will need to access the backed-up <install_dir>/conf/conf-mms.properties
file later in this procedure.
Remove the installed Ops Manager Application and Backup Daemon (Pre-2.0 only) packages.¶
On servers where there is an existing Ops Manager Application or Backup Daemon, first remove the existing application or daemon. Do not remove your backups of the configuration files.
Download the latest version of the Ops Manager archive.¶
- 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
RedHat 5+ / CentOS 5+ / SUSE 11+ / Amazon Linux
orUbuntu 12.04+
from the Platforms drop-down menu. - Select
TAR.GZ
from the Packages drop-down menu. - Click Download.
Note
The downloaded package is named mongodb-mms-<version>.x86_64.tar.gz
,
where <version>
is the version number.
Install the Ops Manager package on each server being used for Ops Manager.¶
Navigate to the directory to which to install Ops Manager. Extract the archive to that directory:
Copy the connection string to the new Ops Manager instances.¶
Copy the
mongo.mongoUri
string from theconf-mms.properties
file of the server that was upgraded to the current version of Ops Manager.Replace the
mongo.mongoUri
string in eachconf-mms.properties
file in each servers which previously only hosted a Backup Daemon.Note
The former Backup Daemon only servers used a different config file, but the upgrade to Ops Manager on those servers created a
conf-mms.properties
file. For these new instances to properly connect to the databases, this string must be replaced.
Start Ops Manager on every server.¶
Issue the following command:
Log into Ops Manager as a user with the Global Owner role.¶
Ops Manager displays a setup wizard for entering the Ops Manager configuration in the Application Database.
Complete the Ops Manager configuration setup.¶
The setup wizard walks you through several pages to configure
the Application Database. Refer to your existing
conf-mms.properties
file as needed.
See also
Ops Manager Configuration for the mapping of
conf-mms.properties
parameters to setup wizard fields.
Important
Make sure you click Save on each tab, even if you do not make any changes.
For any Backup Agents that were installed manually, update their configurations to use port 8080.¶
Beginning with Ops Manager 2.0, Backup Agents access Ops Manager through
port 8080. The Automation Agent automatically updates the ports on
managed Backup Agents. For any Backup Agents that were installed
manually, you must edit the agent’s configuration file and set the mothership
property to
access Ops Manager on port 8080.