Merge pull request #299094 from MicrosoftDocs/main

Publish to live, Wednesday 4AM PST, 4/30

Author: PMEds28

articles/app-service/configure-language-java-deploy-run.md

@@ -401,25 +401,9 @@ To configure the app setting from the Maven plugin, add setting/value tags in th
 
 ::: zone-end
 
-Developers running a single application with one deployment slot in their App Service plan can use the following options:
-
-- B1 and S1 instances: `-Xms1024m -Xmx1024m`
-- B2 and S2 instances: `-Xms3072m -Xmx3072m`
-- B3 and S3 instances: `-Xms6144m -Xmx6144m`
-- P1v2 instances: `-Xms3072m -Xmx3072m`
-- P2v2 instances: `-Xms6144m -Xmx6144m`
-- P3v2 instances: `-Xms12800m -Xmx12800m`
-- P1v3 instances: `-Xms6656m -Xmx6656m`
-- P2v3 instances: `-Xms14848m -Xmx14848m`
-- P3v3 instances: `-Xms30720m -Xmx30720m`
-- I1 instances: `-Xms3072m -Xmx3072m`
-- I2 instances: `-Xms6144m -Xmx6144m`
-- I3 instances: `-Xms12800m -Xmx12800m`
-- I1v2 instances: `-Xms6656m -Xmx6656m`
-- I2v2 instances: `-Xms14848m -Xmx14848m`
-- I3v2 instances: `-Xms30720m -Xmx30720m`
-
-When tuning application heap settings, review your App Service plan details. Consider the needs of multiple applications and deployment slots to find the optimal allocation of memory.
+By default, App Service sets the JVM Max Heap size to 70% of the total memory available for the App Service Plan. To disable the default setting, you can use app setting WEBSITE_DISABLE_JAVA_HEAP_CONFIGURATION=”true".
+
+Enhancing your application's performance on the platform may involve adjusting the heap size to better suit your specific needs. When tuning application heap settings, please review your App Service plan details and consider the requirements of multiple applications and deployment slots to find the optimal memory allocation.
 
 ### Turn on web sockets
 

articles/backup/azure-data-lake-storage-backup-support-matrix.md

@@ -2,7 +2,7 @@
 title: Support matrix for Azure Data Lake Storage Vaulted Backup (preview)
 description: Learn about the  regional availability, supported scenarios, and limitations for vaulted backups of Azure Data Lake Storage (preview).
 ms.topic: reference
-ms.date: 04/16/2025
+ms.date: 04/30/2025
 ms.custom: references_regions, engagement-fy24
 ms.service: azure-backup
 author: jyothisuri
@@ -42,7 +42,7 @@ Azure Data Lake Storage protection (preview) has the following supported and uns
 
 - Any new containers that get created after backup configuration for the storage account aren't backed up automatically. To enable the backup operation for the new containers, modify the protection of the storage account. 
 - The storage accounts to be backed up must contain a *minimum of one container*. If the storage account doesn't contain any containers or if no containers are selected, an error might appear when you configure backup.
-- The backup operation isn't supported for blobs that are uploaded by using [Data Lake Storage APIs](/rest/api/storageservices/data-lake-storage-gen2). 
+- Object Replication fails to register changes when a storage account or container is deleted and recreated with the same name between two consecutive backups, causing recovery points to retain older blobs and versions. Similarly, when you rename the parent path of blobs created via async copy, those blobs are excluded from recovery points.
 - Backup vaults with User-Assigned Managed Identity (UAMI) aren't compatible with Azure Blob Vaulted backups. Only System-Assigned Managed Identity (SAMI) works, because the vault needs to access the storage account where the blobs are stored. The vault uses its system-assigned managed identity for this access.
 - Enabling backups isn't supported for the blob container that are configured with native replication using data factory.
 - You can protect the storage account with the vault in another subscription but in the same region as storage account.

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

@@ -2,7 +2,7 @@
 title: Azure Database for PostgreSQL- Flexible server support matrix
 description: Provides a summary of support settings and limitations of Azure Database for PostgreSQL- Flexible server backup.
 ms.topic: reference
-ms.date: 04/11/2025
+ms.date: 04/30/2025
 ms.custom: references_regions, ignite-2024
 ms.service: azure-backup
 author: jyothisuri
@@ -41,6 +41,22 @@ Azure Database for PostgreSQL – Flexible Server backups include the following
 - Vaulted backups support full backups only; incremental or differential backups aren't supported.
 
 
+### Restore limitations
+- The use of **create role** scripts for `azure_su`, `azure_pg_admin`, `replication`, `localadmin`, and `Entra Admin` causes the following errors  during restoration on another flexible server, which you can safely ignore.
+
+  - `role "azure_pg_admin" already exists.`
+  - `role "azuresu" already exists.`
+  - `role "replication" already exists.`
+  - `ERROR: must be superuser to create superusers`
+  - `ERROR: Only roles with privileges of role "azuresu" may grant privileges as this role. permission denied granting privileges as role "azuresu"`
+  - `ERROR: permission denied granting privileges as role "azuresu" SQL state: 42501 Detail: Only roles with privileges of role "azuresu" may grant privileges.`
+  - `Ignore any errors related to pg_catalog, pg _aadauth extensions as it is owned by azure_su and localadmin does not have access to directly create this extension on flexible server, but these are automatically created on new flexible servers or when you enable Microsoft entra authentication.`
+  - `ERROR: Only roles with the ADMIN option on role "pg_use_reserved_connections" may grant this role. permission denied to grant role "pg_use_reserved_connections"`
+  - `ERROR: permission denied to grant role "pg_use_reserved_connections" SQL state: 42501 Detail: Only roles with the ADMIN option on role "pg_use_reserved_connections" may grant this role.`
+
+- In PostgreSQL **community version 16**, the requirement for superuser privileges to set the Bypass Row -level security (RLS) attribute was removed. So, in versions 16 and higher, you can grant the Bypass RLS to azure_pg_admin allowing others to set the RLS. For versions lower than 16, the bypasses attribute is granted only to the server admin and no other nonsuperuser roles. 
+- If you're using Entra Admins after restoration, you might encounter the **Owner Change Issue** : As a workaround, use the **grant** option to provide ownership. 
+
 
 ## Next steps
 

articles/backup/backup-azure-system-state-troubleshoot.md

@@ -3,7 +3,7 @@ title: Troubleshoot System State Backup
 description: In this article, learn how to troubleshoot issues in System State Backup for on-premises Windows servers.
 ms.reviewer: srinathv
 ms.topic: troubleshooting
-ms.date: 07/22/2019
+ms.date: 04/30/2025
 author: jyothisuri
 ms.author: jsuri
 ---
@@ -34,6 +34,8 @@ We recommend you perform the following validation steps, before you start troubl
 
 ### Limitation
 
+Here are the limitations for System State backups:
+
 - Recovering to different hardware using System State recovery isn't recommended by Microsoft
 - System State backup currently supports "on-premises" Windows servers. This functionality isn't available for Azure VMs.
 
@@ -49,7 +51,7 @@ Ensure Windows Server Backup is installed and enabled in the server. To check th
 Get-WindowsFeature Windows-Server-Backup
 ```
 
-If the output displays the **Install State** as **available**, then it means Windows Server backup feature is available for the installation but not installed on the server. However, if Windows Server Backup isn't installed, then use one of the methods below to install it.
+If the output displays the **`Install State`** as **available**, then it means Windows Server backup feature is available for the installation but not installed on the server. However, if Windows Server Backup isn't installed, then use one of the methods below to install it.
 
 #### Method 1: Install Windows Server Backup using PowerShell
 
@@ -61,7 +63,7 @@ To install Windows Server Backup using PowerShell, run the following command:
 
 #### Method 2: Install Windows Server Backup using Server Manager
 
-To install Windows Server Backup using Server Manager, perform the following steps:
+To install Windows Server Backup using Server Manager, follow these steps:
 
 1. In **Server Manger**, select **Add roles and features**. The **Add roles and features wizard** appears.
 
@@ -99,48 +101,48 @@ Microsoft Software Shadow Copy Provider(SWPRV) | Manual
 
 ### Validate Windows Server Backup status
 
-To validate Windows Server Backup status, perform the following steps:
+To validate Windows Server Backup status, follow these steps:
 
-- Ensure WSB PowerShell is running
+1. Ensure WSB PowerShell is running
 
-  - Run `Get-WBJob` from an elevated PowerShell and make sure it doesn't return the following error:
+   - Run `Get-WBJob` from an elevated PowerShell and make sure it doesn't return the following error:
 
-    > [!WARNING]
-    > Get-WBJob: The term 'Get-WBJob' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
+     > [!WARNING]
+     > Get-WBJob: The term 'Get-WBJob' isn't recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
 
-    - If it fails with this error, then reinstall the Windows Server Backup feature on the server machine as mentioned in step 1 of the prerequisites.
+   - If it fails with this error, then reinstall the Windows Server Backup feature on the server machine as mentioned in step 1 of the prerequisites.
 
-  - Ensure WSB backup is working properly, by running the following command from an elevated command prompt:
+1. Ensure WSB backup is working properly, by running the following command from an elevated command prompt:
 
-      `wbadmin start systemstatebackup -backuptarget:X: -quiet`
+   `wbadmin start systemstatebackup -backuptarget:X: -quiet`
 
-      > [!NOTE]
-      > Replace X with the drive letter of the volume where you want to store the system state back up image.
+   > [!NOTE]
+   > Replace X with the drive letter of the volume where you want to store the system state backup image.
 
-    - Periodically check the status of the job by running `Get-WBJob` command from elevated PowerShell
-    - After backup job completes check the final status of the job by running `Get-WBJob -Previous 1` command
+1. Periodically check the status of the job by running `Get-WBJob` command from elevated PowerShell
+1. After backup job completes, check the final status of the job by running `Get-WBJob -Previous 1` command
 
 If the job fails, it indicates a WSB issue that would result in MARS agent System State Backups failure.
 
 ## Common errors
 
-### VSS Writer timeout error
+### VSS Writer time-out error
 
 | Symptom | Cause | Resolution
 | -- | -- | --
-| - MARS agent fails with error message: "WSB job failed with VSS errors. Check VSS event logs to resolve the failure"<br/><br/> - Following error log is present in VSS Application event logs: "A VSS writer has rejected an event with error 0x800423f2, the writer's timeout expired between the Freeze and Thaw events."| VSS writer is unable to complete in time due to lack of CPU and memory resources on the machine <br/><br/> Another backup software is already using the VSS writer, as a result snapshot operation could not complete for this backup | Wait for CPU/memory to be freed up on system or abort the processes taking too much memory/CPU and try the operation again. <br/><br/>  Wait for the ongoing backup to complete and try the operation at a later point when no backups are running on the machine.
+| - MARS agent fails with error message: "WSB job failed with VSS errors. Check VSS event logs to resolve the failure"<br/><br/> - Following error log is present in VSS Application event logs: "A VSS writer has rejected an event with error 0x800423f2, the writer's time-out expired between the Freeze and Thaw events."| VSS writer is unable to complete in time due to lack of CPU and memory resources on the machine <br/><br/> Another backup software is already using the VSS writer, as a result snapshot operation couldn't complete for this backup | Wait for CPU/memory to be freed up on system or abort the processes taking too much memory/CPU and try the operation again. <br/><br/>  Wait for the ongoing backup to complete and try the operation at a later point when no backups are running on the machine.
 
 ### Insufficient disk space to grow shadow copies
 
 | Symptom | Resolution
 | -- | --
-| - MARS agent fails with error message: Backup failed as the shadow copy volume could not grow due to insufficient disk space on volumes containing system files <br/><br/> - Following error/warning log is present in volsnap system event logs: "There was insufficient disk space on volume C: to grow the shadow copy storage for shadow copies of C: due to this failure all shadow copies of volume C: are at risk of being deleted" | - Free up space in the highlighted volume in the event log so that there's sufficient space for shadow copies to grow while backup is in progress <br/><br/> -  While configuring shadow copy space we can restrict the amount of space used for shadow copy. For more information, see this [article](/windows-server/administration/windows-commands/vssadmin-resize-shadowstorage)
+| - MARS agent fails with error message: Backup failed as the shadow copy volume couldn't grow due to insufficient disk space on volumes containing system files <br/><br/> - Following error/warning log is present in volsnap system event logs: "There was insufficient disk space on volume C: to grow the shadow copy storage for shadow copies of C: due to this failure all shadow copies of volume C: are at risk of being deleted" | - Free up space in the highlighted volume in the event log so that there's sufficient space for shadow copies to grow while backup is in progress <br/><br/> -  While configuring shadow copy space we can restrict the amount of space used for shadow copy. For more information, see this [article](/windows-server/administration/windows-commands/vssadmin-resize-shadowstorage)
 
 ### EFI partition locked
 
 | Symptom | Resolution
 | -- | --
-| MARS agent fails with error message: "System state backup failed as the EFI system partition is locked. This can be due to system partition access by a third-party security or back up software" | - If the issue is due to a third-party security software, then you need to contact the Anti Virus vendor so that they can allow MARS agent <br/><br/> - If a third-party backup software is running, then wait for it to finish and then retry back up
+| MARS agent fails with error message: System state backup operation failed as the EFI system partition is locked. This can be due to system partition access by a third-party security or back up software. | - If the issue is due to a third-party security software, then you need to contact the Anti Virus vendor so that they can allow MARS agent <br/><br/> - If a third-party backup software is running, then wait for it to finish and then retry backup.
 
 ## Next steps