Performing an Incremental Backup for a MongoDB Cluster

You can perform an incremental backup for a MongoDB cluster. Incremental backups back up the MongoDB oplog dumps that are collected at specific intervals. By default, the Commvault software collects oplog dumps every 15 minutes and triggers an incremental back up every four hours.

Note

  • If an incremental backup fails for any reason like oplog roll over and role reversal, then the Commvault converts the log backup to a full snapshot backup automatically. The discovery operation will run as part of full snapshot.

  • To disable the default behavior of converting an incremental log backup to a full backup, you must configure the bMongoDbConvertToFullOnLogBkpFailure. For information on how to configure an additional setting, see Adding a Setting for Servers and Server Groups.

Before You Begin

  • Set the oplog size to an optimal value so that the transactions are not overwritten before they are backed up by the scheduled oplog dump backups. For more information about setting the oplog size, see MongoDB documentation:

  • Verify that the mongodump and mongorestore binaries are placed in the MongoDB bin path that you specified during instance creation.

  • Perform an IntelliSnap full backup on the MongoDB client for the oplog backup schedule.

Procedure

  1. From the navigation pane, go to Manage > Plans.

    The Plans page appears.

  2. In the Plan name column, click the server plan associated with the MongoDB cluster.

    The server plan page appears.

  3. On the Overview tab, under RPO next to Backup frequency, click Add.

    The Add backup frequency dialog box appears.

    To modify an existing backup frequency, click the backup frequency. In the Edit backup frequency dialog box, modify the backup type and the frequency for backups.

  4. From the Backup type list, select Transaction Log, and from the for list, select Databases.

  5. Specify the frequency of the backup.

  6. Click Save.

What to Do Next

To disable operation log dump backups, you must set the bEnableMongoOpLogDumps additional setting to 0.

Loading...