Addressed PM review inputs

AbhishekMallick01 · AbhishekMallick01 · commit 35773cb9a7a2 · 2025-05-06T17:58:29.000+05:30
diff --git a/articles/backup/sap-ase-backup-support-matrix.md b/articles/backup/sap-ase-backup-support-matrix.md
@@ -3,7 +3,7 @@ title: SAP ASE Backup support matrix
 description: In this article, learn about the supported scenarios and limitations when you use Azure Backup to back up SAP ASE databases on Azure VMs.
 ms.topic: reference
 ms.custom: references_regions, ignite-2024
-ms.date: 05/14/2025
+ms.date: 05/13/2025
 ms.service: azure-backup
 author: jyothisuri
 ms.author: jsuri
@@ -21,15 +21,15 @@ This article summarizes the scenarios supported and limitations present when you
 | **Scenario** | **Supported  configurations** | **Unsupported  configurations** |
 | ------- | -------- | -------- |
 | **Topology** | SAP ASE Database running in Azure Linux VMs only. | Windows |
-| **Regions** | **Americas** – Canada Central, Canada East, Brazil South.<br> <br> **Asia Pacific** – Australia Central, Australia Central 2, Australia East, Australia Southeast, Japan East, Japan West, Korea Central, Korea South, East Asia, Southeast Asia, Central India, South India, West India. <br><br> **Europe** – West Europe, North Europe, France Central, France South, UK South, UK West, Germany North, Germany West Central, Switzerland North, Switzerland West, Central Switzerland North, Norway East, Norway West, Sweden Central, Sweden South. <br><br> **Africa/ME** - South Africa North, South Africa West, UAE North, UAE Central. | Central US, East US 2, East US, North Central US, South Central US, West US 2, West US 3, West Central US, West US, Germany Central, Germany Northeast, US Gov IOWA, Azure Gov, China East, China East 2, China East 3, China North, China North 2, China North 3. |
+| **Regions** | **Americas** – Canada Central, Canada East, Brazil South.<br> <br> **Asia Pacific** – Australia Central, Australia Central 2, Australia East, Australia Southeast, Japan East, Japan West, Korea Central, Korea South, East Asia, Southeast Asia, Central India, South India, West India. <br><br> **Europe** – West Europe, North Europe, France Central, France South, UK South, UK West, Germany North, Germany West Central, Switzerland North, Switzerland West, Central Switzerland North, Norway East, Norway West, Sweden Central, Sweden South. <br><br> **Africa/ME** - South Africa North, South Africa West, UAE North, UAE Central, Central US, East US 2, East US, North Central US, South Central US, West US 2, West US 3, West Central US, West US, China East, China East 2, China East 3, China North, China North 2, China North 3, US GOV Arizona, US GOV Texas, US GOV Virginia. | Germany Central, Germany Northeast, US Gov IOWA, Azure Gov. |
 | **OS versions** | SLES 12 with SP0, SP1, SP2, SP3, SP4, and SP5; SLES 15 with SP0, SP1, SP2, SP3, SP4, and SP5, 15.6 <br><br> RHEL 7.1, 7.2, 7.3, 7.4, 7.6, 7.7, 7.9, 8.1, 8.2, 8.3, 8.4,8.5, 8.6, 8.7, 8.8, 8.9, 8.10, 9.2 |  |
 | **ASE versions** | SAP Adaptive Server Enterprise 16.0 SP02, SP03, SP04 |  |
-| **ASE Instances** | A single SAP ASE instance on a single Azure Virtual Machine (VM). | HA and multi SID on single VM isn't currently supported. |
+| **ASE Instances** | A single SAP ASE instance on a single Azure Virtual Machine (VM). <br><br> Multi SID on single VM. | HA on single VM isn't currently supported. |
 | **Backup types** | Full, Differential, and Log backups. | Incremental, archival support is currently not available. |
 | **Restore types** | ALR-Alternate Location Restore, OLR-Original Location Restore (In-Place), Restore as Files.  |  |
 | **Cross Subscription Restore** | Supported via the Azure portal.<br>Cross Subscription Restore to Paired Region. |  Region of Choice isn't supported. |
 | **Number of full backups per day** | One scheduled backup. <br><br> Three on-demand backups. <br> <br> We recommend not to trigger more than three backups per day. However, to allow user retries for failed attempts, hard limit for on-demand backups is set to nine attempts. |
-| **ASE deployments** | Standalone | HA, Multi SID on Single VM. |
+| **ASE deployments** | Standalone, Multi SID on Single VM. | HA on Single VM. |
 | **Compression** | You can enable ASE Native compression via the Backup policy and when you take an on-demand Backup/Backup Now. In Preregistration Script, Compression Level is set to **Level 101** for Optimal results. |  |
 | **Striping Support** | You can increase your  backup throughput by enabling Striping configuration, which needs to be set in **Preregistration script** –  refer parameters **enable-striping** - Set to **true** and **stripesCount** set to 4 by Default and can be adjusted.  | |
 | **Azure CLI/PowerShell** |  | Azure CLI/PowerShell support is currently not available. |
diff --git a/articles/backup/sap-ase-database-about.md b/articles/backup/sap-ase-database-about.md
@@ -2,7 +2,7 @@
 title: About the SAP ASE (Sybase) database backup on Azure VMs
 description: In this article, learn about backing up SAP ASE (Sybase) databases that are running on Azure virtual machines.
 ms.topic: overview
-ms.date: 05/14/2025
+ms.date: 05/13/2025
 ms.service: azure-backup
 ms.custom:
   - ignite-2024
@@ -40,32 +40,25 @@ You can back up SAP ASE (Sybase) databases that are running inside an Azure VM a
 * The Azure VM that's running the SAP ASE server is registered with the vault, and the databases to be backed up are discovered. To enable the Azure Backup service to discover databases, a [preregistration script](https://go.microsoft.com/fwlink/?linkid=2173610) must be run on the ASE server as a root user.
 * This script creates the *AZUREWLBACKUPASEUSER* database user or uses the custom Backup user you already created. It then creates a corresponding key with the same name in *hdbuserstore*. To learn more about the functionality of the script, see [Back up SAP ASE (Sybase) databases in an Azure VM](sap-ase-database-backup.md).
 * The Azure Backup service now installs the Azure Backup plugin for ASE on the registered SAP ASE server.
-* The `AZUREWLBACKUPASEUSER` database user (created by the preregistration script or the custom Backup user you created, and added as input to the preregistration script) is used by the Azure Backup plugin for ASE to back up and restore. If you attempt to configure backup for SAP ASE (Sybase) databases without running this script, you might receive the UserErrorHanaScriptNotRun error.
+* The `AZUREWLBACKUPASEUSER` database user (created by the preregistration script or the custom Backup user you created, and added as input to the preregistration script) is used by the Azure Backup plugin for ASE to back up and restore. If you attempt to configure backup for SAP ASE (Sybase) databases without running this script, you might receive the UserErrorASEScriptNotRun error.
 * To configure a backup on the databases that you discovered, choose the required backup policy, and then enable backups.
 
-* After you configure the backup, the Azure Backup service sets up the following Backint parameters at the database level on the protected SAP ASE server:
-  * `[catalog_backup_using_backint:true]`
-  * `[enable_accumulated_catalog_backup:false]`
-  * `[parallel_data_backup_backint_channels:1]`
-  * `[log_backup_timeout_s:900)]`
-  * `[backint_response_timeout:7200]`
-
    > [!NOTE]
    > Ensure that these parameters aren't present at the host level. Host-level parameters override these parameters and might cause unexpected behavior.
 
 
-* The Azure Backup plugin for ASE maintains all the backup schedules and policy details. It triggers the scheduled backups and communicates with the ASE backup engine through the Backint APIs.
-* The ASE backup engine returns a Backint stream with the data to be backed up.
+* The Azure Backup plugin for ASE maintains all the backup schedules and policy details. It triggers the scheduled backups and communicates with the ASE backup engine through the APIs.
+* The ASE backup engine returns a stream with the data to be backed up.
 * All the scheduled backups and on-demand backups (triggered from the Azure portal) that are either full or differential are initiated via the Azure Backup plugin for ASE. However,  the ASE backup engine manages and triggers log backups.
-* Azure Backup for SAP ASE, because it's a Backint-certified solution, doesn't depend on underlying disk or VM types. ASE generates streams that actively perform the backup.
+* Azure Backup for SAP ASE, because it's a certified solution, doesn't depend on underlying disk or VM types. ASE generates streams that actively perform the backup.
 
 :::image type="content" source="./media/sap-ase-database-about/database-backup-architecture.png" alt-text="Diagram shows the SAP ASE Sybase database backup." lightbox="./media/sap-ase-database-about/database-backup-architecture.png":::
 
 ## Use Azure VM backup with Azure SAP ASE backup
 
 In addition to using SAP ASE backup in Azure, which provides database-level backup and recovery, you can use the Azure VM backup solution to back up the operating system and nondatabase disks.
 
-You can use the [Backint certified Azure SAP ASE backup solution](#backup-architecture-for-sap-ase-sybase-databases) for database backup and recovery.
+You can use the [certified Azure SAP ASE backup solution](#backup-architecture-for-sap-ase-sybase-databases) for database backup and recovery.
 
 You can use [an Azure VM backup](backup-azure-vms-introduction.md) to back up the operating system and other nondatabase disks. The VM backup is run once a day, and it backs up all disks, except the Write Accelerated operating system disks and ultra disks. Because you're backing up the database by using the Azure SAP ASE backup solution, you can take a file-consistent backup of only the operating system and nondatabase disks by using the [selective disk backup and restore for Azure VMs](selective-disk-backup-restore.md) feature.
 
diff --git a/articles/backup/sap-ase-database-backup-run-preregistration-quickstart.md b/articles/backup/sap-ase-database-backup-run-preregistration-quickstart.md
@@ -16,16 +16,13 @@ This quickstart describes how to run the preregistration script to prepare an SA
 
 The preregistration script for SAP ASE database backup using Azure Backup ensures the system is properly configured by setting up authentication, validating network connectivity, and installing necessary packages. It also supports private endpoints and prepares the database for seamless backup operations.
 
->[!Note]
->- Currently, the SAP ASE is available only in non-US public regions. Learn about the [supported regions](sap-ase-backup-support-matrix.md#scenario-support-for-sap-ase-sybase-databases-on-azure-vms).
->- Learn about the [supported configurations and scenarios for SAP ASE database backup](sap-ase-backup-support-matrix.md) on Azure VMs.
+Learn about the [supported configurations and scenarios for SAP ASE database backup](sap-ase-backup-support-matrix.md) on Azure VMs.
 
 ## Prerequisites
 
 Before you run the preregistration script, ensure that the following prerequisites are met:
 
-- [Download the latest preregistration script](https://aka.ms/preregscriptsapase) for Multiple Components on One System (MCOS)
- and Multi System Identifier (SID) support.
+- [Download the latest preregistration script](https://aka.ms/preregscriptsapase) for [Multi System Identifier (SID) support](sap-ase-backup-support-matrix.md#support-for-multiple-sap-ase-instances-on-a-single-host).
 - Run the SAP ASE backup configuration script on the virtual machine where ASE is installed.
 - Check if you're the root user for proper configuration and access.
 - Use the `-sn` or `--skip-network-checks` parameter when running the script, if your ASE setup uses Private Endpoints.
diff --git a/articles/backup/sap-ase-database-backup-tutorial.md b/articles/backup/sap-ase-database-backup-tutorial.md
@@ -2,7 +2,7 @@
 title: Tutorial - Back up SAP ASE (Sybase) database using Azure Business Continuity Center
 description: In this tutorial, learn how to back up an SAP ASE (Sybase) database that's running on an Azure virtual machine using Azure Business Continuity Center.
 ms.topic: tutorial
-ms.date: 05/14/2025
+ms.date: 05/13/2025
 ms.service: azure-backup
 ms.custom:
   - ignite-2024
@@ -14,9 +14,7 @@ ms.author: jsuri
 
 This tutorial describes how to back up an SAP Adaptive Server Enterprise (ASE) (Sybase) database that's running on an Azure Virtual Machine (VM) using [Azure Business Continuity Center](../business-continuity-center/business-continuity-center-overview.md).
 
->[!Note]
->- Currently, the SAP ASE is available only in non-US public regions. Learn about the [supported regions](sap-ase-backup-support-matrix.md#scenario-support-for-sap-ase-sybase-databases-on-azure-vms).
->- Learn about the [supported configurations and scenarios for SAP ASE database backup](sap-ase-backup-support-matrix.md) on Azure VMs.
+Learn about the [supported configurations and scenarios for SAP ASE database backup](sap-ase-backup-support-matrix.md) on Azure VMs.
 
 ## Prerequisites
 
diff --git a/articles/backup/sap-ase-database-manage.md b/articles/backup/sap-ase-database-manage.md
@@ -2,7 +2,7 @@
 title: Manage and monitor backed-up SAP ASE database using Azure portal
 description: In this article, learn the common tasks for managing and monitoring SAP ASE databases that are running on Azure virtual machines.
 ms.topic: how-to
-ms.date: 05/14/2025
+ms.date: 05/13/2025
 ms.service: azure-backup
 ms.custom:
   - ignite-2024
diff --git a/articles/backup/sap-ase-database-restore.md b/articles/backup/sap-ase-database-restore.md
@@ -171,7 +171,7 @@ To trigger Cross Subscription Restore to a Private Endpoint enabled vault, follo
    - Select the subscription of the target vault in which you want to restore.
    - Select the VNet of the target VM that you want to restore across subscription.
 
-1. After the Private Endpoint is created, [trigger restore](#restore-sap-ase-databases-on-azure-vms).
+1. After the Private Endpoint is created, [trigger restore](#restore-a-user-database).
 
 >[!Note]
 >By default, CSR is enabled on the Recovery Services vault. To update the Recovery Services vault restore settings, go to the **Recovery Services vault** > **Properties** > **Cross Subscription Restore** and then select **Update** to implement the required changes.
