Skip to content

Commit 34de242

Browse files
committed
Linking to PITR limitations from backup migration doc
1 parent eb93ca8 commit 34de242

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/cosmos-db/migrate-continuous-backup.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Azure Cosmos DB currently supports a one-way migration from periodi
44
author: SnehaGunda
55
ms.service: cosmos-db
66
ms.subservice: cosmosdb-sql
7-
ms.date: 10/04/2021
7+
ms.date: 10/28/2021
88
ms.author: sngun
99
ms.topic: how-to
1010
ms.reviewer: sngun
@@ -26,7 +26,7 @@ The following are the key reasons to migrate into continuous mode:
2626
> [!NOTE]
2727
> The migration capability is one-way only and it's an irreversible action. Which means once you migrate from periodic mode to continuous mode, you can’t switch back to periodic mode.
2828
>
29-
> You can migrate an account to continuous backup mode only if the following conditions are true:
29+
> You can migrate an account to continuous backup mode only if the following conditions are true. Also checkout the [point in time restore limitations](continuous-backup-restore-introduction.md#current-limitations) before migrating your account:
3030
>
3131
> * If the account is of type SQL API or API for MongoDB.
3232
> * If the account has a single write region.

0 commit comments

Comments
 (0)