Merge pull request #187840 from v-amallick/Feb-8-2022-HANA

HANA - Documentation updates

Author: PRMerger6

articles/backup/sap-hana-db-manage.md

@@ -2,7 +2,7 @@
 title: Manage backed up SAP HANA databases on Azure VMs
 description: In this article, learn common tasks for managing and monitoring SAP HANA databases that are running on Azure virtual machines.
 ms.topic: conceptual
-ms.date: 11/02/2021
+ms.date: 02/09/2022
 author: v-amallick
 ms.service: backup
 ms.author: v-amallick
@@ -88,41 +88,7 @@ Restores triggered from HANA native clients to restore to another machine are no
 #### Delete
 
 Delete operation from HANA native is **NOT** supported by Azure Backup since the backup policy determines the lifecycle of backups in Azure Recovery services vault.
-
-### Run SAP HANA native client backup to local disk on a database with Azure Backup enabled
-
-If you want to take a local backup (using HANA Studio / Cockpit) of a database that's being backed up with Azure Backup, do the following:
-
-1. Wait for any full or log backups for the database to finish. Check the status in SAP HANA Studio/ Cockpit.
-2. For the relevant database:
-    1. Unset the backint parameters. To do this, double-click **systemdb** > **Configuration** > **Select Database** > **Filter (Log)**.
-        * enable_auto_log_backup: No
-        * log_backup_using_backint: False
-        * catalog_backup_using_backint:False
-3. Take an on-demand full backup of the database
-4. Then reverse the steps. For the same relevant DB mentioned above,
-    1. Re-enable the backint parameters:
-        1. catalog_backup_using_backint:True
-        1. log_backup_using_backint: True
-        1. enable_auto_log_backup: Yes
-
-### Manage or clean-up the HANA catalog for a database with Azure Backup enabled
-
-If you want to edit or clean up the backup catalog, do the following:
-
-1. Wait for any full or log backups for the database to finish. Check the status in SAP HANA Studio/ Cockpit.
-2. For the relevant database:
-    1. Unset the backint parameters. To do this, double-click **systemdb** > **Configuration** > **Select Database** > **Filter (Log)**.
-        * enable_auto_log_backup: No
-        * log_backup_using_backint: False
-        * catalog_backup_using_backint:False
-3. Edit the catalog and remove the older entries
-4. Then reverse the steps. For the same relevant DB mentioned above,
-    1. Re-enable the backint parameters
-        1. catalog_backup_using_backint:True
-        1. log_backup_using_backint: True
-        1. enable_auto_log_backup: Yes
-
+.
 ### Change policy
 
 You can change the underlying policy for an SAP HANA backup item.

articles/backup/sap-hana-faq-backup-azure-vm.yml

@@ -4,7 +4,7 @@ metadata:
   description: This article provides answers to common questions about backing up SAP HANA databases using the Azure Backup service.
   ms.topic: article
   ms.service: backup
-  ms.date: 02/02/2022
+  ms.date: 02/08/2022
   author: v-amallick
   ms.author: v-amallick
 
@@ -115,22 +115,34 @@ sections:
           Currently we don't have the capability to set up the solution against a virtual IP or Proxy. We need a virtual machine to execute the solution.
 
       - question: |
-          How can I move an on-demand backup to the local file system instead of the Azure vault?
+          How can I move on-demand backups (triggered from HANA native clients) to the local file system instead of the Azure vault?
         answer: |
           1. Wait for the currently running backup to complete on the desired database (check from studio for completion).
-          1. Disable log backups and set the catalog backup to **Filesystem** for the desired DB using the following steps:
+          1. Disable log backups and set the catalog backup to **Filesystem** for the desired database using the following steps:
           1. Double-click **SYSTEMDB** -> **configuration** -> **Select Database** -> **Filter (log)**
               1. Set enable_auto_log_backup to **no**.
               1. Set catalog_backup_using_backint to **false**.
           1. Take an on-demand backup (full / differential/ incremental) on the desired database, and wait for the backup and catalog backup to complete.
-          1. If you want to also move the log backups to the Filesystem, set enable_auto_log_backup to **yes**.
+          1. If you want to also move the log backups to the Filesystem, set enable_auto_log_backup to **yes** and log_backup_using_backint to **false**.
           1. Revert to the previous settings to allow backups to flow to the Azure vault:
               1. Set enable_auto_log_backup to **yes**.
               1. Set catalog_backup_using_backint to **true**.
+              1. Set log_backup_using_backint to **true**, if it's set to **false**.
           
           > [!NOTE]
           > Moving backups to the local Filesystem and switching back again to the Azure vault may cause a log chain break of the log backups in the vault. This will trigger a full backup, which once successfully completed will start backing up the logs.
-          
+
+      - question: |
+          How can I manage or clean-up the HANA catalog for database with Azure Backup enabled?
+        answer: |
+          - SAP recommends the catalog retention should be determined by your business need (retention policy). The most common is _30 days_ retention.
+          - You can trigger clean-up/pruning of HANA catalog through HANA native clients (such as cockpit or studio) or through SQL commands.
+          - This clean-up task generates a catalog backup that's not moved to the Azure Backup vault (as there is no associated data backup).
+          - The catalog backup is therefore shown as a failure in the Cockpit/Studio. However, note that this catalog backup failure doesn't mean  the catalog clean-up activity has failed.
+          - Note that this **catalog backup failure also doesn't affect your point-in-time recoverability**.
+          - The catalog clean-up activity may cause the log backups triggered at the same time to be queued. These logs are then moved to the vault after the catalog backup (triggered by catalog clean-up) fails.
+          - Manually check the success of the catalog clean-up activity.
+
       - question: |
           How can I use SAP HANA Backup with my HANA Replication set-up?
         answer: |