Skip to content

Commit b385bc0

Browse files
author
Jill Grant
authored
Merge pull request #235030 from seesharprun/cosmos-revamp-continuous-backup-restore-faq
[Cosmos DB] Update continuous backup/restore FAQ
2 parents 9bcf86a + d74365d commit b385bc0

3 files changed

+70
-50
lines changed

articles/cosmos-db/continuous-backup-restore-frequently-asked-questions.yml

Lines changed: 11 additions & 50 deletions
Original file line numberDiff line numberDiff line change
@@ -1,87 +1,48 @@
11
### YamlMime:FAQ
22
metadata:
3-
title: Frequently asked questions about Azure Cosmos DB continuous backup
3+
title: Frequently asked questions about continuous backup
4+
titleSuffix: Azure Cosmos DB
45
description: This article lists frequently asked questions about the Azure Cosmos DB point-in-time restore feature that's available in continuous backup mode.
56
author: kanshiG
6-
ms.service: cosmos-db
7-
ms.custom: ignite-2022
8-
ms.topic: faq
9-
ms.date: 04/14/2022
107
ms.author: govindk
118
ms.reviewer: mjbrown
9+
ms.topic: faq
10+
ms.service: cosmos-db
11+
ms.date: 04/19/2023
12+
ms.custom: ignite-2022
1213
title: Frequently asked questions about the Azure Cosmos DB continuous backup
1314
summary: |
1415
[!INCLUDE[NoSQL, MongoDB, Gremlin, Table](includes/appliesto-nosql-mongodb-gremlin-table.md)]
1516
1617
This article lists frequently asked questions about the Azure Cosmos DB point-in-time restore functionality that's available in continuous backup mode.
17-
18-
1918
sections:
2019
- name: Ignored
2120
questions:
2221
- question: |
2322
How much time does it takes to restore?
2423
answer: |
2524
Restore time is a function of the data size, the amount of log backup that needs to be replayed, and the number of partitions that need to be restored. Restoring 1 terabyte of data typically takes 30 to 90 minutes.
26-
2725
- question: |
2826
Can I submit the restore time in local time?
2927
answer: |
30-
The restore might not happen, depending on whether key resources like databases or containers existed at that time. You can verify by entering the time and looking at a selected database or container for that time. If no resources exist to restore, the restore process won't work.
31-
28+
The restore might not happen, depending on whether key resources like databases or containers existed at that time. You can verify by entering the time and looking at a selected database or container for that time. If that is no resources exist to restore, the restore process doesn't work.
3229
- question: |
3330
How can I track the restoration of an account?
3431
answer: |
35-
After you submit the restore command and wait on the page, the status bar shows a message about a successfully restored account when the operation finishes. You can also search for the restored account and [track its status](restore-account-continuous-backup.md#track-restore-status). While the restore is in progress, the account status is **Creating**. After the restore operation finishes, the account status changes to **Online**.
36-
37-
For PowerShell and the Azure CLI, you can track the progress of a restore operation by using the `az cosmosdb show` command:
38-
39-
```azurecli-interactive
40-
az cosmosdb show --name "accountName" --resource-group "resourceGroup"
41-
```
42-
43-
The `provisioningState` value is `Succeeded` when the account is online.
44-
45-
```json
46-
{
47-
"virtualNetworkRules": [],
48-
"writeLocations" : [
49-
{
50-
"documentEndpoint": "https://<accountname>.documents.azure.com:443/",
51-
"failoverpriority": 0,
52-
"id": "accountName" ,
53-
"isZoneRedundant" : false,
54-
"locationName": "West US 2",
55-
"provisioningState": "Succeeded"
56-
}
57-
]
58-
}
59-
```
60-
32+
[!INCLUDE[](includes/continuous-backup-restore-frequently-asked-questions-restore-progress-commands.md)]
6133
- question: |
6234
How can I find out whether a continuous backup mode account was restored from another account?
6335
answer: |
64-
You can identify whether an account is restored and get the restore details by using the [Azure portal](restore-account-continuous-backup.md#get-the-restore-details-portal), [Azure PowerShell](restore-account-continuous-backup.md#get-the-restore-details-powershell), and the [Azure CLI](restore-account-continuous-backup.md#get-the-restore-details-cli).
65-
36+
You can identify whether an account is restored and gets the restore details by using the [Azure portal](restore-account-continuous-backup.md#get-the-restore-details-portal), [Azure PowerShell](restore-account-continuous-backup.md#get-the-restore-details-powershell), and the [Azure CLI](restore-account-continuous-backup.md#get-the-restore-details-cli).
6637
- question: |
67-
What is the use of instanceId in the account definition?
38+
What is the use of `instanceId` in the account definition?
6839
answer: |
69-
At any point in time, an Azure Cosmos DB account's `accountName` property is globally unique while it's alive. After the account is deleted, it's possible to create another account with the same name. If that happens, `accountName` is no longer enough to identify an instance of an account.
70-
71-
The instance ID, or `instanceId`, is a property of an instance of an account. It's used to disambiguate across multiple accounts (live and deleted) if they have same name for restore. You can get the instance ID by running the `Get-AzCosmosDBRestorableDatabaseAccount` or `az cosmosdb restorable-database-account` command. The name attribute value denotes the instance ID.
72-
40+
[!INCLUDE[](includes/continuous-backup-restore-frequently-asked-questions-instanceid.md)]
7341
- question: |
7442
Is continuous backup supported for Azure Synapse Link enabled accounts?
7543
answer: |
76-
7744
No. Currently, continuous backup mode and Azure Synapse Link can't coexist in the same database account.
78-
- question: |
79-
Is continuous backup mode supported for API for Table or Gremlin?
80-
answer: |
81-
82-
Yes, currently it is in preview and restore is supported from PowerShell and the Azure CLI.
8345
additionalContent: |
84-
8546
## Next steps
8647
8748
* Learn more about [continuous backup](continuous-backup-restore-introduction.md) mode.
Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
---
2+
author: kanshiG
3+
ms.author: govindk
4+
ms.reviewer: mjbrown
5+
ms.service: cosmos-db
6+
ms.topic: include
7+
ms.date: 04/19/2023
8+
---
9+
10+
At any point in time, an Azure Cosmos DB account's `accountName` property is globally unique while it's alive. After the account is deleted, it's possible to create another account with the same name. If that happens, `accountName` is no longer enough to identify an instance of an account.
11+
12+
The instance ID, or `instanceId`, is a property of an instance of an account. It's used to disambiguate across multiple accounts (live and deleted) if they have same name for restore. You can get the instance ID by running either of these commands:
13+
14+
```azurepowershell-interactive
15+
Get-AzCosmosDBRestorableDatabaseAccount
16+
```
17+
18+
```azurecli-interactive
19+
az cosmosdb restorable-database-account
20+
```
21+
22+
> [!NOTE]
23+
> The name attribute value denotes the instance ID.
Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
---
2+
author: kanshiG
3+
ms.author: govindk
4+
ms.reviewer: mjbrown
5+
ms.service: cosmos-db
6+
ms.topic: include
7+
ms.date: 04/19/2023
8+
---
9+
10+
After you submit the restore command and wait on the page, the status bar shows a message about a successfully restored account when the operation finishes. You can also search for the restored account and [track its status](../restore-account-continuous-backup.md#track-restore-status). While the restore is in progress, the account status is **Creating**. After the restore operation finishes, the account status changes to **Online**.
11+
12+
For PowerShell and the Azure CLI, you can track the progress of a restore operation by using the [`az cosmosdb show`](/cli/azure/cosmosdb#az-cosmosdb-show) command:
13+
14+
```azurecli-interactive
15+
az cosmosdb show \
16+
--resource-group <resource-group> \
17+
--name <account-name>
18+
```
19+
20+
The `provisioningState` value is `Succeeded` when the account is online.
21+
22+
```json
23+
{
24+
"virtualNetworkRules": [],
25+
"writeLocations" : [
26+
{
27+
"documentEndpoint": "https://<accountname>.documents.azure.com:443/",
28+
"failoverpriority": 0,
29+
"id": "accountName" ,
30+
"isZoneRedundant" : false,
31+
"locationName": "West US 2",
32+
"provisioningState": "Succeeded"
33+
}
34+
]
35+
}
36+
```

0 commit comments

Comments
 (0)