One of several lightweight programs that run within your network to monitor, manage, and back up your MongoDB databases.

See Automation Agent, Monitoring Agent and Backup Agent.

agent API key

A unique identifier that authenticates a group’s agents to Cloud Manager. A group can have multiple agent API keys.

See Manage Agent API Keys.

authentication mechanism

A method to enable access to a MongoDB database. This is separate from authorization, which grants you permission to use certain actions on a MongoDB database.

See Configure MongoDB Authentication and Authorization.


The assisted management of MongoDB processes through the Cloud Manager interface. Automation Agents installed on your MongoDB servers allow you to deploy, configure, and update MongoDB processes directly from Cloud Manager.

See Automation.

Automation Agent

A lightweight component that automates common management tasks. The Automation Agent runs on every server that will have a mongod or mongos.

See Automation Agent.

Backup Agent

A lightweight component that runs within your data center and backs up MongoDB processes via the MongoDB wire protocol. No direct file system access is needed.

See Backup Agent.

In Cloud Manager, cluster can refer to either a replica set or sharded cluster.
custom snapshot

A backup of the state of your MongoDB deployment at a point in time between stored snapshots. Cloud Manager builds a custom snapshot by applying oplog data to a stored snapshot.

See Restore Overview.

Usually refers to all the MongoDB processes that run within a Cloud Manager group. Deployment can also refer to a specific set of MongoDB processes, such as a specific sharded cluster or replica set.
dirty bytes
Data that has been updated in the WiredTiger cache but not flushed to disk.
excluded namespace

A database or collection that Cloud Manager will not back up, as designated by its namespace.

See Namespaces Filter.


A distinct set of MongoDB processes and Cloud Manager users.

See Create a Group.

initial sync

The MongoDB operation that replicates data from an existing replica set member to a new member. Cloud Manager uses initial sync when starting a new backup.

See Replica Set Data Synchronization in the MongoDB manual.

The real-time reporting, visualization, and alerting of the state of your MongoDB processes. See Monitoring.
Monitoring Agent
A lightweight component that runs within your data center and monitors your MongoDB processes via the MongoDB wire protocol. No direct file system access is needed. See Monitoring Agent.

The combination of the database name and collection name:


A data transmission sent by the Monitoring Agent to Cloud Manager to confirm that the agent and its MongoDB processes are running and reachable.
point-in-time restore

A database restoration that captures the state of your data at a moment in-between snapshots. Point-in-time restores take longer to perform than snapshot restores.

See Restore Overview.


An instance of MongoDB running on a given host and port. The MongoDB database process is mongod. MongoDB also uses the mongos process to route operations in the sharded clusters.

See MongoDB Package Components in the MongoDB manual.

Public API key
A unique identifier that authenticates a Cloud Manager user through the Public API. The key belongs to the user, as opposed to the agent API key, which belongs to the group.
Recovery Point Objective
The maximum tolerable age of backup files that must be recovered from storage for normal operations to resume after a failure or disaster occurs.
Recovery Time Objective
The maximum tolerable length of time that a system can be offline after a failure or disaster occurs.

The access given to a Cloud Manager or MongoDB user.

A physical or virtual machine that hosts one or more MongoDB processes.

A backup of your data captured at a specific interval and stored by Cloud Manager. The Snapshot Frequency and Retention Policy determines the interval for taking snapshots and how long to store them.

See also custom snapshot.

snapshot frequency and retention policy

The schedule for how often to take snapshots and how long to store them.

See Snapshot Frequency and Retention Policy.

snapshot store
The location where your snapshots are stored.
storage engine

The database storage engine manages how data is stored on disk. MongoDB versions 3.0 and higher offer multiple storage engines.

See Storage and FAQ: MongoDB Storage in the MongoDB manual.

sync store
During initial sync of a backed-up deployment, Ops Manager briefly stores slices of the backed-up deployment in a temporary sync store on the Application Database. Ops Manager uses the storage while streaming slices to the Backup Daemon.