Skip to content

Commit aa76717

Browse files
Merge pull request #233013 from kanshiG/patch-130
Update continuous-backup-restore-introduction.md
2 parents 138d702 + 2837c9c commit aa76717

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

articles/cosmos-db/continuous-backup-restore-introduction.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Azure Cosmos DB's point-in-time restore feature helps to recover da
44
author: kanshiG
55
ms.service: cosmos-db
66
ms.topic: conceptual
7-
ms.date: 03/02/2023
7+
ms.date: 03/31/2023
88
ms.author: govindk
99
ms.reviewer: mjbrown
1010
ms.custom: references_regions, cosmos-db-video, ignite-2022
@@ -33,7 +33,7 @@ The time window available for restore (also known as retention period) is the lo
3333

3434
The selected option depends on the chosen tier of continuous backup. The point in time for restore can be any timestamp within the retention period no further back than the point when the resource was created. In strong consistency mode, backups taken in the write region are more up to date when compared to the read regions. Read regions can lag behind due to network or other transient issues. While doing restore, you can [get the latest restorable timestamp](get-latest-restore-timestamp.md) for a given resource in a specific region. Getting the latest timestamp ensures that the resource has taken backups up to the given timestamp, and can restore in that region.
3535

36-
Currently, you can restore an Azure Cosmos DB account (API for NoSQL or MongoDB) contents at a specific point in time to another account. You can perform this restore operation via the [Azure portal](restore-account-continuous-backup.md#restore-account-portal), the [Azure CLI](restore-account-continuous-backup.md#restore-account-cli) (Azure CLI), [Azure PowerShell](restore-account-continuous-backup.md#restore-account-powershell), or [Azure Resource Manager templates](restore-account-continuous-backup.md#restore-arm-template). API for Table or Gremlin are in preview and supported through [Azure CLI](restore-account-continuous-backup.md#restore-account-cli) (Azure CLI) and [Azure PowerShell](restore-account-continuous-backup.md#restore-account-powershell).
36+
Currently, you can restore an Azure Cosmos DB account (API for NoSQL or MongoDB, API for Table, API for Gremlin) contents at a specific point in time to another account. You can perform this restore operation via the [Azure portal](restore-account-continuous-backup.md#restore-account-portal), the [Azure CLI](restore-account-continuous-backup.md#restore-account-cli) (Azure CLI), [Azure PowerShell](restore-account-continuous-backup.md#restore-account-powershell), or [Azure Resource Manager templates](restore-account-continuous-backup.md#restore-arm-template).
3737

3838
## Backup storage redundancy
3939

@@ -129,8 +129,6 @@ Currently the point in time restore functionality has the following limitations:
129129

130130
* Azure Cosmos DB APIs for SQL and MongoDB are supported for continuous backup. API for Cassandra isn't supported now.
131131

132-
* API for Table and Gremlin are in preview and supported via PowerShell and Azure CLI.
133-
134132
* Multi-regions write accounts aren't supported.
135133

136134
* Currently Azure Synapse Link isn't fully compatible with continuous backup mode. For more information about backup with analytical store, see [analytical store backup](analytical-store-introduction.md#backup).

0 commit comments

Comments
 (0)