How to Enable point-in-time restore (PITR) for Azure Cosmos DB for MongoDB account (RU)

Question

How to Enable point-in-time restore (PITR) for Azure Cosmos DB for MongoDB account (RU).

I already followed the below documentation and implemented the changes, still I am not able to see the PITR.

PS: I provide myself an access called "CosmosRestoreOperator" and "Cosmos DB Operator".

https://learn.microsoft.com/en-us/azure/cosmos-db/restore-account-continuous-backup

https://learn.microsoft.com/en-us/azure/cosmos-db/continuous-backup-restore-permissions

Answer 1

Hi Kaushal Akoliya •,

Welcome to Microsoft Q&A forum and thanks for using Azure Services.

As I understand, you could not see PITR backups in Cosmos DB Mongo account.

Could you please check the status of the restore:

Refer to the section Enumerate restorable resources in API for MongoDB.

Also, consider below limitations:

• Azure Cosmos DB APIs for SQL, MongoDB, Gremlin and Table supported for continuous backup. API for Cassandra isn't supported now.
• Multi-regions write accounts aren't supported.
• Currently Azure Synapse Link isn't fully compatible with continuous backup mode. For more information about backup with analytical store, see analytical store backup.
• The restored account is created in the same region where your source account exists. You can't restore an account into a region where the source account didn't exist.
• The restore window is only 30-day for continuous 30-day tier and it can't be changed. Similarly it's only 7-day for continuous 7-day tier and that also can't be changed.
• The backups aren't automatically geo-disaster resistant. You've to explicitly add another region to have resiliency for the account and the backup.
• While a restore is in progress, don't modify or delete the Identity and Access Management (IAM) policies. These policies grant the permissions for the account to change any VNET, firewall configuration.
• Azure Cosmos DB for MongoDB accounts with continuous backup do not support creating a unique index for an existing collection. For such an account, unique indexes must be created along with their collection; this is done using the create collection extension commands.
• The point-in-time restore functionality always restores to a new Azure Cosmos DB account. Restoring to an existing account is currently not supported. If you're interested in providing feedback about in-place restore, contact the Azure Cosmos DB team via your account representative.
• After restoring, it's possible that for certain collections the consistent index may be rebuilding. You can check the status of the rebuild operation via the IndexTransformationProgress property.
• The restore process restores all the properties of a container including its TTL configuration. As a result, it's possible that the data restored is deleted immediately if you configured that way. In order to prevent this situation, the restore timestamp must be before the TTL properties were added into the container.
• Unique indexes in API for MongoDB can't be added or updated when you create a continuous backup mode account. They also can't be modified when you migrate an account from periodic to continuous mode.

Continuous mode restore may not restore throughput setting valid as of restore point.

Restore time is a function of the data size, the amount of log backup that needs to be replayed, and the number of partitions that need to be restored. Restoring 1 TB of data typically takes 30-90 minutes. For an account with multiple regions, the timing to restore into the same account could vary and more than usual restore into new account capability.

Let us know the configuration of the Cosmos DB account and the Restore account details so that we can further investigate. Thank you.