Support matrix for Azure Cosmos DB vaulted backup

This article summarizes supported regions, scenarios, and the limitations for Azure Cosmos DB vaulted backup.

Supported regions

Azure Backup for Cosmos DB is available in all Azure public cloud regions. National clouds and sovereign regions are currently not supported.

Azure Backup supports the following backup and restore scenarios for Azure Cosmos DB accounts:

Cosmos DB accounts with either NoSQL or MongoDB API using Request Units (RUs) are supported.
Daily incremental backups with a weekly full backup are supported, providing a 1-day recovery point objective (RPO). Every policy must include one weekly full backup; incremental backups run on the remaining days. Incremental-only policies aren't supported.
Cosmos DB accounts on continuous (PITR) backup mode are only supported.
Cross-subscription restore of backups to a target Cosmos DB account in a different Azure subscription is supported.
Cross-region restore of backups to a target Cosmos DB account in Azure paired region is supported.
Item-level restore of individual databases and containers from a backup isn't supported.
Backups are supported to Backup Vault with geo-redundant storage enabled.
Supports Immutable vault with WORM (Write Once, Read Many) storage, which helps protect your backup data by preventing operations that could result in the loss of recovery points.
Restore operation to an empty, single-region target Cosmos DB account is supported.
Restore operation to a target Cosmos DB account using the same API type as source Cosmos DB account is supported.
Cosmos DB accounts with partitions upto 2,500 are supported (approximately 125 TB).
On-demand backups support full backups only. Incremental backups are always scheduled; on-demand (ad-hoc) incremental backups aren't supported.

Azure Backup for Cosmos DB includes the following backup and restore limitations:

Cosmos DB account enabled with Network Security Perimeter (NSP) isn't supported.
Restoring an incremental recovery point requires its backup chain to be intact — the parent full backup and all intervening incremental backups.
A backup policy can't schedule more than one full backup per week, including custom policies created through Azure CLI or PowerShell.
Backup isn’t supported if the Cosmos DB account’s primary write region differs from the Backup Vault region.
Backup isn’t supported if the Cosmos DB account’s primary write region differs from its deployment region.
Cosmos DB account with hierarchical partition keys isn't supported.
Cosmos DB account with Per-Partition Automatic Failover (PPAF) enabled isn't supported.
Item-level backup isn't supported.
Restore operation isn't supported to a Serverless target Cosmos DB account.
Restore operation isn't supported to a target Cosmos DB account with throughput limit configured.
Auto-heal (automatic retry of a failed scheduled backup) applies to scheduled backups only, and only for specific transient errors. On-demand backups aren't auto-healed.

Was this page helpful?