Navigation
You were redirected from a different version of the documentation. Click here to go back.

Configure a Highly Available Ops Manager Backup Service

Overview

The Backup Daemon maintains copies of the data from your backed up mongod instances and creates snapshots used for restoring data. The file system that the Backup Daemon uses must have sufficient disk space and write capacity to store the backed up instances.

For replica sets, the local copy is equivalent to an additional secondary replica set member. For sharded clusters the daemon maintains a local copy of each shard as well as a copy of the config database.

To configure high availability

  • scale your deployment horizontally by using multiple backup daemons, and
  • provide failover for your Ops Manager Application Database and Backup Database by deploying replica sets for the dedicated MongoDB processes that host the databases.

Multiple Backup Daemons

To increase your storage and to scale horizontally, you can run multiple instances of the Backup Daemon. This scales by increasing the available storage for the head databases. This does not increase the available space for snapshot storage.

With multiple daemons, Ops Manager binds each backed-up replica set or shard to a particular Backup Daemon. For example, if you run two daemons for a cluster that has three shards, and if Ops Manager binds two shards to the first daemon, then that daemon’s server replicates only the data of those two shards. The server running the second daemon replicates the data of the remaining shard.

Multiple Backup Daemons allow for manual failover should one daemon become unavailable. You can instruct Ops Manager to transfer the daemon’s backup responsibilities to another Backup Daemon. Ops Manager reconstructs the data on the new daemon’s server and binds the associated replica sets or shards to the new daemon. See Move Jobs from a Lost Backup Daemon to another Backup Daemon for a description of this process.

Ops Manager reconstructs the data using a snapshot and the oplog from the Backup Data Storage.

The Backup Daemon is installed with Ops Manager package but must be specifically activated to run. For more information, see Install Ops Manager and select the procedure specific to your operation system.

Replica Sets for Application and Backup Data

Deploy replica sets rather than standalones for the dedicated MongoDB processes that host the Ops Manager Application Database and Backup Database. Replica sets provide automatic failover should the primary become unavailable.

When deploying a replica set with members in multiple facilities, ensure that a single facility has enough votes to elect a primary if needed. Choose the facility that hosts the core application systems. Place a majority of voting members and all the members that can become primary in this facility. Otherwise, network partitions could prevent the set from being able to form a majority. For details on how replica sets elect primaries, see Replica Set Elections.

To deploy a replica set, see Deploy a Replica Set.

Additional Information

To move jobs from a lost Backup server to another Backup server, see Move Jobs from a Lost Backup Daemon to another Backup Daemon.

For information on making the Ops Manager Application highly available, see Configure a Highly Available Ops Manager Application.