> This page location: /docs.md > /docs/management.md > /docs/atlas/backup-restore-cluster.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, ui
-->

# Restore Your Cluster

Atlas lets you restore data from

- [scheduled and on-demand snapshots](https://www.mongodb.com/docs/atlas/backup/cloud-backup/restore-from-snapshot.md#std-label-restore-from-snapshot)

- [continuous cloud backup](https://www.mongodb.com/docs/atlas/backup/cloud-backup/restore-from-continuous.md#std-label-restore-from-continuous)

- [locally-downloaded snapshot files](https://www.mongodb.com/docs/atlas/backup/cloud-backup/restore-from-local-file.md#std-label-restore-from-local-file)

- [snapshots of a cluster using Encryption at Rest using Customer Key Management](https://www.mongodb.com/docs/atlas/backup/cloud-backup/restore-from-ear.md#std-label-restore-from-ear)

- [a Cloud Manager deployment](https://www.mongodb.com/docs/atlas/backup/cloud-backup/restore-from-cloud-manager.md#std-label-restore-from-cloud-manager)

For scheduled and on-demand snapshots, and continuous cloud backup backups, Atlas supports restoring selected databases or collections. To learn more, see [Collection- and Database-Level Restore Considerations](https://www.mongodb.com/docs/atlas/backup/cloud-backup/restore-from-db-coll.md#std-label-restore-from-db-coll)

To learn more about:

- Cloud Backup, see [Restore Your Cluster.](https://www.mongodb.com/docs/atlas/backup/cloud-backup/restore-overview.md#std-label-restore-overview)

- Optimizing restore speed, see  [Requirements for Using Faster Cross-Project Restores.](https://www.mongodb.com/docs/atlas/backup/cloud-backup/restore-from-snapshot.md#std-label-restore-time-optimizations)

- Restoring snapshots using Encryption at Rest using Customer Key Management, see [Restore from a Snapshot Using Encryption at Rest.](https://www.mongodb.com/docs/atlas/backup/cloud-backup/restore-from-ear.md#std-label-restore-from-ear)

**Note:**

This page applies to Atlas Core only. To learn about Atlas Infinite restores, see [Restore an Atlas Infinite Cluster.](https://www.mongodb.com/docs/atlas/backup/cloud-backup/atlas-infinite-restore.md#std-label-atlas-infinite-restore)

## Required Access

To view cloud backup restore jobs, you must have [`Project Backup Recovery Operator`](https://www.mongodb.com/docs/atlas/reference/user-roles.md#mongodb-authrole-Project-Backup-Recovery-Operator), [`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.

## Encryption

When you initiate a restore job, Atlas transfers the source snapshot over the network using TLS to protect the data in transit. Your cloud provider encrypts restored data at rest using its standard encryption method. These protections apply to all restore jobs, including cross-cloud restores (for example, restoring a snapshot of an AWS (Amazon Web Services) cluster to a Google Cloud cluster).

## Limitations

You can't restore a snapshot created from a MongoDB 7.0 sharded cluster with 3 or fewer shards to a MongoDB 8.0 sharded cluster with 3 or fewer shards with the default [embedded config server](https://www.mongodb.com/docs/atlas/cluster-additional-settings.md#std-label-config-server-types) configuration on MongoDB 8.0.  You must first disable the [Managed Configs](https://www.mongodb.com/docs/atlas/cluster-additional-settings.md#std-label-config-server-management) to create a sharded cluster with dedicated config server before restoring the snapshot. This limitation does not apply to collection- and database-level restore jobs.

## Prerequisites

### Stop Client Operations during Restoration

You must ensure that the target Atlas cluster doesn't receive client requests during restoration. You can restore to a new cluster and reconfigure your application to use that new cluster once it is running for maximum uptime.

## View Status of Snapshot Restorations

### Atlas CLI

### View Cluster Restore Jobs

To list all cloud backup restore jobs for your cluster using the Atlas CLI, run the following command:

```sh

atlas backups restores describe <restoreJobId> [options]

```

To return the details for the cloud backup restore job you specify using the Atlas CLI, run the following command:

```sh

atlas accessLists create [entry] [options]

```

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

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

See also [Troubleshoot Encryption at Rest.](https://www.mongodb.com/docs/atlas/backup/cloud-backup/restore-from-ear.md#std-label-troubleshoot-snapshot-encryption)
