Navigation
This version of the documentation is archived and no longer supported. To learn how to upgrade your version of MongoDB Ops Manager, refer to the upgrade documentation.
You were redirected from a different version of the documentation. Click here to go back.

Installation Checklist

Overview

You must make the following decisions before you install Ops Manager. During the install procedures you will make choices based on your decisions here.

If you have not yet read the Ops Manager Components page, please do so for a description of the system’s components.

The sequence for installing Ops Manager is to:

  • Plan your installation according to the questions on this page.
  • Provision servers that meet the Hardware and Software Requirements
  • Set up the Ops Manager Application Database and optional Backup Database.
  • Install the Ops Manager Application and optional Backup Daemon.

Note

To install a simple evaluation deployment on a single server, see Install a Simple Test Ops Manager Installation.

Topology Decisions

Do you require durability and/or high availability?

Ops Manager stores application metadata and snapshots in the Ops Manager Application Database and Backup Database respectively. To provide data durability, run each database as a three-member replica set on multiple servers.

To provide high availability for write operations to the databases, set up each replica set so that all three members hold data. This way, if a member is unreachable the replica set can still write data. Ops Manager uses w:2 write concern, which requires acknowledgement from the primary and one secondary for each write operation.

To provide high availability for the Ops Manager Application, run at least two instances of the application and use a load balancer. For more information, see Configure a Highly Available Ops Manager Application.

The following tables describe the pros and cons for each combination of durability and high availability.

Non-Durable, Test Install

This is a non-durable install that runs on one server. If you lose the server, you must start over from scratch.

Pros: Needs only needs one server.
Cons: If you lose the server, you lose everything: users and groups, metadata, backups, automation configurations, stored monitoring metrics, etc.

Durable Production Install

This install runs on at least three servers and provides durability for your metadata and snapshots. The replica sets for the Ops Manager Application Database and the Backup Database are each made up of two data-bearing members and an arbiter. This installation does not provide high availability.

Pros: Can run on as few as three servers. Ops Manager metadata and backups are durable from the perspective of the Ops Manager Application.
Cons:

No high availability, neither for the databases nor the application:

  1. If the Ops Manager Application Database or the Backup Database loses a data-bearing member, the data is durable but you must restart the member to gain back full Ops Manager functionality. For the Backup Database, Ops Manager will not write new snapshots until the member is again running.
  2. Loss of the Ops Manager Application requires you to manually start a new Ops Manager Application. No Ops Manager functionality is available while the application is down.

Durable Production Install with Highly Available Backup and Application Data

This install requires at least three servers. The replica sets for the Ops Manager Application Database and the Backup Database each comprise at least three data-bearing members. This requires more storage and memory than for the Durable Production Install.

Pros: You can lose a member of the Ops Manager Application Database or Backup Database and still maintain Ops Manager availability. No Ops Manager functionality is lost while the member is down.
Cons: Loss of the Ops Manager Application requires you to manually start a new Ops Manager Application. No Ops Manager functionality is available while the application is down.

Durable Production Install with a Highly Available Ops Manager Application

This runs multiple Ops Manager Applications behind a load balancer and requires infrastructure outside of what Ops Manager offers. For details, see Configure a Highly Available Ops Manager Application.

Pros: Ops Manager continues to be available even when any individual server is lost.
Cons: Requires a larger number of servers, and requires a load balancer capable of routing traffic to available application servers.

Will you deploy managed MongoDB instances on servers that have no internet access?

If you use Automation and if the servers where you will deploy MongoDB do not have internet access, then you must configure Ops Manager to locally store and share the binaries used to deploy MongoDB so that the Automation agents can download them directly from Ops Manager.

You must configure local mode and store the binaries before you create the first managed MongoDB deployment from Ops Manager. For more information, see Configure Local Mode if Ops Manager has No Internet Access.

Will you use a proxy for the Ops Manager application’s outbound network connections?

If Ops Manager will use a proxy server to access external services, you must configure the proxy settings in Ops Manager’s conf-mms.properties configuration file. If you have already started Ops Manager, you must restart after configuring the proxy settings.

Security Decisions

Will you use authentication and/or SSL for the connections to the backing databases?

If you will use authentication or SSL for connections to the Ops Manager Application Database and Backup Database, you must configure those options on each database when deploying the database and then you must configure Ops Manager with the necessary certificate information for accessing the databases. For details, see Configure the Connections to the Backing MongoDB Instances

Will you use LDAP for user authenticate to Ops Manager?

If you will use LDAP for user management, you must configure LDAP authentication before you register any Ops Manager user or group. If you have already created an Ops Manager user or group, you must start from scratch with a fresh Ops Manager install.

During the procedure to install Ops Manager, you are given the option to configure LDAP before creating users or groups. For details on LDAP authentication, see Configure Users and Groups with LDAP for Ops Manager.

Will you use SSL (HTTPS) for connections to the Ops Manager application?

If you will use SSL for connections to Ops Manager from agents, users, and the API, then you must configure Ops Manager to use SSL. The procedure to install Ops Manager includes the option to configure SSL access.

Backup Decisions

Will the servers that run your Backup Daemons have internet access?

If the servers that run your Backup Daemons have no internet access, you must configure offline binary access for the Backup Daemon before running the Daemon. The install procedure includes the option to configure offline binary access.

Are certain backups required to be in certain data centers?

If you need to assign backups of particular MongoDB deployments to particular data centers, then each data center requires its own Ops Manager Application, Backup Daemon, and Backup Agent. The separate Ops Manager Application instances must share a single dedicated Ops Manager Application Database. The Backup Agent in each data center must use the URL for its local Ops Manager Application, which you can configure through either different hostnames or split-horizon DNS. For detailed requirements, see Configure Multiple Blockstores in Multiple Data Centers.