Navigation
This version of the documentation is archived and no longer supported. It will be removed on EOL_DATE. 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.
This version of the manual is no longer supported. It will be removed on EOL_DATE.

Manage Oplog Storage

Throughout the lifecycle of a backup, the Backup Agent tails the oplog of each replica set and sends new oplog entries to Ops Manager. The oplog entries are sent in compressed bundles of approximately 10 MB in size called oplog slices. These oplog slices are stored in one or more MongoDB databases called Oplog Stores. Every Ops Manager deployment needs at least one Oplog Store.

When you enable backups, you are prompted to create one Oplog Store. Once one Oplog Store is created, you manage it separately from your snapshot stores and can create additional Oplog Stores.

This tutorial covers creating additional Oplog Stores to store oplog entries. Like any MongoDB instance, Oplog Stores can exist on any host running MongoDB that the Ops Manager application can access.

Prerequisites

Before creating any Oplog Stores:

Add a Oplog Store

1
2

Click Create New Oplog Store.

3

Provide the Oplog Store details.

Field Contents
Name A name for the Oplog Store
Datastore Type Select Standalone, Replica Set or Sharded Cluster.
MongoDB Host List (replica set and sharded cluster only)

Type a comma-separated list of mongod instances (for a Replica Set) or mongos instances (for a Sharded Cluster) in the <hostname:port> format that comprise the Oplog Store database.

Example

host1.example.com:27017, host2.example.com:27017, host2.example.com:27018

MongoDB Hostname (Standalone only) Type the hostname of the standalone MongoDB instance.
MongoDB Port (Standalone only) Type the port number of the standalone MongoDB instance.
Username
Auth Mechanism Action Configure Instructions
Username and Password (SCRAM-SHA-1) Type the name of the user authorized to access the Oplog Store database. SCRAM
x.509 (X.509) Type the RFC2253-formatted subject from the client certificate of the user authorized to access the Oplog Store database. x.509
Kerberos (GSSAPI) Type the UPN of the user authorized to access the Oplog Store database. Kerberos
LDAP (PLAIN) Type the name of the LDAP user authorized to access the Oplog Store database. LDAP
Password (optional)

Warning

If you did not use the credentialstool to encrypt this password, it is stored as plaintext in the database.

Auth Mechanism Action Configure Instructions
Username and Password (SCRAM-SHA-1) Type the password associated with the username that can access the Oplog Store database. SCRAM
x.509 (X.509) Leave it blank. x.509
Kerberos (GSSAPI) Kerberos retrieves the password from its keytab file. You do not need to type a password into this field. Kerberos
LDAP (PLAIN) Type the password of the LDAP user authorized to access the Oplog Store database. LDAP
Connection Options (optional)

Type any additional configuration file options for the MongoDB instance. This field supports unescaped values only.

For proper syntax, see Connection String URI Format in the MongoDB manual.

Encrypted Credentials (optional) Select if the credentials for the database were encrypted using the credentialstool. The credentials include the Username, Password, AWS Access Key ID and AWS Secret Key.
Use TLS/SSL (optional)

Select if the Oplog Store database only accepts connection encrypted using TLS.

Beyond this checkbox, to connect this oplog store using TLS, you must enable:

  • TLS on the oplog store database.

  • Ops Manager to use TLS to connect to this oplog store.

    Note

    All backing databases share the same TLS certificates. If you have enabled TLS for another backing database, you need only select this checkbox to enable a TLS connection to this oplog store.

New Assignment Enabled (optional) Select if you want to enable this Oplog Store after creating it. This is selected by default so the Oplog Store can be assigned backup jobs. If you clear this checkbox, the Oplog Store is created but you cannot assign backups to this Oplog Store.
4

Click Create.

Edit an Existing Oplog Store

Once created, Oplog Stores are listed directly on the Oplog Storage page in a table. Each row contains the settings for each Oplog Store.

1

Navigate to the Oplog Storage page.

  1. Click the Admin link.
  2. Click the Backup tab.
  3. (Optional) If you have not previously set the head directory, set it in the Head Directory box.
  4. Click the Oplog Storage page.
2

Go to the row for the Oplog Store you want to edit.

3

In the MongoDB Connection column, update any values that need to be changed in the following fields:

Field Contents
<hostname>:<port>

Type in one or more hosts that comprise the Oplog Store database in the <hostname:port> format.

Important

If these hosts are changed, the Oplog Store database they host must have the same data as the original Oplog Store database. Changing the host to a new Oplog Store database results in data loss.

  • If the Oplog Store database is a Replica Set or Sharded Cluster, type a comma-separated list of mongod instances (for a Replica Set) or mongos instances (for a Sharded Cluster).

    Example

    host1.example.com:27017, host2.example.com:27017, host2.example.com:27018

  • If the Oplog Store database is a standalone MongoDB instance, type the hostname:port of the instance.

MongoDB Auth Username
Auth Mechanism Action Configure Instructions
Username and Password (SCRAM-SHA-1) Type the name of the user authorized to access the Oplog Store database. SCRAM
x.509 (X.509) Type the RFC2253-formatted subject from the client certificate of the user authorized to access the Oplog Store database. x.509
Kerberos (GSSAPI) Type the UPN of the user authorized to access the Oplog Store database. Kerberos
LDAP (PLAIN) Type the name of the LDAP user authorized to access the Oplog Store database. LDAP
MongoDB Auth Password

Warning

If you did not use the credentialstool to encrypt this password, it is stored as plaintext in the database.

Auth Mechanism Action Configure Instructions
Username and Password (SCRAM-SHA-1) Type the password associated with the username that can access the Oplog Store database. SCRAM
x.509 (X.509) Leave it blank. x.509
Kerberos (GSSAPI) Kerberos retrieves the password from its keytab file. You do not need to type a password into this field. Kerberos
LDAP (PLAIN) Type the password of the LDAP user authorized to access the Oplog Store database. LDAP
Encrypted Credentials Select if the credentials for the database were encrypted using the credentialstool. The credentials include the Username, Password, AWS Access Key ID and AWS Secret Key.
Use TLS/SSL

Select if the Oplog Store database only accepts connection encrypted using TLS.

Beyond this checkbox, to connect this oplog store using TLS, you must enable:

  • TLS on the oplog store database.

  • Ops Manager to use TLS to connect to this oplog store.

    Note

    All backing databases share the same TLS certificates. If you have enabled TLS for another backing database, you need only select this checkbox to enable a TLS connection to this oplog store.

Connection Options Type any additional configuration file options for the MongoDB instance. This field supports unescaped values only.
Assignment Labels Type a comma-separated list of labels to assign the Oplog Stores to specific projects.
Write Concern

Select your preferred Write Concern:

Default
Deployment Type Default Write Concern
Standalone Journaled
Replica sets or sharded clusters W2
Journaled A primary or standalone MongoDB instance acknowledged the write and wrote that write to their on-disk journals.
Acknowledged A primary or standalone acknowledged the write.
W2 More than one of the cluster members acknowledged the write.
Majority A majority of the replica set members acknowledged the write.
4

Select the checkbox in the Assignment Enabled column.

Select if you want to enable this Oplog Store after creating it. This is selected by default so the Oplog Store can be assigned backup jobs. If you clear this checkbox, the Oplog Store is created but you cannot assign backups to this Oplog Store.

5

Click Save.

6

If you change any connection string values or the Write Concern, restart all the Ops Manager instances including those running Backup Daemons.

Warning

Modifying the connection string values or the Write Concern for an existing blockstore requires you to restart all Ops Manager components, including those only running the Backup Daemon to apply those changes. Connection parameters include:

  • <hostname>:<port>
  • MongoDB Auth Username
  • MongoDB Auth Password
  • Encrypted Credentials
  • Use TLS/SSL
  • Connection Options
  • Write Concern

If you change to another Oplog Store host, the data on the existing Oplog Store is not copied automatically to the other Oplog Store.

See also

For more details on the MongoDB connection string URI, see Connection String URI Format in the MongoDB Manual.

Delete a Oplog Store

1

Navigate to the Oplog Storage page.

  1. Click the Admin link.
  2. Click the Backup tab.
  3. (Optional) If you have not previously set the head directory, set it in the Head Directory box.
  4. Click the Oplog Storage page.
2