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.

Back up a Deployment

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 and then Overview page.

2

On the line listing the process, click the ellipsis icon and click Start.

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

3

In the Sync Source field, select the replica set member from which to create the backup.

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

4

If the MongoDB processes uses access control, specify the Auth Mechanism and credentials.

Specify the following, as appropriate:

Auth Mechanism

The authentication mechanism used by the host. The available options are:
DB Username For Username/Password or LDAP authentication, the username used to authenticate the Backup Agent to the MongoDB deployment. For information on setting up credentials, see: Configure Backup Agent for MONGODB-CR or Configure Backup Agent for LDAP Authentication.
DB Password For Username/Password or LDAP authentication, the password used to authenticate the Backup Agent to the MongoDB deployment.
Replica set allows SSL for connections, or Cluster allows SSL for connections If checked, the Backup Agent uses SSL to connect to MongoDB. The agent must have a trusted CA certificate to connect. See Configure Backup Agent for SSL.
5

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

Select the following, as desired.

Storage Engine Select MongoDB Memory Mapped Files 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.
Excluded Namespaces Enter the databases and collections to exclude. For collections, enter the full namespace: <database>.<collection>.
6

Click Start.

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