Merge pull request #287680 from AbhishekMallick-MS/Oct-1-2024-EEE3

Addressed EEE doc ask #16739841

Author: prmerger-automator[bot]

articles/backup/sap-hana-database-with-hana-system-replication-backup.md

@@ -2,7 +2,7 @@
 title: Back up SAP HANA System Replication databases on Azure VMs using Azure Backup
 description: In this article, discover how to back up SAP HANA databases with HANA System Replication enabled.
 ms.topic: how-to
-ms.date: 09/30/2024
+ms.date: 10/01/2024
 ms.service: azure-backup
 author: AbhishekMallick-MS
 ms.author: v-abhmallick
@@ -47,8 +47,25 @@ When a failover occurs, the users are replicated to the new primary, but *hdbuse
    | SDC | Backup Admin | Reads the backup catalog. |
    | SAP_INTERNAL_HANA_SUPPORT |      | Accesses a few private tables. <br><br> Required only for single container database (SDC) and multiple container database (MDC) versions earlier than HANA 2.0 SPS04 Rev 46. It isn't required for HANA 2.0 SPS04 Rev 46 versions and later, because we receive the required information from public tables now after the fix from HANA team. |
 
+   **Example**:
+
+   ```HDBSQL
+   - hdbsql -t -U SYSTEMKEY CREATE USER USRBKP PASSWORD AzureBackup01 NO FORCE_FIRST_PASSWORD_CHANGE
+   - hdbsql -t -U SYSTEMKEY 'ALTER USER USRBKP DISABLE PASSWORD LIFETIME'
+   - hdbsql -t -U SYSTEMKEY 'ALTER USER USRBKP RESET CONNECT ATTEMPTS'
+   - hdbsql -t -U SYSTEMKEY 'ALTER USER USRBKP ACTIVATE USER NOW'
+   - hdbsql -t -U SYSTEMKEY 'GRANT DATABASE ADMIN TO USRBKP'
+   - hdbsql -t -U SYSTEMKEY 'GRANT CATALOG READ TO USRBKP'
+   ```
+
 1. Add the key to *hdbuserstore* for your custom backup user that enables the HANA backup plug-in to manage all operations (database queries, restore operations, configuring, and running backup). 
 
+   **Example**:
+
+   ```HDBSQL
+   - hdbuserstore set BKPKEY localhost:39013 USRBKP AzureBackup01
+   ```
+
 1. Pass the custom backup user key to the script as a parameter: 
 
    ```HDBSQL
@@ -83,13 +100,26 @@ When a failover occurs, the users are replicated to the new primary, but *hdbuse
 
    You must provide the same HSR ID on both VMs/nodes. This ID must be unique within a vault. It should be an alphanumeric value containing at least one digit, one lowercase letter, and one uppercase character, and it should contain from 6 to 35 characters.
 
+   **Example**:
+
+   ```HDBSQL
+   - ./script.sh -sk SYSTEMKEY -bk USRBKP -hn HSRlab001 -p 39013
+   ```
+
 1. While you're running the preregistration script on the secondary node, you must specify the SDC/MDC port as input. This is because SQL commands to identify the SDC/MDC setup can't be run on the secondary node. You must provide the port number as a parameter, as shown here: 
 
    `-p PORT_NUMBER` or `–port_number PORT_NUMBER`.
 
    - For MDC, use the format `3<instancenumber>13`.
    - For SDC, use the format `3<instancenumber>15`.
 
+   **Example**:
+
+   ```HDBSQL
+   - MDC: ./script.sh -sk SYSTEMKEY -bk USRBKP -hn HSRlab001 -p 39013
+   - SDC: ./script.sh -sk SYSTEMKEY -bk USRBKP -hn HSRlab001 -p 39015
+   ```
+
 1. If your HANA setup uses private endpoints, run the preregistration script with the `-sn` or `--skip-network-checks` parameter. Ater the preregistration script has run successfully, proceed to the next steps.
 
 1. Run the SAP HANA backup configuration script (preregistration script) in the VMs where HANA is installed as the root user. This script sets up the HANA system for backup. For more information about the script actions, see the [What the preregistration script does](tutorial-backup-sap-hana-db.md#what-the-pre-registration-script-does) section.