> This page location: /docs.md > /docs/management.md > /docs/atlas/backup-restore-cluster.md > /docs/atlas/backup/cloud-backup/overview.md

> For the complete MongoDB documentation index, see www.mongodb.com/docs/llms.txt

<!--
Tab options on this page. Append to the .md URL to filter:
  ?tabs=<id,...>   select specific tabs (e.g. ?tabs=nodejs,shell)
  ?allTabs=true    include every tab
  (no param)       default: one tab per tabset

Available tabs:
  other tabs: atlascli, api, ui
-->

# Configure a Backup Compliance Policy

**Note:**

This page applies to both Atlas Infinite and Atlas Core.

If you have strict data protection requirements, you can enable a Backup Compliance Policy to protect your backup data.

**Note:**

**Important: MongoDB Support must approve requests to disable a Backup Compliance Policy**

After you enable a Backup Compliance Policy, only MongoDB support can approve requests to disable the Backup Compliance Policy from the security or legal representative specified for the Backup Compliance Policy. After MongoDB Support approves the request, Project Owners can disable the Backup Compliance Policy.

To disable a Backup Compliance Policy, the security or legal representative specified for the Backup Compliance Policy must open a case to [request support](https://www.mongodb.com/docs/atlas/support.md#std-label-request-support) and complete an extensive verification process.

Before you enable a Backup Compliance Policy, carefully review the [prohibited actions](https://www.mongodb.com/docs/atlas/backup/cloud-backup/backup-compliance-policy.md#std-label-bcp-prohibited-actions) and [considerations](https://www.mongodb.com/docs/atlas/backup/cloud-backup/backup-compliance-policy.md#std-label-bcp-considerations). You can re-enable a Backup Compliance Policy at any time.

## Prohibited Actions

If you enable a Backup Compliance Policy, no user, regardless of role, can do the following actions:

- Disable the Backup Compliance Policy without MongoDB support. To disable a Backup Compliance Policy, 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.

  **Note:**

  The only exception applies to empty projects that contain no active or paused clusters and no retained snapshots from previously terminated clusters. If a project is empty, users with the [`Organization Owner`](https://www.mongodb.com/docs/atlas/reference/user-roles.md#mongodb-authrole-Organization-Owner) role or the [`Project Owner`](https://www.mongodb.com/docs/atlas/reference/user-roles.md#mongodb-authrole-Project-Owner) role can disable the Backup Compliance Policy.

- 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.

- [Delete a backup snapshot.](https://www.mongodb.com/docs/atlas/backup/cloud-backup/snapshot-management.md#std-label-delete-snapshot)

- Decrease the [retention time](https://www.mongodb.com/docs/atlas/backup/cloud-backup/configure-backup-policy.md#std-label-configure-backup-policy) for a snapshot after it's taken.

- Disable [Cloud Backup.](https://www.mongodb.com/docs/atlas/cluster-additional-settings.md#std-label-create-cluster-backups)

- Disable [Continuous Cloud Backup](https://www.mongodb.com/docs/atlas/cluster-additional-settings.md#std-label-create-cluster-backups) if the Backup Compliance Policy has the Require Point in Time Restore to all clusters option set to On without MongoDB Support. To disable Continuous Cloud Backup, 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.

- 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) without MongoDB Support. 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.

- Delete [policy items](https://www.mongodb.com/docs/atlas/backup/cloud-backup/configure-backup-policy.md#std-label-creating-backup-policy) specified in the Backup Compliance Policy without MongoDB Support. To delete policy items specified in the Backup Compliance Policy, 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.

- [Delete the project](https://www.mongodb.com/docs/atlas/tutorial/manage-projects.md#std-label-delete-project) if any snapshots exist. If you can't remove all projects, you can't [delete the organization.](https://www.mongodb.com/docs/atlas/access/orgs-create-view-edit-delete.md#std-label-delete-organization)

## Considerations

After you enable a Backup Compliance Policy, the following behaviors apply:

- A Backup Compliance Policy limits your ability to reduce backup storage costs. You can't adjust the retention or delete a backup to reduce the backup storage costs. To learn more, see [Manage Billing.](https://www.mongodb.com/docs/atlas/billing.md#std-label-atlas-billing)

- All new and existing clusters have Cloud Backup automatically enabled and use the project-level Backup Compliance Policy. Atlas augments any preexisting [cluster-level backup policies](https://www.mongodb.com/docs/atlas/backup/cloud-backup/configure-backup-policy.md#std-label-configure-backup-policy) to meet the minimum requirements of the Backup Compliance Policy. All new clusters use the Backup Compliance Policy unless the minimum requirements of the [cluster-level backup policy](https://www.mongodb.com/docs/atlas/backup/cloud-backup/configure-backup-policy.md#std-label-configure-backup-policy) expand beyond the minimum requirements of the Backup Compliance Policy.

- You can modify the [cluster-level backup policies](https://www.mongodb.com/docs/atlas/backup/cloud-backup/configure-backup-policy.md#std-label-configure-backup-policy) at any time. If you reduce the frequency of a cluster-level backup policy, 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.

- If the Backup Compliance Policy has the Keep all snapshots when removing additional snapshot regions option set to On and you enable, modify, or delete [multi-region snapshots](https://www.mongodb.com/docs/atlas/backup/cloud-backup/snapshot-distribution.md#std-label-snapshot-distribution), any snapshots already taken remain.

- When you [resume a cluster](https://www.mongodb.com/docs/atlas/pause-terminate-cluster.md#std-label-resume-cluster), Atlas automatically enables Cloud Backup. If the Backup Compliance Policy has the Require Point in Time Restore to all clusters option set to On, Atlas automatically enables Continuous Cloud Backup and adjusts the restore window according to the Backup Compliance Policy. Atlas automatically modifies the backup to meet the minimum requirements of the Backup Compliance Policy.

- If you [terminate a cluster](https://www.mongodb.com/docs/atlas/pause-terminate-cluster.md#std-label-terminate-cluster), Atlas maintains all existing snapshots after the termination according to your backup policy. Atlas retains the [oplog](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-oplog) for [restoring a point in time with continuous cloud backup](https://www.mongodb.com/docs/atlas/recover-pit-continuous-cloud-backup.md#std-label-recover-pit-continuous-cloud-backup) in a static state until Atlas can no longer use them for continuous cloud backup.

- If you [terminate a cluster](https://www.mongodb.com/docs/atlas/pause-terminate-cluster.md#std-label-terminate-cluster), you can't create another cluster with the same name because Atlas uses the name to identify snapshots.

- Whenever a user enables, modifies, or disables a Backup Compliance Policy, Atlas reflects the event in the [Project Activity Feed.](https://www.mongodb.com/docs/atlas/tutorial/activity-feed.md#std-label-view-activity-feed)

## Required Access

To configure a Backup Compliance Policy, you must have [`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 Owner` to the project before configuring a Backup Compliance Policy.

## Prerequisites

- Only MongoDB Support can do the following actions:

  - Approve requests to disable a Backup Compliance Policy.

  - Disable [Continuous Cloud Backup](https://www.mongodb.com/docs/atlas/cluster-additional-settings.md#std-label-create-cluster-backups) if the Backup Compliance Policy has the Require Point in Time Restore to all clusters option set to On.

  - 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)

  - Delete [policy items](https://www.mongodb.com/docs/atlas/backup/cloud-backup/configure-backup-policy.md#std-label-creating-backup-policy) specified in the Backup Compliance Policy.

- Only the specified security or legal representative can [request support.](https://www.mongodb.com/docs/atlas/support.md#std-label-request-support)

- You can apply a Backup Compliance Policy to `M10+` dedicated clusters only.

  **Note:**

  You can't convert a dedicated cluster to a Free cluster (formerly known as `M0`) or a Flex cluster.

## Procedure

### Atlas CLI

To enable the backup compliance policy for your project using the Atlas CLI, run the following command:

```sh

atlas backups compliancePolicy enable [options]

```

To learn more about the command syntax and parameters, see the Atlas CLI documentation for [atlas backups compliancePolicy enable.](https://www.mongodb.com/docs/atlas/cli/current/command/atlas-backups-compliancePolicy-enable/)

## View Projects that have a Backup Compliance Policy Enabled

### Atlas CLI

To return the backup compliance policy for your project using the Atlas CLI, run the following command:

```sh

atlas backups compliancePolicy describe [options]

```

To learn more about the command syntax and parameters, see the Atlas CLI documentation for [atlas backups compliancePolicy describe.](https://www.mongodb.com/docs/atlas/cli/current/command/atlas-backups-compliancePolicy-describe/)

## View Backup Details for Dedicated Clusters

You can view backup details for all `M10+` dedicated clusters including deleted clusters with retained snapshots.

To view backup details:

1. In Atlas, go to the Backup details for your project.

   If it's not already displayed, select the organization that contains your project from the  Organizations menu in the navigation bar.

   If it's not already displayed, select your project from the Projects menu in the navigation bar.

   In the sidebar, click Backup under the Database heading.

   The [Backup](https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%2F%3Cproject%3E%23%2Fsecurity%2Fbackup%2Fclusters) details display.

   Click the cluster link.

2. View the backup details.

## 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 Extra Snapshot Retention.](https://www.mongodb.com/docs/atlas/backup/cloud-backup/configure-backup-policy.md#std-label-config-extra-snapshot-retention)
