Merge pull request #281189 from rajats22/backuupdates-07152024

AKS, Postgres and MySQL updates

Author: PMEds28

articles/backup/azure-kubernetes-service-cluster-restore.md

@@ -25,6 +25,8 @@ Azure Backup now allows you to back up AKS clusters (cluster resources and persi
 
 - 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.
 
+- 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**. 
+
 For more information on the limitations and supported scenarios, see the [support matrix](azure-kubernetes-service-cluster-backup-support-matrix.md).
 
 ## Restore the AKS clusters
@@ -35,7 +37,7 @@ To restore the backed-up AKS cluster, follow these steps:
 
    :::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.":::
 
-2. On the next page, click **Select backup instance**, and then select the *instance* that you want to restore.
+2. On the next page, select **Select backup instance**, and then select the *instance* that you want to restore.
 
    If the instance is available in both *Primary* and *Secondary Region*, select the *region to restore* too, and then select **Continue**.
 
@@ -70,7 +72,7 @@ To restore the backed-up AKS cluster, follow these steps:
 
    :::image type="content" source="./media/azure-kubernetes-service-cluster-restore/select-resources-to-restore-page.png" alt-text="Screenshot shows the Select Resources to restore page.":::
 
-6. If you seleted a recovery point for restore from *Vault-standard datastore*, then provide a *snapshot resource group* and *storage account* as the staging location.
+6. If you selected a recovery point for restore from *Vault-standard datastore*, then provide a *snapshot resource group* and *storage account* as the staging location.
 
    :::image type="content" source="./media/azure-kubernetes-service-cluster-restore/restore-parameters.png" alt-text="Screenshot shows the parameters to add for restore from Vault-standard storage.":::
 

articles/backup/backup-azure-backup-vault-troubleshoot.md

@@ -0,0 +1,31 @@
+---
+title: Troubleshoot Azure Backup Vault
+description: Symptoms, causes, and resolutions of the Azure Backup Vault related operations.
+ms.topic: troubleshooting
+ms.date: 07/18/2024
+ms.service: backup
+author: AbhishekMallick-MS
+ms.author: v-abhmallick
+---
+
+# Troubleshoot Azure Backup Vault related operations
+
+This article provides troubleshooting steps that help you resolve Azure Backup Vault management errors.
+
+## Common user errors
+
+#### Error code: UserErrorSystemIdentityNotEnabledWithVault
+
+**Possible Cause:** 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 operation fails with this error. 
+
+**Resolution:** To resolve this error, enable the System Identity of the Backup Vault and reassign 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. 
+
+#### Error code: UserErrorUserIdentityNotFoundOrNotAssociatedWithVault
+
+**Possible Cause:** Backup Instances can be created with a User Identity having all the required 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 is deleted or not attached with the Backup Vault.  
+
+**Resolution:** To resolve this error, 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. 
+
+## Next steps
+
+- [About Azure Backup Vault](create-manage-backup-vault.md)

articles/backup/backup-azure-mysql-flexible-server-restore.md

@@ -13,6 +13,10 @@ This article describes how to restore the Azure Database for MySQL - Flexible Se
 
 Learn more about the [supported scenarios. considerations, and limitations](backup-azure-mysql-flexible-server-support-matrix.md).
 
+## Prerequisites
+
+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**.
+
 ## Restore MySQL - Flexible Server database
 
 To restore the database, follow these steps:
@@ -44,4 +48,4 @@ To restore the database, follow these steps:
 
 ## Next steps
 
-- [Back up the Azure Database for MySQL - Flexible Server (preview)](backup-azure-mysql-flexible-server.md)
+- [Back up the Azure Database for MySQL - Flexible Server (preview)](backup-azure-mysql-flexible-server.md)

articles/backup/restore-azure-database-postgresql-flex.md

@@ -14,7 +14,9 @@ This article explains how to restore an Azure PostgreSQL -flex server backed up
 
 ## Prerequisites
 
-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).
+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).
+
+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**.
 
 ## Restore Azure PostgreSQL-Flexible database
 
@@ -40,7 +42,35 @@ Follow these steps:
 
 1. Submit the Restore operation and track the triggered job under **Backup jobs**.
    :::image type="content" source="./media/restore-azure-database-postgresql-flex/validate.png" alt-text="Screenshot showing the validate process page.":::
+
+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:
+
+   - 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.
+     
+   - 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**
+     
+   - The Third File **_roles**. Has roles backed up using pg_dumpall
+ 
+   - The Fourth file **_schemas**. backed up using pg_dumpall
+     
+   - The Fifth file **_tablespaces**. Has the tablespaces backed up using pg_dumpall
+
+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
+
+   `pg_restore -h <hostname> -U <username> -d <db name> -Fd -j <NUM>  -C  <dump directory>`
+
+   * `-Fd`: The directory format.   
+   * `-j`: The number of jobs.   
+   * `-C`: Begin the output with a command to create the database itself and then reconnect to it.     
+
+   Here's an example of how this syntax might appear:
+
+   `pg_restore -h <hostname>  -U <username> -j <Num of parallel jobs> -Fd -C -d <databasename> sampledb_dir_format`
+
+   If you have more than one database to restore, re-run the earlier command for each database.
+
+   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.
 
 ## Next steps
 
-[Support matrix for PostgreSQL-Flex database backup by using Azure Backup](backup-azure-database-postgresql-flex-support-matrix.md).
+[Support matrix for PostgreSQL-Flex database backup by using Azure Backup](backup-azure-database-postgresql-flex-support-matrix.md).

articles/backup/toc.yml

@@ -811,6 +811,8 @@
       href: backup-azure-troubleshoot-slow-backup-performance-issue.md
     - name: Azure Backup Server
       href: backup-azure-mabs-troubleshoot.md
+    - name: Azure Backup Vault
+      href: backup-azure-backup-vault-troubleshoot.md
     - name: System Center DPM
       href: backup-azure-scdpm-troubleshooting.md
     - name: Azure File share