> Expert > Backup and Restore Agents > Big Data Apps > MongoDB > MongoDB Configuration

Selecting Secondary Nodes for MongoDB Backups

To perform backups in both MongoDB replica set and sharded cluster deployments, you can select either the node with the least lag or with the least priority, from the secondary node list.

Procedure

  • To the master node client computer that is selected during MongoDB instance creation, add the additional settings as shown in the following table.

    For instructions about adding an additional setting from the CommCell Console, see Adding an Additional Setting from the CommCell Console.

Additional Setting

Category

Type

Value

bMongoDBUseLeastLagNode

iDataAgent

Boolean

Enter one of the following values:

  • TRUE: The node with the least lag in the secondary node list is selected for backups.

    If all secondary nodes have the same lag, then the first node in the list is selected for backups.

  • FALSE: The node with the least priority in the secondary node list is selected for backups (default).

bMongoDBUseLowestPriorityNode

iDataAgent

Boolean

Enter one of the following values:

  • TRUE: The node with the least priority in the secondary node list is selected for backups.

  • FALSE: Irrespective of priority, the first node in the secondary node list is selected for backups.

bMongoDBUseDelayedLagNode

iDataAgent

Boolean

When set to TRUE, the backup operation automatically selects a delayed secondary node that is hidden with priority 0 and slaveDelay > 0.

Loading...