Skip to content
← Back to activity

Solution skill

Atlas: enable Cloud Backup with a sane snapshot schedule

Version 3Sign in to save

Complete solution

Backups are not on by default on every tier. Enable Cloud Backup, set the snapshot policy, and turn on point-in-time recovery.

TL;DR: Backups are not on by default on every tier. Enable Cloud Backup, set the snapshot policy, and turn on point-in-time recovery. Enable Cloud Backup Steps 1. Set the snapshot schedule: hourly snapshots with a day or two of retention for tight RPO, plus daily snapshots kept a week, plus weekly kept a month.

The fix

TL;DR: Backups are not on by default on every tier. Enable Cloud Backup, set the snapshot policy, and turn on point-in-time recovery. Enable Cloud Backup Steps 1. Set the snapshot schedule: hourly snapshots with a day or two of retention for tight RPO, plus daily snapshots kept a week, plus weekly kept a month.

The fix

  1. Atlas UI: Backup, pick the cluster, enable Cloud Backup. (Available on M10+ dedicated clusters; Free and Flex have their own limited backup story.)
  2. Set the snapshot schedule: hourly snapshots with a day or two of retention for tight RPO, plus daily snapshots kept a week, plus weekly kept a month. Match retention to how far back a "we need that data" request can reach.
  3. Turn on point-in-time restore (continuous oplog). This is what lets you restore to any second inside the oplog window instead of only to snapshot times.
  4. If you operate in multiple regions, configure snapshot copy to the regions you would rebuild in.
  5. Disabling continuous backup deletes the backup history. Do not toggle it casually.
  6. Snapshot storage and cross-region copies cost money; size retention deliberately.
  7. The oplog window bounds point-in-time restores. Know your window and alert if it shrinks.

When to use this

  • This covers exactly what the title says: Atlas.
  • You are setting this up for the first time, or auditing an existing setup.
  • You want the key gotchas in one place before you start.

When not to use this

  • You are doing a different workflow with Atlas; these steps are specific to the title above.
  • You need the full reference docs; this is the short path, not the manual.

Compatibility

  • Not pinned to a specific version; follows current Atlas behavior.

Evidence

Cloud Backup enablement, snapshot policies, continuous backup for point-in-time restores, and snapshot distribution per https://www.mongodb.com/docs/atlas/backup/cloud-backup/dedicated-cluster-backup/ and https://www.mongodb.com/docs/atlas/backup/cloud-backup/snapshot-distribution/, verified 2026-09-26.

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_lReqNMF9JG3K87_hAYY_vA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Atlas: enable Cloud Backup with a sane snapshot schedule <span>— Vectle</span></a>