Navigation
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 Introduction, please do so now. The introduction describes the Ops Manager components and common topologies.

The sequence for installing Ops Manager is to:

  1. Plan your installation according to the questions on this page.

  2. Provision servers that meet the Ops Manager System Requirements.

    Warning

    Failure to configure servers according to the Ops Manager System Requirements, including the requirement to read the MongoDB Production Notes, can lead to production failure.

  3. Install the Application Database and optional Backup Database.

  4. Install Ops Manager.

    Note

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

Topology Decisions

Do you require redundancy and/or high availability?

The topology you choose for your deployment affects the redundancy and availability of both your metadata and snapshots, and the availability of the Ops Manager Application.

Ops Manager stores application metadata and snapshots in the Ops Manager Application Database and Backup Database respectively. To provide data redundancy, 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. A load balancer placed in front of the Ops Manager Application must not return cached content. For more information, see Configure a Highly Available Ops Manager Application.

The following tables describe the pros and cons for different topologies.

Test Install

This deployment runs on one server and has no data-redundancy. 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.

Production Install with Redundant Metadata and Snapshots

This install runs on at least three servers and provides redundancy 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.

Pros: Can run on as few as three servers. Ops Manager metadata and backups are redundant 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, 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 instance requires you to manually start a new Ops Manager instance. No Ops Manager functionality is available while the application is down.

Production Install with Highly Available Metadata and Snapshots

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 Production Install with Redundant Metadata and Snapshots.

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 instance requires you to manually start a new Ops Manager instance. No Ops Manager functionality is available while the application is down.

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 for Ops Manager Servers without 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 want to use LDAP for user management, you can configure LDAP authentication before or after creating your first group. There are different prerequisites for implementing a new LDAP authentication scheme and converting existing authentication scheme to LDAP. To learn more about these differences, see Using LDAP from the Fresh Install vs. Converting to LDAP.

For details on LDAP authentication, see Configure Ops Manager Users for LDAP Authentication and Authorization.

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 instance, Backup Daemon, and Backup Agent. The separate Ops Manager 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 instance, which you can configure through either different hostnames or split-horizon DNS. For detailed requirements, see Assign Snapshot Stores to Specific Data Centers.