Addressed Peer-review inputs - Commit 2

AbhishekMallick01 · AbhishekMallick01 · commit e738c4be46be · 2025-05-07T18:15:19.000+05:30
diff --git a/articles/backup/sap-ase-database-about.md b/articles/backup/sap-ase-database-about.md
@@ -93,7 +93,7 @@ With Cross-Subscription Restore (CSR), you can restore SAP ASE databases to any
 >- Cross-Subscription Restore can be initiated directly from the Recovery Services vault.
 >- Cross Regional Restore (CRR) with CSR isn't supported.
 
-Learn how to [trigger Cross Subscription Restore to a Private Endpoint enabled vault](sap-ase-database-restore.md#restore-to-a-private-endpoint-enabled-vault-in-a-different-subscription).
+Learn how to [trigger Cross Subscription Restore to a private endpoint enabled vault](sap-ase-database-restore.md#restore-to-a-private-endpoint-enabled-vault-in-a-different-subscription).
 
 ## Next steps
 
diff --git a/articles/backup/sap-ase-database-backup-run-preregistration-quickstart.md b/articles/backup/sap-ase-database-backup-run-preregistration-quickstart.md
@@ -12,9 +12,9 @@ ms.author: jsuri
 
 # Quickstart: Run the preregistration script for SAP ASE (Sybase) database backup in Azure Cloud Shell
 
-This quickstart describes how to run the preregistration script to prepare an SAP Adaptive Server Enterprise (ASE) (Sybase) database configuration for backup on Azure VMs using Azure Backup.
+This quickstart describes how to run the preregistration script to prepare an SAP Adaptive Server Enterprise (ASE) (Sybase) database configuration for backup on Azure VMs using Azure Cloud Shell.
 
-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.
+The preregistration script for SAP ASE database backup using Azure Backup ensures the system is properly configured, which includes authentication configuration, network connectivity validation, and necessary packages installation. It also supports private endpoints and prepares the database for seamless backup operations.
 
 Learn about the [supported configurations and scenarios for SAP ASE database backup](sap-ase-backup-support-matrix.md) on Azure VMs.
 
@@ -31,37 +31,35 @@ Before you run the preregistration script, ensure that the following prerequisit
 
 The preregistration script is a Python script that you run on the VM where the SAP ASE database is installed. The script performs the following tasks:
 
-1. Creates the necessary group where the **plugin users** are added.
-2. Installs and updates required packages such as waagent, Python, curl, unzip, Libicu, and PythonXML.
-3. Verifies the status of waagent, checks `wireserver` and `IMDS connectivity`, and tests **TCP connectivity** to  Microsoft Entra ID.
-4. Confirms if the geographic region is supported.
-5. Checks for available free space for logs, in the `waagent` directory, and `/opt` directory.
-6. Validates if the Adaptive Server Enterprise (ASE) version is supported.
-7. Logs in the SAP instance using the provided username and password, enabling dump history, which is necessary for backup and restore operations.
-8. Ensures that the OS version is supported.
-9. Installs and updates required Python modules such as requests and cryptography.
-10. Creates the workload configuration file.
-11. Sets up the required directories under `/opt` for backup operations.
-12. Encrypts the password and securely stores it in the virtual machine. 
+- Creates the necessary group where the **plugin users** are added.
+- Installs and updates required packages such as waagent, Python, curl, unzip, Libicu, and PythonXML.
+- Verifies the status of waagent, checks `wireserver` and `IMDS connectivity`, and tests **TCP connectivity** to  Microsoft Entra ID.
+- Confirms if the geographic region is supported.
+- Checks for available free space for logs, in the `waagent` directory, and `/opt` directory.
+- Validates if the Adaptive Server Enterprise (ASE) version is supported.
+- Logs in the SAP instance using the provided username and password, enabling dump history, which is necessary for backup and restore operations.
+- Ensures that the OS version is supported.
+- Installs and updates required Python modules such as requests and cryptography.
+- Creates the workload configuration file.
+- Sets up the required directories under `/opt` for backup operations.
+- Encrypts the password and securely stores it in the virtual machine. 
 
 ## Run the preregistration script
 
-To execute the preregistration script for SAP ASE database backup, run the following bash commands:
-
-1. [Download the ASE Preregistration Script file](https://aka.ms/preregscriptsapase).
-2. Copy the file to the virtual machine (VM).
+Before you execute the preregistration script, [download the ASE preregistration script file](https://aka.ms/preregscriptsapase) and copy it to the virtual machine (VM).
 
-  
-   >[!NOTE]
-   >Replace `<script name>` in the following commands with the name of the script file you downloaded and copied to the VM.
+>[!NOTE]
+>Replace `<script name>` in the following commands with the name of the script file you downloaded and copied to the VM.
 
-3. Convert the script to the Unix format.
+To execute the preregistration script for SAP ASE database backup, run the following bash commands:
+ 
+1. Convert the script to the Unix format.
 
    ```bash
     dos2unix <script name>
    ```
 
-4. Change the permission of the script file.
+1. Change the permission of the script file.
 
    >[!Note]
    >Before you run the following command, replace `/path/to/script/file` with the actual path of the script file in the VM.
@@ -70,13 +68,13 @@ To execute the preregistration script for SAP ASE database backup, run the follo
     sudo chmod -R 777 /path/to/script/file
    ```
 
-5. Update the script name.
+1. Update the script name.
 
    ```bash
     sudo ./<script name> -us
    ```
 
-6. Run the script.
+1. Run the script.
 
     >[!Note]
     >Before running the following command, provide the required values for the placeholders.
@@ -99,7 +97,7 @@ To execute the preregistration script for SAP ASE database backup, run the follo
     >[!NOTE]
     >To find the `<private-ip-of-vm>`, open the VM in the Azure portal and check the private IP under the **Networking** section.
 
-7. View details of the parameters.
+1. View details of the parameters.
 
    ```bash
     sudo ./<script name> -aw SAPAse --help
diff --git a/articles/backup/sap-ase-database-backup-tutorial.md b/articles/backup/sap-ase-database-backup-tutorial.md
@@ -22,7 +22,7 @@ Before you set up the SAP ASE database for backup, review the following prerequi
 - Identify or create a Recovery Services vault in the same region and subscription as the VM running SAP ASE.
 - Allow connectivity from the VM to the internet, so that it can reach Azure.
 - The combined length of the SAP ASE Server VM name and the Resource Group name must have **<= 84** characters for Azure Resource Manager (ARM) VMs (and 77 characters for classic VMs) as the service reserves some characters. 
-- VM must have python **>= 3.6.15** (recommended- Python3.10) with requests module installed. The default sudo python3 must run python 3.6.15 or higher. Validate by running python3 and **sudo python3** in your system to check the python version it runs by default. To change the default version, link python3 to python 3.6.15 or higher.
+- VM must have python **>= 3.6.15** (recommended- Python3.10) with requests module installed. The default sudo python3 must run python 3.6.15 or higher. Validate by running python3 and **sudo python3** in your system to check the python version. To change the default version, link python3 to python 3.6.15 or higher.
 - [Run the SAP ASE backup configuration script (preregistration script)](sap-ase-database-backup-run-preregistration-quickstart.md) in the virtual machine that hosts the SAP ASE database. This script gets the ASE system ready for backup.
 - Assign the following privileges and settings for the backup operation:
   
@@ -154,9 +154,9 @@ To create a custom role for Azure Backup, run the following bash commands:
 ## Establish network connectivity
 
 For all operations, an SAP ASE database running on an Azure VM requires connectivity to the Azure Backup service, Azure Storage, and Microsoft Entra ID. You can achieve this connectivity by using private endpoints or by allowing access to the required public IP addresses or Fully Qualified Domain Names
- (FQDNs). Not allowing proper connectivity to the required Azure services might lead to failure in operations like database discovery, configuring backup, performing backups, and restoring data.
+ (FQDNs). If you don't allow proper connectivity to the required Azure services, it might lead to failure in operations, such as database discovery, configuring backup, performing backups, and restoring data.
 
-The following table lists the various alternatives you can use for establishing connectivity:
+The following table lists the various alternatives you can use to establish connectivity:
 
 | Option | Advantages | Disadvantages |
 | --- | --- | --- |
@@ -179,7 +179,7 @@ Private endpoints allow you to connect securely from servers in a virtual networ
 
 ### Network Security Group tags
 
-If you use Network Security Groups (NSG), use the AzureBackup service tag to allow outbound access to Azure Backup. In addition to the Azure Backup tag, you also need to allow connectivity for authentication and data transfer by creating similar [NSG rules](/azure/virtual-network/network-security-groups-overview#service-tags) for Microsoft Entra ID and Azure Storage (Storage). 
+If you use Network Security Groups (NSG), use the AzureBackup service tag to allow outbound access to Azure Backup. In addition to the Azure Backup tag, you must allow connectivity for authentication and data transfer by creating similar [NSG rules](/azure/virtual-network/network-security-groups-overview#service-tags) for Microsoft Entra ID and Azure Storage (Storage). 
 
 To create a rule for the Azure Backup tag, follow these steps:
 
@@ -246,7 +246,7 @@ To use an HTTP proxy server to route traffic for Microsoft Entra ID, follow thes
 
 #### Use outbound rules
 
-If the **Firewall** or **NSG** setting block the `management.azure.com` domain from Azure Virtual Machine, snapshot backups fails.
+If the **Firewall** or **NSG** setting block the `management.azure.com` domain from Azure Virtual Machine, snapshot backups fail.
 
 Create the following outbound rule and allow the domain name to back up the database. Learn [how to create the outbound rules](/azure/machine-learning/how-to-access-azureml-behind-firewall).
 
@@ -264,7 +264,7 @@ In the Recovery Services vault, you can enable [Cross Region Restore](backup-azu
 
 :::image type="content" source="./media/sap-ase-database-backup/enable-cross-region-restore.png" alt-text="Screenshot shows how to enable Cross Region Restore in the Recovery Services vault. " lightbox="./media/sap-ase-database-backup/enable-cross-region-restore.png":::
 
-## Discover the databases
+## Discover the SAP ASE databases
 
 To discover the SAP ASE databases, follow these steps:
 
@@ -366,7 +366,7 @@ To configure the backup operation for the SAP ASE database, follow these steps:
 
      >[!Note]
      >- Log backups only begin to flow after a successful full backup is completed.
-     >- Each log backup is chained to the previous full backup to form a recovery chain. This full backup is retained until the retention of the last log backup has expired. This might mean that the full backup is retained for an extra period to make sure all the logs can be recovered. Let's assume a user has a weekly full backup, daily differential and 2-hour logs. All of them are retained for 30 days. But, the weekly full can be really cleaned up/deleted only after the next full backup is available, that is, after 30 + 7 days. For example, a weekly full backup happens on Nov 16th. According to the retention policy, it should be retained until Dec 16th. The last log backup for this full happens before the next scheduled full, on Nov 22nd. Until this log is available until Dec 22nd, the Nov 16th full can't be deleted. So, the Nov 16th full is retained until Dec 22nd.
+     >- Each log backup is chained to the previous full backup to form a recovery chain. This full backup is retained until the retention of the last log backup has expired. This might mean that the full backup is retained for an extra period to make sure all the logs can be recovered. Let's assume a user has a weekly full backup, daily differential and 2-hour logs. All of them are retained for 30 days. But the weekly full can be really cleaned up/deleted only after the next full backup is available, that is, after 30 + 7 days. For example, a weekly full backup happens on Nov 16th. According to the retention policy, it should be retained until Dec 16th. The last log backup for this full happens before the next scheduled full, on Nov 22nd. Until this log is available until Dec 22nd, the Nov 16th full can't be deleted. So, the Nov 16th full is retained until Dec 22nd.
 
 1. Select **OK** to save the log backup policy configuration.
 1. On the **Create Policy** pane, select **OK** to complete the backup policy creation.
diff --git a/articles/backup/sap-ase-database-backup.md b/articles/backup/sap-ase-database-backup.md
@@ -22,7 +22,7 @@ Before you set up the SAP ASE database for backup, review the following prerequi
 - Identify or create a Recovery Services vault in the same region and subscription as the VM running SAP ASE.
 - Allow connectivity from the VM to the internet, so that it can reach Azure.
 - The combined length of the SAP ASE Server VM name and the Resource Group name must have **<= 84** characters for Azure Resource Manager (ARM) VMs (and 77 characters for classic VMs) as the service reserves some characters. 
-- VM must have python **>= 3.6.15** (recommended- Python3.10) with requests module installed. The default sudo python3 must run python 3.6.15 or higher. Validate by running python3 and **sudo python3** in your system to check the python version it runs by default. To change the default version, link python3 to python 3.6.15 or higher.
+- VM must have python **>= 3.6.15** (recommended- Python3.10) with requests module installed. The default sudo python3 must run python 3.6.15 or higher. Validate by running python3 and **sudo python3** in your system to check the python version. To change the default version, link python3 to python 3.6.15 or higher.
 - [Run the SAP ASE backup configuration script (preregistration script)](sap-ase-database-backup-run-preregistration-quickstart.md) in the virtual machine that hosts the SAP ASE database. This script gets the ASE system ready for backup.
 - Assign the following privileges and settings for the backup operation:
   
@@ -47,7 +47,7 @@ Before you set up the SAP ASE database for backup, review the following prerequi
 - Use an existing Recovery Services vault, or [create a new one](backup-create-recovery-services-vault.md#create-a-recovery-services-vault).
 - [Enable Cross Region Restore](sap-ase-database-backup-tutorial.md#enable-cross-region-restore) for Recovery Services vault.
 
-## Discover the databases
+## Discover the SAP ASE databases
 
 To discover the SAP ASE databases, follow these steps:
 
diff --git a/articles/backup/sap-ase-database-restore.md b/articles/backup/sap-ase-database-restore.md
@@ -158,15 +158,15 @@ The secondary region restore user experience is similar to the primary region re
 Learn about the [minimum role requirements for cross-region restore](/azure/backup/backup-rbac-rs-vault#minimum-role-requirements-for-azure-workload-backups-sql-and-hana-db-backups).
 
 
-## Restore to a Private Endpoint enabled vault in a different subscription
+## Restore to a private endpoint enabled vault in a different subscription
 
 Before you do Cross Subscription Restore (CSR), ensure that the Recovery Services vault has the necessary [Azure role-based access control (Azure RBAC) permissions](backup-rbac-rs-vault.md#minimum-role-requirements-for-sap-ase-sybase-database--cross-subscription-restore).
 
-To trigger Cross Subscription Restore to a Private Endpoint enabled vault, follow these steps:
+To trigger Cross Subscription Restore to a private endpoint enabled vault, follow these steps:
 
-1. In the Azure portal, go to the source **Recovery Services vault** , and then [create Private Endpoints](private-endpoints.md#create-private-endpoints-for-azure-backup).
+1. In the [Azure portal](https://portal.azure.com/), go to the source **Recovery Services vault** , and then [create Private Endpoints](private-endpoints.md#create-private-endpoints-for-azure-backup).
 
-   During Private Endpoint creation, ensure that you enter the following details:
+   During private endpoint creation, ensure that you enter the following details:
 
    - 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.
