Skip to content

Commit c8dc68e

Browse files
authored
Merge pull request #177976 from SnehaGunda/alwaysencrypted
Linking to PITR limitations from backup migration doc
2 parents 3bb9ae4 + 1ad64d4 commit c8dc68e

File tree

2 files changed

+31
-3
lines changed

2 files changed

+31
-3
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.

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

Lines changed: 29 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to identify the restore time and restore a live or delete
44
author: kanshiG
55
ms.service: cosmos-db
66
ms.topic: how-to
7-
ms.date: 07/29/2021
7+
ms.date: 11/02/2021
88
ms.author: govindk
99
ms.reviewer: sngun
1010
ms.custom: devx-track-azurepowershell
@@ -89,6 +89,18 @@ After initiating a restore operation, select the **Notification** bell icon at t
8989

9090
:::image type="content" source="./media/restore-account-continuous-backup/track-restore-operation-status.png" alt-text="The status of restored account changes from creating to online when the operation is complete." border="true" lightbox="./media/restore-account-continuous-backup/track-restore-operation-status.png":::
9191

92+
### Get the restore details from the restored account
93+
94+
After the restore operation completes, you may want to know the source account name from which you restored or the restore time. In some cases, the source account may be deleted and you can get these details from the restored account.
95+
96+
Use the following steps to get the restore details from Azure portal:
97+
98+
1. Sign into the [Azure portal](https://portal.azure.com/) and navigate to the restored account.
99+
100+
1. Navigate to the **Export template** pane. It opens a JSON template, corresponding to the restored account.
101+
102+
1. The **resources** > **properties** > **restoreParameters** object contains the restore details. The **restoreTimestampInUtc** gives you the time at which the account was restored and the **databasesToRestore** shows the database and container from which the account was restored.
103+
92104
## <a id="restore-account-powershell"></a>Restore an account using Azure PowerShell
93105

94106
Before restoring the account, install the [latest version of Azure PowerShell](/powershell/azure/install-az-ps?view=azps-6.2.1&preserve-view=true) or version higher than 6.2.0. Next connect to your Azure account and select the required subscription with the following commands:
@@ -148,6 +160,14 @@ Restore-AzCosmosDBAccount `
148160
149161
```
150162

163+
### Get the restore details from the restored account
164+
165+
Import the `Az.CosmosDB` module and run the following command to get the restore details:
166+
167+
```azurepowershell
168+
Get-AzCosmosDBAccount -ResourceGroupName MyResourceGroup -Name MyCosmosDBDatabaseAccount
169+
```
170+
151171
### <a id="enumerate-sql-api"></a>Enumerate restorable resources for SQL API
152172

153173
The enumeration cmdlets help you discover the resources that are available for restore at various timestamps. Additionally, they also provide a feed of key events on the restorable account, database, and container resources.
@@ -311,6 +331,14 @@ The simplest way to trigger a restore is by issuing the restore command with nam
311331
312332
```
313333

334+
### Get the restore details from the restored account
335+
336+
Run the following command to get the restore details. The restoreTimestamp will be under the restoreParameters object:
337+
338+
```azurecli-interactive
339+
az cosmosdb show --name MyCosmosDBDatabaseAccount --resource-group MyResourceGroup
340+
```
341+
314342
### <a id="enumerate-sql-api"></a>Enumerate restorable resources for SQL API
315343

316344
The enumeration commands described below help you discover the resources that are available for restore at various timestamps. Additionally, they also provide a feed of key events on the restorable account, database, and container resources.

0 commit comments

Comments
 (0)