NetBackup for MongoDB terminologies — NetBackup 11.1 | Cohesity Documentation

Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist

NetBackup for MongoDB terminologies — NetBackup 11.1 | Cohesity Documentation

NetBackup for MongoDB terminologies

The following table defines the terms you come across when using NetBackup for protecting MongoDB cluster.

Table: NetBackup terminologies

Terminology	Definition
Compound job	A backup job for MongoDB data is a compound job. The backup job runs a discovery job for getting information of the data to be backed up. Child jobs are created for each backup host that performs the actual data transfer. After the backup is complete, the job cleans up the snapshots on the backup nodes, removes the thin client and is marked complete.
Discovery job	When a backup job is ran, first a discovery job is created. The discovery job communicates with the config server and gathers information of the shards that need to be backed up and the associated nodes. At the end of the discovery, the job populates a workload discovery file that NetBackup then uses to distribute the workload amongst the backup hosts.
Child job	For backup, a separate child job is created for each backup host to transfer data to the storage media. A child job can transfer data blocks from multiple secondary nodes.
Workload discovery file	During discovery, when the backup host communicates with the config server, a workload discovery file is created. The file contains information about the data files to be backed up and the associated data nodes.
Workload distribution file	After the discovery is complete, NetBackup creates a workload distribution file for each backup host. These files contain information of the data that is backed up by the respective backup host.
Parallel streams	The NetBackup parallel streaming framework allows data blocks from multiple secondary nodes to be backed up using multiple backup hosts simultaneously.
Backup host	The backup host acts as a proxy client. All the backup and the restore operations are ran through the backup host. You can configure media servers, clients, or a primary server as a backup host. The backup host is also used as destination client during restores.
BigData policy	The BigData policy is introduced to: Specify the application type. Allow backing up distributed multi-node environments. Associate backup hosts. Perform workload distribution.
Application server	Sharded MongoDB cluster: Application server is the MongoDB primary config server. Replica set MongoDB cluster: Application server is the primary node of MongoDB. Standalone cluster: Application server is the standalone node.
Primary config server	In a high-availability scenario, the primary config server is the MongoDB instance running in a primary role on a config server replica set. The primary config server must have at least one associated mongos service running on the same host.
Failover config server	In a high-availability scenario, the config server other than the primary config server that is specified as alternate_config_server in the `mongodb.conf` file is referred as the failover config server.

Feedback

Was this page helpful?

Feedback

Was this page helpful?