atlas backups restores start initiates a restore job for MongoDB Atlas dedicated clusters running M10 or higher. It restores from a snapshot or point-in-time position, either replacing the source cluster’s data or directing the result to another cluster. section 21.1.2
Choose the restore mode and account for these operational details:
- Automated restore returns a cluster to a selected snapshot and requires the source cluster, snapshot ID, target cluster, and target project. section 21.1.2
- Point-in-time restore uses a UTC timestamp; download restore retrieves the selected snapshot. section 21.1.2
- Automated restore deletes existing data in the target cluster before making it match the snapshot. section 21.1.2
- Flex clusters cannot use Atlas CLI restoration; restore their daily snapshots through the Atlas UI, and target replica sets rather than sharded clusters. section 21.1.2
atlas backups restores start automated \ --clusterName "MongoDB-in-Action-M10" \ --targetClusterName "MongoDB-in-Action-M10" \ --snapshotId 6725be13eae896510f35a553 \ --targetProjectId 65d70c5bc9b5633e80a9c998
Restore a snapshot into the original cluster by keeping the source and target cluster names identical. section 21.1.2
atlas backups restores start automated \
--clusterName "MongoDB-in-Action-M10" \
--snapshotId 6725be13eae896510f35a553 \
--targetClusterName myRestoreDemo \
--targetProjectId 1a2345b67c8e9a12f3456de7
Restore into myRestoreDemo and a separate project to validate data without overwriting the original cluster. section 21.1.2
