Merge pull request #107492 from dcurwin/saphana-march12-2020

changes to saphana docs

Author: ttorble

articles/backup/backup-azure-sap-hana-database-troubleshoot.md

@@ -119,7 +119,26 @@ Upgrades to OS or SAP HANA that don't cause a SID change can be handled as outli
 - Rerun the [pre-registration script](https://aka.ms/scriptforpermsonhana). Usually, we have seen upgrade process removes the necessary roles. Running the pre-registration script will help verify all the required roles.
 - [Resume protection](sap-hana-db-manage.md#resume-protection-for-an-sap-hana-database) for the database again
 
+## Re-registration failures
+
+Check for one or more of the following symptoms before you trigger the re-register operation:
+
+- All operations (such as backup, restore, and configure backup) are failing on the VM with one of the following error codes: **WorkloadExtensionNotReachable, UserErrorWorkloadExtensionNotInstalled, WorkloadExtensionNotPresent, WorkloadExtensionDidntDequeueMsg**.
+- If the **Backup Status** area for the backup item is showing **Not reachable**, rule out all the other causes that might result in the same status:
+
+  - Lack of permission to perform backup-related operations on the VM
+  - The VM is shutdown, so backups cannot take place
+  - Network issues
+
+These symptoms may arise for one or more of the following reasons:
+
+- An extension was deleted or uninstalled from the portal.
+- The VM was restored back in time through in-place disk restore.
+- The VM was shut down for an extended period, so the extension configuration on it expired.
+- The VM was deleted, and another VM was created with the same name and in the same resource group as the deleted VM.
+
+In the preceding scenarios, we recommend that you trigger a re-register operation on the VM.
+
 ## Next steps
 
-- Review the [frequently asked questions](https://docs.microsoft.com/azure/backup/sap-hana-faq-backup-azure-vm)
- about backing up SAP HANA databases on Azure VMs]
+- Review the [frequently asked questions](https://docs.microsoft.com/azure/backup/sap-hana-faq-backup-azure-vm) about backing up SAP HANA databases on Azure VMs.

articles/backup/media/sap-hana-db-manage/choose-frequency.png

@@ -52,7 +52,7 @@ ToTo learn more about monitoring, go to [Monitoring in the Azure portal](https:/
 
 Azure Backup makes management of a backed-up SAP HANA database easy with an abundance of management operations that it supports. These operations are discussed in more detail in the following sections.
 
-### Run an ad-hoc backup
+### Run an on-demand backup
 
 Backups run in accordance with the policy schedule. You can run a backup on-demand as follows:
 
@@ -61,6 +61,16 @@ Backups run in accordance with the policy schedule. You can run a backup on-dema
 3. In **Backup Now**, use the calendar control to select the last day that the recovery point should be retained. Then click **OK**.
 4. Monitor the portal notifications. You can monitor the job progress in the vault dashboard > **Backup Jobs** > **In progress**. Depending on the size of your database, creating the initial backup may take a while.
 
+### HANA native client integration
+
+Now on-demand full backups triggered from any of the HANA native clients will show up as a full backup on the **Backup Items** page.
+
+![Last backups run](./media/sap-hana-db-manage/last-backups.png)
+
+These ad-hoc full backups will also show up in the list of restore points for restore.
+
+![List of restore points](./media/sap-hana-db-manage/list-restore-points.png)
+
 ### Run SAP HANA native client backup 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:
@@ -108,6 +118,37 @@ You can change the underlying policy for an SAP HANA backup item.
 >
 > Incremental backup policies cannot be used for SAP HANA databases. Incremental backup is not currently supported for these databases.
 
+### Modify Policy
+
+Modify policy to change backup types, frequencies and retention range.
+
+>[!NOTE]
+>Any change in the retention period will be applied retroactively to all the older recovery points, in addition to the new ones.
+
+1. In the vault dashboard, go to **Manage > Backup Policies** and choose the policy you want to edit.
+
+   ![Choose the policy to edit](./media/sap-hana-db-manage/manage-backup-policies.png)
+
+1. Select **Modify**.
+
+   ![Select Modify](./media/sap-hana-db-manage/modify-policy.png)
+
+1. Choose the frequency for the backup types.
+
+   ![Choose backup frequency](./media/sap-hana-db-manage/choose-frequency.png)
+
+Policy modification will impact all the associated backup items and trigger corresponding **configure protection** jobs.
+
+### Inconsistent policy
+
+Occasionally a modify policy operation can lead to an **inconsistent** policy version for some backup items. This happens when the corresponding **configure protection** job fails for the backup item after a modify policy operation is triggered. It appears as follows in the backup item view:
+
+![Inconsistent policy](./media/sap-hana-db-manage/inconsistent-policy.png)
+
+You can fix the policy version for all the impacted items in one click:
+
+![Fix policy version](./media/sap-hana-db-manage/fix-policy-version.png)
+
 ### Stop protection for an SAP HANA database
 
 You can stop protecting an SAP HANA database in a couple of ways:
@@ -162,7 +203,7 @@ Learn how to continue backup for an SAP HANA database [after upgrading from SAP
 
 Learn how to continue backup of an SAP HANA database whose [SID has not changed after upgrade](backup-azure-sap-hana-database-troubleshoot.md#upgrading-without-an-sid-change).
 
-### Unregister an SAP HANA database
+### Unregister an SAP HANA instance
 
 Unregister an SAP HANA instance after you disable protection but before you delete the vault:
 
@@ -180,6 +221,12 @@ Unregister an SAP HANA instance after you disable protection but before you dele
 
    ![Select unregister](./media/sap-hana-db-manage/unregister.png)
 
+### Re-register extension on the SAP HANA server VM
+
+Sometimes the workload extension on the VM may get impacted for one reason or another. In such cases, all the operations triggered on the VM will begin to fail. You may then need to re-register the extension on the VM. Re-register operation reinstalls the workload backup extension on the VM for operations to continue.
+
+Use this option with caution: when triggered on a VM with an already healthy extension, this operation will cause the extension to get restarted. This may cause all the in-progress jobs to fail. Check for one or more of the [symptoms](backup-azure-sap-hana-database-troubleshoot.md#re-registration-failures) before triggering the re-register operation.
+
 ## Next steps
 
 * Learn how to [troubleshoot common issues when backing up SAP HANA databases.](https://docs.microsoft.com/azure/backup/backup-azure-sap-hana-database-troubleshoot)

articles/backup/media/sap-hana-db-manage/fix-policy-version.png

@@ -93,10 +93,10 @@ Running the pre-registration script performs the following functions:
 * It performs outbound network connectivity checks with Azure Backup servers and dependent services like Azure Active Directory and Azure Storage.
 * It logs into your HANA system using the user key listed as part of the [prerequisites](#prerequisites). The user key is used to create a backup user (AZUREWLBACKUPHANAUSER) in the HANA system and the user key can be deleted after the pre-registration script runs successfully.
 * AZUREWLBACKUPHANAUSER is assigned these required roles and permissions:
-  * DATABASE ADMIN: to create new databases during restore.
+  * DATABASE ADMIN (in case of MDC) and BACKUP ADMIN (in case of SDC): to create new databases during restore.
   * CATALOG READ: to read the backup catalog.
   * SAP_INTERNAL_HANA_SUPPORT: to access a few private tables.
-* The script adds a key to **hdbuserstore** for AZUREWLBACKUPHANAUSER for the HANA plug-in to handle all operations (database queries, restore operations, configuring and running backup).
+* The script adds a key to **hdbuserstore** for AZUREWLBACKUPHANAUSER for the HANA backup plug-in to handle all operations (database queries, restore operations, configuring and running backup).
 
 To confirm the key creation, run the HDBSQL command on the HANA machine with SIDADM credentials: