Docs Menu
Docs Home
/
MongoDB Ops Manager
/ /

Update from all legacy Agents

You have a project with automated MongoDB deployments with Monitoring, Backup, or both and want to update to the MongoDB Agent.

Note

Review the Prerequisites First

If you want to start or continue using Automation to manage your MongoDB deployments, please review the MongoDB Agent Prerequisites before updating to the MongoDB Agent.

1
2

If you upgrade from Ops Manager 4.0 to 4.2 or later, edit each deployment to remove any unique indexes from management.

Ops Manager 4.2 and later differs from 4.0 in how it manages index. To view, create, or delete indexes after this upgrade, use Data Explorer.

Warning

Don't drop your unique indexes. You need only remove them from management.

3

The Update to MongoDB Agent page opens to start the update process. The Introducing the MongoDB Agent step displays. When you have finished reading this step, click Next.

4

If Automation did not manage your Backup or Monitoring Agents, you can add any Backup or Monitoring settings you had before at the Add Custom Configuration Options for your MongoDB Agent (Optional) step.

Important

Deployments using Kerberos Authentication

Don't add either of the following settings from the legacy Agents:

  • krb5Principal

  • krb5Keytab

Your legacy Agents authenticated with Kerberos as separate database users. Because the MongoDB Agent combines the functions of the legacy Agents, it employs a single database user. To upgrade to the MongoDB Agent and continue using Kerberos, you must:

  1. Create a new Kerberos User Principal and database user for the MongoDB Agent.

  2. Update the Agent authentication configuration in the Ops Manager Authentication & TLS settings with the new MongoDB Agent Principal and Keytab files.

You can remove the legacy Monitoring and Backup Agent users after updating to the MongoDB Agent.

To add options that you had for your Backup Agent and Monitoring Agent:

  1. Under the Backup Configurations section:

    1. Type the desired setting in the Setting box and its corresponding value in the Value box.

    2. To add more than one Setting, click the + Add Setting link. Another row appears.

    3. Repeat until all settings have been added.

  2. Under the Monitoring Configurations section:

    1. Type the desired setting in the Setting box and the corresponding value in the Value box.

    2. To add more than one Setting, click the + Add Setting link. Another row appears.

    3. Repeat until all settings have been added.

  3. Once you have added all the settings necessary for your deployment, click Next.

You can click the to remove any settings that you have added.

Important

Ops Manager does not validate any of these settings. Make sure that the settings and values are correct.

5

If your project has hosts that use Automation, you can update the Agents on those hosts to the MongoDB Agent.

  1. Click Update All.

  2. Wait until all hosts show Updated.

  3. Click Next.

Important

All authentication SCRAM, LDAP, and Kerberos credentials from legacy Agents are retained after the update. All .pem key files are retained as well.

All credentials for the legacy Agents are migrated to the MongoDB Agent.

  • The legacy Automation Agent credentials become the MongoDB Agent credentials used for Automation. These credentials should not need modification. However, if you need to modify them, navigate to Deployment Security Settings Edit Settings.

  • The legacy Monitoring Agent credentials can be modified from Deployment Processes Monitoring Settings Credentials.

  • The legacy Backup Agent credentials can be modified from Continuous Backup Overview <Deployment to Backup> under Options column Edit Credentials.

6

At the Final Steps modal, the legacy Backup and Monitoring Agents are put into standby mode. Click Finish.

After the MongoDB Agent update completes:

← Update to the MongoDB Agent