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/restore-account-continuous-backup.md
+10-24Lines changed: 10 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -123,14 +123,16 @@ Before restoring the account, install the [latest version of Azure PowerShell](/
123
123
124
124
The following cmdlet is an example to trigger a restore operation with the restore command by using the target account, source account, location, resource group, PublicNetworkAccess and timestamp:
If `PublicNetworkAccess` is not set, restored account is accessible from public network, please ensure to pass Disabled to the `PublicNetworkAccess` option to disable public network access for restored account.
153
+
If `PublicNetworkAccess` is not set, restored account is accessible from public network, please ensure to pass `Disabled` to the `PublicNetworkAccess` option to disable public network access for restored account.
152
154
153
155
> [!NOTE]
154
-
> For restoring with public network access disabled, you'll need to install the preview of powershell module of CosmosDB by executing `Install-Module -Name Az.CosmosDB -AllowPrerelease`. You would also require version 5.1 of the Powershell.
156
+
> For restoring with public network access disabled, the minimum stable version of Az.CosmosDB required is 1.12.0.
155
157
156
158
**Example 2:** Restoring specific collections and databases. This example restores the collections *MyCol1*, *MyCol2* from *MyDB1* and the entire database *MyDB2*, which, includes all the containers under it.
157
159
@@ -194,7 +196,7 @@ Restore-AzCosmosDBAccount `
194
196
-TargetDatabaseAccountName "Pitracct" `
195
197
-SourceDatabaseAccountName "SourceTable" `
196
198
-RestoreTimestampInUtc "2022-04-06T22:06:00" `
197
-
-TablesToRestore $tablesToRestore
199
+
-TablesToRestore $tablesToRestore `
198
200
-Location "West US"
199
201
```
200
202
### To restore a continuous account that is configured with managed identity using CLI
@@ -372,8 +374,8 @@ Use the following command to list all the versions of tables. This command only
#### Find tables that can be restored at any given timestamp
379
381
@@ -411,8 +413,6 @@ The simplest way to trigger a restore is by issuing the restore command with nam
411
413
412
414
#### Create a new Azure Cosmos DB account by restoring from an existing account
413
415
414
-
415
-
416
416
```azurecli-interactive
417
417
418
418
az cosmosdb restore \
@@ -428,11 +428,7 @@ az cosmosdb restore \
428
428
If `--public-network-access` is not set, restored account is accessible from public network. Please ensure to pass `Disabled` to the `--public-network-access` option to prevent public network access for restored account.
429
429
430
430
> [!NOTE]
431
-
> For restoring with public network access disabled, you'll need to install the cosmosdb-preview 0.23.0 of CLI extension by executing `az extension update --name cosmosdb-preview `. You would also require version 2.17.1 of the CLI.
432
-
433
-
434
-
435
-
431
+
> For restoring with public network access disabled, the minimum stable version of azure-cli is 2.52.0.
436
432
437
433
#### Create a new Azure Cosmos DB account by restoring only selected databases and containers from an existing database account
438
434
@@ -669,16 +665,6 @@ az cosmosdb mongodb restorable-resource list \
669
665
--restore-timestamp "2020-07-20T16:09:53+0000"
670
666
```
671
667
672
-
673
-
674
-
675
-
676
-
677
-
678
-
679
-
680
-
681
-
682
668
#### List all the versions of databases in a live database account
683
669
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 graph resources. These commands only work for live accounts.
0 commit comments