Upgrade from Version 1.2 and Earlier¶

On this page

Overview
Procedure

Warning

To use Ops Manager 1.6 Automation to manage MongoDB Enterprise deployments, you must first install the MongoDB Enterprise dependencies to each server that runs MongoDB Enterprise. You must install the dependencies to the servers before using Automation.

Note that Automation does not yet support use of the MongoDB Enterprise advanced security features (SSL, LDAP, Kerberos, and auditing). Automation will support these features in the next major Ops Manager release.

To run MongoDB Enterprise with advanced security now, deploy MongoDB Enterprise manually (not through Automation) and use Ops Manager only for Monitoring and Backup.

Overview¶

Because of a company name change, the name of the Ops Manager package changed between versions 1.2 and 1.3. Therefore, to upgrade from any version before 1.3, use the following procedure:

Procedure¶

Recommended. Take a full backup of the MMS database before beginning the upgrade procedure.
Shut down MMS, using the following command:
copy
```
/etc/init.d/10gen-mms stop
```
Download the latest Ops Manager package from the downloads page and proceed with the instructions for a fresh install. Do not attempt to use your package manager to do an upgrade.
Follow the procedure for a new install, including steps to configure the conf-mms.properties file. If you used encrypted authentication credentials you will need to regenerate these manually. Do not copy the credentials from your old properties file. Old credentials will not work.
Start Ops Manager using the new package name.

For upgrades using rpm or deb packages, issue:
copy
```
sudo /etc/init.d/mongodb-mms start
```
For upgrades using tar.gz or zip archives, issue:
copy
```
<install_dir>/bin/mongodb-mms start
```
Update the Monitoring Agent. See Install Monitoring Agent for more information.

← Upgrade Ops Manager from tar.gz or zip Archives Configure Local Mode if Ops Manager has No Internet Access →