Docs Menu
Docs Home
/
MongoDB Atlas
/ / /

Manage Your Backup Snapshots

On this page

  • Required Access
  • Delete a Backup Snapshot
  • In Atlas, go to the Clusters page for your project.
  • Go to the Backup page for your cluster.
  • Select the snapshot to delete.
  • View Backup Snapshots
  • In Atlas, go to the Clusters page for your project.
  • Go to the Backup page for your cluster.
  • Click Snapshots.
  • Take On-Demand Snapshots

While most Atlas snapshot operations are automated according to your backup policies, you can also:

  • View snapshots

  • Manually delete snapshots

  • Initiate on-demand snapshots between planned backups.

To take or delete a backup snapshot, you must have Project Owner access to the project. Users with Organization Owner access must add themselves as a Project Owner to the project before they can take or delete a backup snapshot.

To view backup snapshots, you must have Project Read Only access to the project. Users with Organization Owner access must add themselves as a Project Owner to the project before they can take or delete a backup snapshot.

Note

If you have a Backup Compliance Policy enabled, you can't delete a backup snapshot.

You can delete a snapshot using either the Atlas CLI or the Atlas UI. To delete all copies of a snapshot affected by a multi-region Snapshot Distribution policy without deleting the policy itself, delete the snapshot from its original region.

Deleting the original snapshot by any of these methods will propagate the deletion to all copies of that snapshot.

By default, Atlas displays both on-demand and policy-based snapshots. To view only policy-based snapshots:

  1. Click Policy under View Snapshots by.

    Alternatively, click On-demand to display only snapshots taken by clicking Take Snapshot Now.

Snapshots taken according to your backup policy display the frequency of the policy item that generated the snapshot in the Frequency column: Yearly, Monthly, Weekly, Daily, or Hourly.

Note

If overlapping policy items generate the same snapshot, Atlas associates the snapshot with the policy item with the longest retention time.

Example

The policy specifies a daily snapshot with two-day retention and a weekly snapshot every Saturday with three-week retention. Since the retention time for the weekly policy item is longer than that specified for the hourly policy item, Atlas displays a frequency of Weekly in the Frequency column on the Snapshots page for the snapshot taken on Saturday and retains it for three weeks.

You can change a zone's name in the Atlas UI. If you rename a zone, old snapshots' tooltip zone names aren't renamed.

Atlas takes on-demand snapshots immediately, unlike scheduled snapshots which occur at regular intervals. If there is already an on-demand snapshot with a status of queued or inProgress, you must wait until Atlas has completed the on-demand snapshot before taking another. If there is already a scheduled snapshot with a status of queued or inProgress, you may queue an on-demand snapshot.

Note

If you have a Backup Compliance Policy enabled with a specified retention time for on-demand snapshots, you can't decrease the retention time for an on-demand snapshot after it's taken.

← Manage Backup Policies