• Back Up and Restore Deployments >
• Manage Backups >
• Edit a Backup’s Settings

Edit a Backup’s Settings

Available backup settings depend on the FCV value of your MongoDB database. You can modify the following backup settings for one of your backups.

• If you run FCV 4.2 or later, you can modify:
  • schedule and retention
  • authentication mechanism
  • storage engine
• If you run FCV 4.4 or later, you can modify:
  • preferred member for backup
• If you run FCV 4.0 or earlier, you can also modify:
  • cluster checkpoints
  • schedule

To edit Backup’s settings:

1. Click Backup.
2. Overview tab. Cloud Manager lists all available backups.
3. Click ellipsis h icon next to each backup to access its settings.

Backup Settings Available to All FCVs

Edit Snapshot Schedule and Retention Policy

1

Click Backup.

2

On the row for the process, click the backup’s ellipsis icon, then click Edit Snapshot Schedule.

3

Configure the snapshot settings.

1. Enter the following information as needed.

   See also

   To learn about retention values, see Snapshot Frequency and Retention Policy.

   Take snapshots every … hours and save for … days	Sets how frequently, in hours, Cloud Manager takes a base snapshot of the deployment and the number of days Cloud Manager retains base snapshots. Changes to the snapshot schedule affect your snapshot storage costs.
   Create cluster checkpoint every … minutes (Sharded Clusters only)	Sets how frequently, in minutes, Cloud Manager creates a Checkpoints in between snapshots of a sharded cluster. Checkpoints provide restore points that you can use to create custom point-in-time snapshots. Important You may use checkpoints for clusters that run MongoDB with Feature Compatibility Version of 4.0 or earlier. Checkpoints were removed from MongoDB instances with FCV of 4.2 or later.
   Store daily snapshots for	Sets the number of days that Cloud Manager retains daily snapshots.
   Store weekly snapshots for	Sets the number of weeks that Cloud Manager retains weekly snapshots.
   Store monthly snapshots for	Sets the number of months that Cloud Manager retains monthly snapshots. Note Ops Manager takes monthly snapshots every 28 days, not by calendar month.
   Day of Week for Full Snapshot	Sets the day of the week when Cloud Manager takes a full snapshot. This ensures a recent complete backup. Cloud Manager sets the default value to a random weekday.

2. Click Submit.

Edit Security Credentials

1

Click Backup, then the Overview tab.

2

Select the backup’s ellipsis icon and select Edit Credentials

On the line listing the process, click the ellipsis icon and click Edit Credentials.

3

Provide the authentication information.

Enter the following information as needed and click Submit.

Auth Mechanism	The authentication mechanism that the MongoDB host uses. MongoDB Community options include: Username/Password X.509 Client Certificate MongoDB Enterprise options also include: Kerberos LDAP
DB Username	For Username/Password or LDAP authentication, the username used to authenticate the MongoDB Agent with the MongoDB deployment. See Configure MongoDB Agent for Authentication or Configure MongoDB Agent for LDAP.
DB Password	For Username/Password or LDAP authentication, the password used to authenticate the MongoDB Agent with the MongoDB deployment.
Allows TLS for connections	If checked, Backup uses TLS to connect to MongoDB. See Configure MongoDB Agent to Use TLS.

Modify the Storage Engine Your Backups Use

1

Click Backup, then the Overview tab.

2

Select the backup’s ellipsis icon and select Edit Storage Engine

On the line listing the process, click the ellipsis icon and click Edit Storage Engine.

3

Select the storage engine.

Select the storage engine. See: Storage Engine for more about choosing an appropriate storage engine for your backup.

4

Select the sync source.

Select the Sync source from which to create the new backup. In order to use the new storage engine, Cloud Manager must resync the backup on the new storage engine.

5

Click Submit.

Backup Settings Available to FCV 4.4 and Later

Edit the Preferred Member for Backup

When each snapshot starts, Cloud Manager selects a replica set member to run the snapshot. This automatically selected member should have the least performance impact on the replica set. You can override the default selection.

Important

Use default selection whenever possible. This choice ensures backup availability.

1

Click Backup, then the Overview tab.

2

Open the Select Preferred Member to Backup panel.

On the line listing the process, click ellipsis icon then click Select Preferred Member to Backup.

3

Choose a replica set member to create snapshots.

Click Select a member manually.

4

Select an available member.

From the Select an available member drop-down, select the hostname and process port for the desired member.

Note

If the selected member becomes unavailable, an error message appears in the panel. Cloud Manager uses a default member until the selected member is available.

5

Click Submit.

Backup Settings Available to FCV 4.0 and Earlier

Enable Cluster Checkpoints

Important

You may use checkpoints for clusters that run MongoDB with Feature Compatibility Version of 4.0 or earlier. Checkpoints were removed from MongoDB instances with FCV of 4.2 or later.

Cluster checkpoints provide restore points in between scheduled snapshots. You can use checkpoints to create custom snapshots at points in time between regular snapshots.

1

Click Backup, then the Overview tab.

2

Select the backup’s ellipsis icon and select Edit Snapshot Schedule.

On the line listing the process, click the ellipsis icon and click Edit Snapshot Schedule.

3

Enable cluster checkpoints.

1. Select Create cluster checkpoint every.
2. Set the interval.
3. Click Submit.

Edit the Namespaces Filter

The Namespaces Filter specifies which databases and collections Cloud Manager backs up.

1

Click Backup, then the Overview tab.

2

Select the backup’s ellipsis icon and select Edit Namespaces Filter.

3

Add or remove namespaces and click Submit.

←   Manage Backups Stop, Restart, or Terminate a Backup  →

© MongoDB, Inc 2008-present. MongoDB, Mongo, and the leaf logo are registered trademarks of MongoDB, Inc.