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.

Activate Backup

On this page

Overview

You can back up a sharded cluster or replica set. To back up a standalone mongod process, you must first convert it to a single-member replica set. You can choose to back up all databases and collections on the deployment or specific ones.

Prerequisites

  • Ops Manager must be monitoring the deployment. For a sharded cluster, Ops Manager must also be monitoring at least one mongos in the cluster.
  • A replica set must be MongoDB version 2.2.0 or later.
  • A sharded-cluster must be MongoDB version 2.4.3 or later.
  • Each replica set must have an active primary.
  • For a sharded cluster, all config servers must be running and the balancing round must have completed within the last hour.
  • If you explicitly select a sync target, ensure that the sync target is accessible on the network and keeping up with replication.

Procedure

Before using this procedure, see the Backup Preparations to decide how to back up the data and what data to back up.

1

Select the Backup tab.

2

Select the replica set or cluster to back up.

If you have not yet enabled Backup, select Begin Setup and follow the prompts. Skip the rest of the this procedure.

If you have already enabled Backup, navigate to either the Sharded Cluster Status or Replica Set Status page. Then click the Start button for the replica set or cluster to back up.

3

Select which process to use for the initial Sync Source.

To minimize the impact on the primary, sync off a secondary.

4

If using access control, specify mechanism and credentials, as needed.

Auth Mechanism The authentication mechanism used by the host. Can specify MONGODB-CR, LDAP (PLAIN), or Kerberos(GSSAPI).
Current DB Username If the authentication mechanism is MONGODB-CR or LDAP, the username used to authenticate the Monitoring Agent to the MongoDB deployment. See Configure Backup Agent for MONGODB-CR, Configure Backup Agent for LDAP Authentication, or Configure the Backup Agent for Kerberos for setting up user credentials.
Current DB Password If the authentication mechanism is MONGODB-CR or LDAP, the password used to authenticate the Monitoring Agent to the MongoDB deployment. See Configure Backup Agent for MONGODB-CR, Configure Backup Agent for LDAP Authentication, or Configure the Backup Agent for Kerberos for setting up user credentials.
My deployment supports SSL for MongoDB connections If checked, the Monitoring Agent must have a trusted CA certificate in order to connect to the MongoDB instances. See Configure Monitoring Agent for SSL.

You can optionally configure authentication credentials later through the deployment’s gear icon.

5

To optionally select a storage engine or exclude namespaces, click Show Advanced Options.

Select the following as desired:

Storage Engine: Select MongoDB Memory Mapped for the MongoDB default MMAPv1 engine or WiredTiger for the 64-bit WiredTiger engine available beginning with MongoDB 3.0. Before selecting a storage engine, see the considerations in Storage Engines.

Manage Excluded Namespaces: Click Manage Excluded Namespaces and enter the databases and collections to exclude. For colletions, enter the full namespace: <database>.<collection>. Click Save. You can later add or remove namespaces from the backup, as needed. For more information, see Excluded Namespaces.

6

Click Start Backup.

© MongoDB, Inc 2008-present. MongoDB, Mongo, and the leaf logo are registered trademarks of MongoDB, Inc.