You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/cosmos-db/migrate-continuous-backup.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Azure Cosmos DB currently supports a one-way migration from periodi
4
4
author: SnehaGunda
5
5
ms.service: cosmos-db
6
6
ms.subservice: cosmosdb-sql
7
-
ms.date: 10/04/2021
7
+
ms.date: 10/28/2021
8
8
ms.author: sngun
9
9
ms.topic: how-to
10
10
ms.reviewer: sngun
@@ -26,7 +26,7 @@ The following are the key reasons to migrate into continuous mode:
26
26
> [!NOTE]
27
27
> 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.
28
28
>
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:
30
30
>
31
31
> * If the account is of type SQL API or API for MongoDB.
Copy file name to clipboardExpand all lines: articles/cosmos-db/restore-account-continuous-backup.md
+29-1Lines changed: 29 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Learn how to identify the restore time and restore a live or delete
4
4
author: kanshiG
5
5
ms.service: cosmos-db
6
6
ms.topic: how-to
7
-
ms.date: 07/29/2021
7
+
ms.date: 11/02/2021
8
8
ms.author: govindk
9
9
ms.reviewer: sngun
10
10
ms.custom: devx-track-azurepowershell
@@ -89,6 +89,18 @@ After initiating a restore operation, select the **Notification** bell icon at t
89
89
90
90
:::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":::
91
91
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
+
92
104
## <aid="restore-account-powershell"></a>Restore an account using Azure PowerShell
93
105
94
106
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 `
148
160
149
161
```
150
162
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:
### <aid="enumerate-sql-api"></a>Enumerate restorable resources for SQL API
152
172
153
173
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
311
331
312
332
```
313
333
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
+
314
342
### <aid="enumerate-sql-api"></a>Enumerate restorable resources for SQL API
315
343
316
344
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