Skip to content

Commit 7b6681e

Browse files
authored
Update how-to-restore-in-account-continuous-backup.md
Fixed duplicate tab
1 parent b29b51b commit 7b6681e

File tree

1 file changed

+2
-5
lines changed

1 file changed

+2
-5
lines changed

articles/cosmos-db/how-to-restore-in-account-continuous-backup.md

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -957,12 +957,9 @@ To restore a table, update the following template as follows:
957957

958958
:::zone-end
959959

960-
961960
> [!NOTE]
962961
> Use [az cosmosdb restorable-database-account list](/cli/azure/cosmosdb/restorable-database-account#az-cosmosdb-restorable-database-account-list) to retrieve a list of instance identifiers for all live and deleted restorable database accounts.
963962
964-
## Deploy the template
965-
966963
1. Deploy the template by using [az deployment group create](/cli/azure/deployment/group#az-deployment-group-create):
967964

968965
```azurecli-interactive
@@ -971,13 +968,13 @@ To restore a table, update the following template as follows:
971968
--template-file <template-filename>
972969
```
973970
974-
971+
---
975972
976973
## Track the status of a restore operation
977974
978975
When a point-in-time restore is initiated for a deleted container or database, the operation is identified as an **InAccount** restore operation on the resource.
979976
980-
### [Azure portal](#tab/azure-portal)
977+
### [Azure portal](#tab/azure-portal)
981978
982979
To get a list of restore operations for a specific resource, filter the activity log of the account by using the **InAccount Restore Deleted** search filter and a time filter. The list that's returns includes the **UserPrincipalName** field, which identifies the user who initiated the restore operation. For more information about how to access activity logs, see [Audit point-in-time restore actions](audit-restore-continuous.md#audit-the-restores-that-were-triggered-on-a-live-database-account).
983980

0 commit comments

Comments
 (0)