Shared Cluster Backups

Required Access

To manage backups for a cluster, 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 manage backups.

Limitations

• Custom policies are not supported for M2 and M5 cluster snapshots. Atlas always takes a single daily snapshot at the same time, starting 24 hours after the cluster was created.

  If you require finer-grained backups, consider upgrading to an M10 or larger cluster tier.

• On-demand snapshots are not supported for M2 and M5 clusters.

• You can't restore M2 and M5 snapshots to a sharded cluster. You can only restore M2 and M5 snapshots to replica sets.

• You can't restore serverless instance snapshots to M2 and M5 clusters.

• Starting with MongoDB 5.0, you can restore snapshots of clusters that run only the two most recent major versions of MongoDB to M2 and M5 clusters.

  Example

  • You can restore snapshots taken from clusters that run MongoDB 4.4 to an M2 or M5 cluster that runs MongoDB 5.0.

  • You can't restore snapshots taken from clusters that run MongoDB version earlier than 4.4 to an M2 or M5 cluster that runs MongoDB 5.0.

Backup Snapshot Storage Locations

The following table indicates where Atlas stores M2 and M5 cluster snapshots:

View M2/M5 Backup Snapshots

The Atlas CLI does not support M2/M5 backup snapshots.

Additionally, Atlas displays existing M2 or M5 snapshots in the All Daily Snapshots table. From this table, you can restore or download your existing snapshots.