Docs Menu

Docs HomeMongoDB Atlas

Serverless Instance Backups

On this page

  • Limitations
  • View Serverless Instance Snapshots

Atlas takes snapshots of serverless instances using the native snapshot capabilities of the serverless instances's cloud service provider.


You can't disable backup of serverless instances.

Atlas offers the following backup options for serverless instances:

Serverless Continuous Backup
Atlas takes incremental snapshots of the data in your serverless instance every six hours and lets you restore the data from a selected point in time within the last 72 hours. Atlas also takes daily snapshots and retains these daily snapshots for 35 days. To learn more, see Serverless Instance Costs.
Basic Backup
Atlas takes incremental snapshots of the data in your serverless instance every six hours and retains only the two most recent snapshots. You can use this option for free.

To learn more, see Configure Serverless Instance Backup.

  • You can't download serverless instance snapshots.

  • Custom policies are not supported for serverless instance snapshots. Atlas always takes snapshots every six hours.

    If you require finer-grained backups, consider migrating to a dedicated cluster.

  • Atlas doesn't support on-demand snapshots for serverless instances.

  • You can't restore snapshots from shared clusters, dedicated clusters, or from Cloud Manager to serverless instances.

Atlas displays existing snapshots on the Snapshots page.

To view your snapshots:

  1. Click Databases in the top-left corner of the Atlas UI.

  2. From the Database Deployments view, click the name of your serverless instance.

  3. Click the Backup tab.

Atlas displays existing snapshots in the All Snapshots table. From this table, you can restore your existing snapshots.

←  Shared Cluster BackupsBackup Scheduling, Retention, and On-Demand Snapshots →
Share Feedback
© 2023 MongoDB, Inc.


  • Careers
  • Investor Relations
  • Legal Notices
  • Privacy Notices
  • Security Information
  • Trust Center
© 2023 MongoDB, Inc.