> For the complete MongoDB documentation index, see www.mongodb.com/docs/llms.txt # Manage Backup Policies **Note:** This page applies to both Atlas Infinite and Atlas Core. You can view and customize Atlas policies for regularly scheduled, automated backups. **Note:** The MongoDB Atlas Shared Responsibility Model defines the complementary duties of MongoDB and its customers in maintaining a secure and resilient data environment. Under this framework, MongoDB manages the security and operational integrity of the underlying platform, while customers are responsible for the configuration, management, and data policies of their specific deployments. For a detailed breakdown of ownership across security and operational excellence, see [Shared Responsibility Model.](https://www.mongodb.com/resources/products/fundamentals/shared-responsibility) To take backup snapshots outside your schedule, see [Take On Demand Snapshots](https://www.mongodb.com/docs/atlas/backup/cloud-backup/snapshot-management.md#std-label-on-demand-snapshots) ## Required Access To view backup policies, you must have at least the [`Project Read Only`](https://www.mongodb.com/docs/atlas/reference/user-roles.md#mongodb-authrole-Project-Read-Only) access to the project. Users with [`Organization Owner`](https://www.mongodb.com/docs/atlas/reference/user-roles.md#mongodb-authrole-Organization-Owner) access must add themselves as a [`Project Read Only`](https://www.mongodb.com/docs/atlas/reference/user-roles.md#mongodb-authrole-Project-Read-Only) to the project before they can view backup policies. To modify or delete backup policies, you must have [`Project Backup Manager`](https://www.mongodb.com/docs/atlas/reference/user-roles.md#mongodb-authrole-Project-Backup-Manager) or [`Project Owner`](https://www.mongodb.com/docs/atlas/reference/user-roles.md#mongodb-authrole-Project-Owner) access to the project. Users with [`Organization Owner`](https://www.mongodb.com/docs/atlas/reference/user-roles.md#mongodb-authrole-Organization-Owner) access must add themselves as a `Project Backup Manager` or `Project Owner` to the project before they can modify or delete backup policies. ## View Backup Policies ### Atlas CLI To return the details of the backup policy for the cluster you specify using the Atlas CLI, run the following command: ```sh atlas backups schedule describe [options] ``` To learn more about the command syntax and parameters, see the Atlas CLI documentation for [atlas backups schedule describe.](https://www.mongodb.com/docs/atlas/cli/current/command/atlas-backups-schedule-describe/) A backup policy has the following sections: - A time of day, in UTC (Coordinated Universal Time), at which to create snapshots. - A frequency interval and duration of retention. - If PIT (Point in Time) Restores are enabled, a PIT (Point in Time) window that allows you to restore to any point in time in the last X days where X is the window. **Example:** The default backup policy specifies a snapshot time of `18:00` UTC (Coordinated Universal Time) and the following four policy items: | Policy Type | Tier | Continuous Cloud Backup | Snapshot Taken | Snapshot Retained | | --- | --- | --- | --- | --- | | Hourly | NVMe (non-volatile memory express) | Enabled | Every 12 hours | 7 days | | Hourly | non-NVMe (non-volatile memory express) | Enabled | Every 6 hours | 7 days | | Daily | All | Either | Every day | 7 days | | Weekly | All | Either | Every Saturday | 4 weeks | | Monthly | All | Either | Last day of the month | 12 months | | Yearly | All | Either | Every 1st of December | 1 year | To learn more about Cloud Backup billing, see [Cloud Backups.](https://www.mongodb.com/docs/atlas/billing/cluster-configuration-costs.md#std-label-billing-backup-cloud-provider-snapshots) **Note:** If you have a [Backup Compliance Policy enabled](https://www.mongodb.com/docs/atlas/backup/cloud-backup/backup-compliance-policy.md#std-label-backup-compliance-policy), you can't modify the [backup policy](https://www.mongodb.com/docs/atlas/backup/cloud-backup/configure-backup-policy.md#std-label-configure-backup-policy) for an individual cluster below the minimum requirements set in the Backup Compliance Policy. You can modify the cluster-level backup policy at any time. Atlas augments any preexisting cluster-level policies to meet the minimum requirements of the Backup Compliance Policy. All new clusters use the Backup Compliance Policy. If you reduce the frequency of a backup schedule, the change applies only to future backups. Any existing [oplog](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-oplog) remains for the original window. The minimum requirements of the Backup Compliance Policy apply. You can [configure extra snapshot retention](https://www.mongodb.com/docs/atlas/backup/cloud-backup/configure-backup-policy.md#std-label-config-extra-snapshot-retention). You can also view backup details for all `M10+` dedicated clusters including deleted clusters with retained snapshots. To learn more, see [View Backup Details for Dedicated Clusters.](https://www.mongodb.com/docs/atlas/backup/cloud-backup/backup-compliance-policy.md#std-label-backup-retained-snapshots) ## Change the Backup Policy Time ### Atlas CLI To update the backup policy for the cluster you specify using the Atlas CLI, run the following command: ```sh atlas backups schedule update [options] ``` To delete the backup policy for the cluster you specify using the Atlas CLI, run the following command: ```sh atlas backups schedule delete [options] ``` To learn more about the syntax and parameters for the previous commands, see the Atlas CLI documentation for [atlas backups schedule update](https://www.mongodb.com/docs/atlas/cli/current/command/atlas-backups-schedule-update/) and [atlas backups schedule delete.](https://www.mongodb.com/docs/atlas/cli/current/command/atlas-backups-schedule-delete/) **See also: Related Links** - [Install the Atlas CLI](https://www.mongodb.com/docs/atlas/cli/current/install-atlas-cli/) - [Connect to the Atlas CLI](https://www.mongodb.com/docs/atlas/cli/current/connect-atlas-cli/) ## Configure Your Backup Policy Each row in the Backup Policy Frequency and Retention table represents a backup policy item. Configure the policy items and, optionally, add new policy items to configure a new backup policy. See the [retention considerations](https://www.mongodb.com/docs/atlas/backup/cloud-backup/configure-backup-policy.md#std-label-snapshot-retention) before finalizing your backup policy. **Tip:** Atlas displays the estimated number of snapshots associated with your changes below the Backup Policy Frequency and Retention table. To specify a backup policy item using the Atlas UI: 1. Select the frequency unit from Frequency Unit for an existing policy item. Alternatively, click Add Frequency Unit to add a new policy item to your backup policy. You can't specify multiple Hourly or Daily backup policy items. **Important:** If you have a [Backup Compliance Policy](https://www.mongodb.com/docs/atlas/backup/cloud-backup/backup-compliance-policy.md#std-label-backup-compliance-policy) enabled, you can't remove backup policy items that the compliance policy requires through self-service backup policy changes. To request changes to policy items that the Backup Compliance Policy protects, the designated security or legal representative for the Backup Compliance Policy must [contact MongoDB Support](https://www.mongodb.com/docs/atlas/support.md#std-label-request-support) and complete the required verification process. 2. Select the specific value for the frequency unit from Every. 3. Specify the retention time. In the Retention Time column, choose a retention value and unit for the policy item. To learn more, see [Snapshot Retention Considerations.](https://www.mongodb.com/docs/atlas/backup/cloud-backup/configure-backup-policy.md#std-label-snapshot-retention) 4. At the bottom of the page, click Review Changes. Atlas displays a summary of differences between your existing backup policy and your new backup policy. 5. (Optional) Apply changes to existing snapshots. To apply the retention changes in the updated backup policy to snapshots that Atlas took previously, check Update retention time of existing snapshots. You must check this **before** saving your changes. **Important:** This option affects only snapshots created by the updated policy items and whose retention has not been updated individually with the [Update Cloud Backup Schedule for One Cluster](https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/operation/operation-updategroupclusterbackupschedule) API call. 6. (Optional) Delete existing snapshots. To delete snapshots and snapshot copies associated with policies that you delete, check Delete all snapshots and any associated snapshot copies from removed policies. You must check this **before** saving your changes. Type `delete snapshots` in the prompt that appears when you check this option. 7. Click Confirm. ## Configure the Restore Window **Note:** If you have a [Backup Compliance Policy enabled](https://www.mongodb.com/docs/atlas/backup/cloud-backup/backup-compliance-policy.md#std-label-backup-compliance-policy), only MongoDB support can reduce the [Continuous Cloud Backup Restore Window](https://www.mongodb.com/docs/atlas/backup/cloud-backup/configure-backup-policy.md#std-label-create-pit-policy). To reduce the Continuous Cloud Backup Restore Window, the security or legal representative specified for the Backup Compliance Policy must [request support](https://www.mongodb.com/docs/atlas/support.md#std-label-request-support) and complete an extensive verification process. You can replay the [oplog](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-oplog) to restore a cluster from any point in time within a specified restore window. To specify the restore window duration, select how long you want Atlas to retain the oplog for point-in-time restores from the Restore Window list. You can't configure a restore window that is longer than the [Hourly Snapshot Retention Time.](https://www.mongodb.com/docs/atlas/backup/cloud-backup/configure-backup-policy.md#std-label-creating-backup-policy) ## Configure Extra Snapshot Retention When a Backup Compliance Policy is enabled for your project, you can also configure extra snapshot retention to retain snapshots beyond the Backup Compliance Policy protection period. Your snapshots remain fully protected and users can't delete them during the Backup Compliance Policy period. During the extra snapshot retention period, snapshots are unprotected again and any user with the appropriate role can delete them. When the extra snapshot retention period ends, Atlas deletes the snapshots automatically. Any changes apply to all existing and future snapshots for that frequency unit. The extra snapshot retention time remains the same even if the Backup Compliance Policy changes. To learn more, see [Configure a Backup Compliance Policy.](https://www.mongodb.com/docs/atlas/backup/cloud-backup/backup-compliance-policy.md#std-label-backup-compliance-policy) To specify extra snapshot retention using the Atlas UI: 1. In the Extra Snapshot Retention section, select the frequency unit from the Frequency Unit dropdown for an existing policy item. Alternatively, click Add Another Region and Frequency to add extra snapshot retention for another region. 2. Select the Retention Time as a combination of number and interval. 3. Toggle Point in Time Restore according to whether or not you want to enable [Continuous Cloud Backup](https://www.mongodb.com/docs/atlas/backup/cloud-backup/configure-backup-policy.md#std-label-create-pit-policy) for snapshot copies in that region. 4. At the bottom of the page, click Review Changes to see a summary of differences between your existing backup policy and your new backup policy. 5. Click Confirm. ## Snapshot Retention Considerations In addition to the Retention Time you define for each Cloud Backup frequency unit, be aware of the following: - If you delete an existing backup frequency unit, you have the option to delete all snapshots created by the policies you delete and all associated snapshot copies. To learn more, see [Configure Your Backup Policy.](https://www.mongodb.com/docs/atlas/backup/cloud-backup/configure-backup-policy.md#std-label-creating-backup-policy) - Atlas requires the following: - The retention time must be equal to or longer than the frequency unit. For example, the retention time for weekly snapshot must be one week or greater. - The value specified for Retention Time for items that are less frequent must be equal to or larger than the value specified for items that are more frequent. For example, if the hourly policy item specifies a retention of two weeks, the retention for the weekly snapshot must be two weeks or greater. - If you have a [Backup Compliance Policy enabled](https://www.mongodb.com/docs/atlas/backup/cloud-backup/backup-compliance-policy.md#std-label-backup-compliance-policy), you can't decrease the retention time for a snapshot after it's taken. - If overlapping policy items generate the same snapshot, Atlas associates the snapshot with the policy item with the longest retention time. For example, if the policy specifies a daily snapshot with two-day retention and a weekly snapshot every Saturday with three-week retention, then Atlas displays a frequency of Weekly in the Frequency column on the Snapshots page for the snapshot taken on Saturday and retains the snapshot for three weeks. This is because the weekly policy item has a longer retention time than the daily policy item. - When you disable Cloud Backup or terminate a cluster that has Cloud Backup enabled, you can select whether to delete or retain existing backup snapshots. To learn more, see [Configure Backup Options for the Cluster](https://www.mongodb.com/docs/atlas/cluster-additional-settings.md#std-label-create-cluster-backups) and [Terminate One Deployment.](https://www.mongodb.com/docs/atlas/pause-terminate-cluster.md#std-label-terminate-cluster) For clusters not using [Encryption at Rest using Customer Key Management](https://www.mongodb.com/docs/atlas/security-kms-encryption.md#std-label-security-kms-encryption), you can [download the latest snapshot](https://www.mongodb.com/docs/atlas/backup/cloud-backup/restore-from-local-file.md#std-label-restore-cloud-provider-snapshot-download) to preserve any data stored in the cluster.