update in aks backup manage and postgres support matrix

Author: rajats22

articles/backup/azure-kubernetes-service-backup-troubleshoot.md

@@ -167,9 +167,9 @@ These error codes appear due to issues on the Backup Extension installed in the
 
 ### BackupPluginPodRestartedDuringBackupError
 
-**Cause**: Backup Extension Pod (dataprotection-microsoft-kubernetes-agent) in your AKS cluster experiencing instability due to insufficient CPU/Memory resources on its current node, leading to OOM (Out of Memory) kill incidents. This could be because of lower compute requested by the backup extension pod.
+**Cause**: Backup Extension Pod (dataprotection-microsoft-kubernetes-agent) in your AKS cluster experiencing instability due to insufficient CPU/Memory resources on its current node, leading to OOM (Out of Memory) kill incidents. This could be because of either lower compute requested by the backup extension pod or a large number of resources of a particular type are being backed up or restored.
 
-**Recommended action**: To address this, we recommend increasing the compute values allocated to this pod. By doing so, it will be automatically provisioned on a different node within your AKS cluster with ample compute resources available.
+**Recommended action**: To address this, first check the backup logs stored in the blob container provided as input in extension installation to verify if the issue is due to large number of resources. If thats the issue then exclude these resources from the backup configuration and reattempt the operation. Otherwise we recommend increasing the compute values allocated to this pod. By doing so, it will be automatically provisioned on a different node within your AKS cluster with ample compute resources available.
 
 The current value of compute for this pod is:
 

articles/backup/azure-kubernetes-service-cluster-manage-backups.md

@@ -102,26 +102,6 @@ To enable Trusted Access between Backup vault and AKS cluster, use the following
 
 Learn more about [other commands related to Trusted Access](/azure/aks/trusted-access-feature#trusted-access-feature-overview).
 
-## Monitor a backup operation
-
-The Azure Backup service creates a job for scheduled backups or if you trigger on-demand backup operation for tracking. To view the backup job status:
-
-1. Go to the **Azure Business Continuity Center** and select **Protected Items** under **Protection Inventory**.
-
-   The **Protected Items** blade shows all the backup instances created across the subscriptions. Use the filters to access the backup instance you would like to take a look at. Select on the protected item and open it.
-
-   :::image type="content" source="./media/backup-managed-disks/jobs-dashboard.png" alt-text="Screenshot shows the jobs dashboard." lightbox="./media/backup-managed-disks/jobs-dashboard.png":::
-
-1. Now select on the **Associated Items** to open up the dashboard for the backup instance. Here you can see the backup jobs for the last seven days. 
-
-1. To view the status of the backup operation, select **View all** to show ongoing and past jobs of this backup instance.
-
-   ![Screenshot shows how to select the view all option.](./media/backup-managed-disks/view-all.png)
-
-1. Review the list of backup and restore jobs and their status. Select a job from the list of jobs to view job details.
-
-   ![Screenshot shows how to select a job to see details.](./media/backup-managed-disks/select-job.png)
-
 ## Manage operations using the Azure portal
 
 This section describes several Azure Backup supported management operations that make it easy to manage Azure Kubernetes Service cluster backups.
@@ -167,7 +147,7 @@ After you trigger the restore operation, the backup service creates a job for tr
     ![Screenshot shows the list of jobs.](./media/restore-managed-disks/list-of-jobs.png)
 
 
-### Monitor AKS backup related jobs with the completed with warnings status
+### Monitor backup and restore jobs with the completed with warnings status
 
 When a scheduled or an on-demand backup or restore operation is performed, a job is created corresponding to the operation to track its progress. If there is a failure, these jobs allow you to identify error codes and fix issues to run a successful job later. 
 
@@ -212,6 +192,10 @@ There are three ways by which you can stop protecting an Azure Disk:
 
 - **Stop Protection and Delete Data**: This option helps you stop all future backup jobs from protecting your clusters and delete all the recovery points. You won't be able to restore the disk or use the **Resume backup** option.
 
+> [!NOTE]
+>
+> Even if AKS Backup is stopped or backups fail, the last restore point is always retained beyond the defined retention period, ensuring at least one restore point remains available.
+
 #### Stop Protection and Retain Data
 
 1. Go to the **Azure Business Continuity Center** and select **Protected Items** under **Protection Inventory**.

articles/backup/backup-azure-database-postgresql-flex-support-matrix.md

@@ -21,13 +21,11 @@ Azure Database for PostgreSQL - Flexible server backup is now available in all p
 
 - PostgreSQL Flexible Server backup data can be recovered in user specified storage containers that can be used to rebuild the PostgreSQL flexible server. You can restore this data as a new PostgreSQL - flexible server with the database native tools.
 
-- Only weekly backups are supported with option to opt for one day in the week on which backup is initiated.
+- Only weekly backups are supported with option to opt for only one day in the week on which backup is initiated.
 
 - Both Cross Region and Cross Subscription backups are supported.
 
-- Recommended limit for the maximum server size is 4 TB.
-
-- Recommended backup frequency for backing up a server is Weekly. In case you opt for Daily backup and observe failures, we recommend decreasing the frequency while relying on automated backup solution to achieve required RPO.  
+- Recommended limit for the maximum server size is 4 TB.  
 
 - PostgreSQL - Flexible servers encrypted by Customer Managed Key are supported.