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/backup/azure-kubernetes-service-cluster-restore.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,6 +25,8 @@ Azure Backup now allows you to back up AKS clusters (cluster resources and persi
25
25
26
26
- You must [install the Backup Extension](azure-kubernetes-service-cluster-manage-backups.md#install-backup-extension) in the target AKS cluster. Also, you must [enable Trusted Access](azure-kubernetes-service-cluster-manage-backups.md#register-the-trusted-access) between the Backup vault and the AKS cluster.
27
27
28
+
- In case you are trying to restore a backup stored in Vault Tier, you need to provide a storage account in input as a staging location. Backup data is stored in the Backup vault as a blob within the Microsoft tenant. During a restore operation, the backup data is copied from one vault to staging storage account across tenants. Ensure that the staging storage account for the restore has the **AllowCrossTenantReplication** property set to **true**.
29
+
28
30
For more information on the limitations and supported scenarios, see the [support matrix](azure-kubernetes-service-cluster-backup-support-matrix.md).
29
31
30
32
## Restore the AKS clusters
@@ -35,7 +37,7 @@ To restore the backed-up AKS cluster, follow these steps:
35
37
36
38
:::image type="content" source="./media/azure-kubernetes-service-cluster-restore/start-kubernetes-cluster-restore.png" alt-text="Screenshot shows how to start the restore process.":::
37
39
38
-
2. On the next page, click**Select backup instance**, and then select the *instance* that you want to restore.
40
+
2. On the next page, select**Select backup instance**, and then select the *instance* that you want to restore.
39
41
40
42
If the instance is available in both *Primary* and *Secondary Region*, select the *region to restore* too, and then select **Continue**.
description: Symptoms, causes, and resolutions of the Azure Backup Vault related operations.
4
+
ms.topic: troubleshooting
5
+
ms.date: 07/18/2024
6
+
ms.service: backup
7
+
author: Rajat Shrivastava
8
+
ms.author: rajats
9
+
---
10
+
11
+
# Troubleshoot Azure Backup Vault Related Operations
12
+
13
+
This article provides troubleshooting steps that help you resolve Azure Backup Vaulte management errors.
14
+
15
+
### Common User Errors
16
+
17
+
## UserErrorSystemIdentityNotEnabledWithVault
18
+
19
+
**Possible Causes:** Backup Vault is created with System Identity enabled by default. This error appears when System Identity of the Backup Vault is in a disabled state and a backup related starts to fail with this error.
20
+
21
+
**Resolution:** To resolve this error, please enable the System Identity of the Backup Vault and re-assign all the necessary roles to it. Else use a User Identity in its place with all the roles assigned and update Managed Identity for all the Backup Instances using the now disabled System Identity.
**Possible Causes:** Backup Instances can be created with a User Identity having all the requried roles assigned to it. In addition, User Identity can also be used for operations like Encryption using a Customer Managed Key. This error appears when the particular User Identity has been deleted or not attached with the Backup Vault.
26
+
27
+
**Resolution:** To resolve this error, please assign the same or alternate User Identity to the Backup Vault and update the Backup Instance to use the new identity in latter case. Otherwise, enable the System Identity of the Backup Vault, update the Backup Instance and assign all the necessary roles to it.
Copy file name to clipboardExpand all lines: articles/backup/backup-azure-mysql-flexible-server-restore.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,6 +13,10 @@ This article describes how to restore the Azure Database for MySQL - Flexible Se
13
13
14
14
Learn more about the [supported scenarios. considerations, and limitations](backup-azure-mysql-flexible-server-support-matrix.md).
15
15
16
+
## Pre-requisites
17
+
18
+
1. Backup data is stored in the Backup vault as a blob within the Microsoft tenant. During a restore operation, the backup data is copied from one storage account to another across tenants. Ensure that the target storage account for the restore has the **AllowCrossTenantReplication** property set to **true**.
Copy file name to clipboardExpand all lines: articles/backup/restore-azure-database-postgresql-flex.md
+32-2Lines changed: 32 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,10 +14,12 @@ This article explains how to restore an Azure PostgreSQL -flex server backed up
14
14
15
15
## Prerequisites
16
16
17
-
Before you restore from Azure Database for PostgreSQL Flexible server backups, ensure that you have the required [permissions for the restore operation](backup-azure-database-postgresql-flex-overview.md#permissions-for-backup).
17
+
1.Before you restore from Azure Database for PostgreSQL Flexible server backups, ensure that you have the required [permissions for the restore operation](backup-azure-database-postgresql-flex-overview.md#permissions-for-backup).
18
18
19
-
## Restore Azure PostgreSQL-Flexible database
19
+
2. Backup data is stored in the Backup vault as a blob within the Microsoft tenant. During a restore operation, the backup data is copied from one storage account to another across tenants. Ensure that the target storage account for the restore has the **AllowCrossTenantReplication** property set to **true**.
20
20
21
+
## Restore Azure PostgreSQL-Flexible database
22
+
**
21
23
Follow these steps:
22
24
23
25
1. Go to **Backup vault** > **Backup Instances**. Select the PostgreSQL-Flex server to be restored and select **Restore**.
@@ -40,6 +42,34 @@ Follow these steps:
40
42
41
43
1. Submit the Restore operation and track the triggered job under **Backup jobs**.
42
44
:::image type="content" source="./media/restore-azure-database-postgresql-flex/validate.png" alt-text="Screenshot showing the validate process page.":::
45
+
46
+
1. Once the job is finished, the backed up data is restored into the storage account. Below are the set of files recovered in your storage account after the restore:
47
+
48
+
- The first file is a marker or timestamp file that gives the customer the time the backup was taken at. The file cannot be restored but if opened with a text editor should tell the customer the UTC time when the backup was taken.
49
+
50
+
- The Second file **_database_** is an individual database backup for database called tempdata2 taken using pg_dump. Each database has a separate file with format **– {backup_name}_database_{db_name}.sql**
51
+
52
+
- The Third File **_roles**. Has roles backed up using pg_dumpall
53
+
54
+
- The Fourth file **_schemas**. backed up using pg_dumpall
55
+
56
+
- The Fifth file **_tablespaces**. Has the tablespaces backed up using pg_dumpall
57
+
58
+
1. Post restoration completion to the target storage account, you can use pg_restore utility to restore an Azure Database for PostgreSQL flexible server database from the target. Use the following command to connect to an existing postgresql flexible server and an existing database
If you have more than one database to restore, re-run the earlier command for each database.
71
+
72
+
Also, by using multiple concurrent jobs **-j**, you can reduce the time it takes to restore a large database on a multi-vCore target server. The number of jobs can be equal to or less than the number of vCPUs that are allocated for the target server.
0 commit comments