To learn more, see the list of geo-redundant pairs of Azure regions article. The region to which the backup is replicated is based on your source region and the regional pair associated with the source region. For resiliency against regional disaster, each snapshot of the backup data in Azure Blob storage is again replicated to another region through geo-redundant storage (GRS). To guarantee low latency, the snapshot of your backup is stored in Azure Blob storage in the same region as the current write region (or one of the write regions, in case you have a multi-region write configuration). If throughput is provisioned at the database level, the backup and restore process happens across the entire database scope.Īzure Cosmos DB stores these backups in Azure Blob storage whereas the actual data resides locally within Azure Cosmos DB. If the container or database is deleted, Azure Cosmos DB retains the existing snapshots of a given provisioned throughput container or shared throughput database for 30 days. You can change the backup configuration during or after the Azure Cosmos DB account is created. If the default intervals aren't sufficient for your workloads, you can change the backup interval and the retention period from the Azure portal. The following steps show how Azure Cosmos DB performs data backup:Īzure Cosmos DB automatically takes a full backup of your database every 4 hours and at any point of time, only the latest two backups are stored by default. With Azure Cosmos DB, not only your data, but also the backups of your data are highly redundant and resilient to regional disasters. All the backups are stored separately in a storage service, and those backups are globally replicated for resiliency against regional disasters. The automatic backups are taken without affecting the performance or availability of the database operations.

Azure Cosmos DB automatically takes backups of your data at regular intervals.

Azure snapshot