Restore a cluster in Azure Cosmos DB for MongoDB vCore
APPLIES TO: MongoDB vCore
Azure Cosmos DB for MongoDB vCore provides automatic backups that enable point-in-time recovery (PITR) without any action required from users. Backups allow customers to restore a server to any point in time within the retention period.
Note
The backup and restore feature is designed to protect against data loss, but it doesn't provide a complete disaster recovery solution. You should ensure that you already have your own disaster recovery plan in place to protect against larger scale outages.
Prerequisites
- An existing Azure Cosmos DB for MongoDB vCore cluster.
- If you don't have an Azure subscription, create an account for free.
- If you have an existing Azure subscription, create a new Azure Cosmos DB for MongoDB vCore cluster.
Backups
Backups are performed automatically in the background. Backups are retained for 35 days for active clusters and 7 days for deleted clusters. All backups are encrypted using AES 256-bit encryption.
Note
Backup files can't be exported. They may only be used for restore operations in Azure Cosmos DB for MongoDB vCore.
In Azure regions that support availability zones, backup snapshots are stored in three availability zones. As long as at least one availability zone is online, the cluster is restorable.
Restore from a backup
The restore process creates a new cluster with the same configuration in the same Azure region, subscription, and resource group as the original. To restore data, customers must create an Azure support request.
Sign in to the Azure portal.
Navigate to the Help + support section and select Create a support request. For more information, see create an Azure support request.
Once the support ticket is submitted, our team guides you through the process of restoring your data from the backup.
Next steps
In this guide, we've covered the backup and restore features for Azure Cosmos DB for MongoDB vCore.
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for