Merge pull request #81037 from pvrk/June2019

ShannonLeavitt · web-flow · commit 358cdd98a58b · 2019-07-01T07:11:54.000-04:00
Created TShoot guide for HANA backups
diff --git a/articles/backup/backup-azure-sap-hana-database-troubleshoot.md b/articles/backup/backup-azure-sap-hana-database-troubleshoot.md
@@ -0,0 +1,68 @@
+---
+title: Troubleshooting errors while backing up SAP HANA databases using Azure Backup | Microsoft Docs
+description: This guide explains how to troubleshoot common errors while trying to backup SAP HANA databases using Azure Backup.
+services: backup
+author: pvrk
+manager: vijayts
+ms.service: backup
+ms.topic: conceptual
+ms.date: 06/28/2019
+ms.author: pullabhk
+---
+
+# Troubleshoot back up of SAP HANA Server on Azure
+
+This article provides troubleshooting information for protecting SAP HANA databases on Azure Virtual Machines. Before proceeding to troubleshooting, let's understand few key points about permissions and settings.
+
+## Understanding pre-requisites
+
+As part of [pre-requisites](backup-azure-sap-hana-database.md#prerequisites), the pre-registration script should be run on the virtual machine where HANA is installed to set up the right permissions.
+
+### Setting up permissions
+
+What does the pre-registration script do:
+
+1. Creates of AZUREWLBACKUPHANAUSER in HANA System and adds required Roles and Permissions as listed below
+    - DATABASE ADMIN  - To create new DBs during restore
+    - CATALOG READ – To read the backup catalog
+    - SAP_INTERNAL_HANA_SUPPORT – To access few private tables
+2. Adding key to Hdbuserstore for HANA plugin to do all operations (inquiry of database, configuring backup, doing backup, doing restore)
+    - If you run the HDBSQL command within the HANA machine,
+
+    ``` hdbsql 
+    ‘hdbuserstore list’
+    ```
+
+    it should display the key {SID}{DBNAME} with the user as ‘AZUREWLBACKUPHANAUSER’
+
+> [!NOTE]
+> Make sure you have a unique set of SSFS files under the path “/usr/sap/<SID>/home/.hdb/”. There should be only one folder under this path.
+
+### Setting up BackInt parameters
+
+Once a database is chosen for backup, the Azure Backup service will configure backInt parameters at DATABASE level.
+
+- [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]
+> Make sure these parameters are NOT present at HOST level. Host level parameters will override these parameters and may cause different behavior than expected.
+
+'Stop protection with retain data' and then 'resume backup' once more will reset the parameters to the right values.
+
+## Understanding common user errors
+
+### UserErrorInOpeningHanaOdbcConnection
+
+| Error message | Possible causes | Recommended action |
+|---|---|---|
+| Failed to connect to HANA system.check your system is up and running.| Azure Backup service is not able to connect to HANA because HANA DB is down. Or HANA is running but not allowing Azure Backup service to connect | Check if the HANA DB/service is down. If HANA DB/service is up and running, check if all permissions are set up as mentioned [here](#setting-up-permissions). If the key is missing, rerun the pre-registration script to create a new key. |
+
+### UserErrorInvalidBackintConfiguration
+
+| Error message | Possible causes | Recommended action |
+|---|---|---|
+| Detected Invalid Backint Configuration. Stop protection and reconfigure the database.| The backInt parameters are incorrectly specified for Azure Backup. | Check the parameters are as mentioned [here](#setting-up-backint-parameters). If backInt based parameters are present in HOST, then remove them. If parameters are not present at HOST but have been manually modified at a database level, then revert them to the appropriate values as mentioned above. Or 'stop protection with retain data' from Azure portal and 'resume backup' once again.|
diff --git a/articles/backup/backup-azure-sap-hana-database.md b/articles/backup/backup-azure-sap-hana-database.md
@@ -18,15 +18,13 @@ ms.author: raynew
 > [!NOTE]
 > This feature is currently in public preview. It's not currently production ready, and doesn't have a guaranteed SLA. 
 
-
 ## Scenario support
 
 **Support** | **Details**
 --- | ---
 **Supported geos** | Australia South East, East Australia <br> Brazil South <br> Canada Central, Canada East <br> South East Asia, East Asia <br> East US, East US 2, West Central US, West US, West US 2, North Central US, Central US, South Central US<br> India Central, India South <br> Japan East, Japan West<br> Korea Central, Korea South <br> North Europe, West Europe <br> UK South, UK West
 **Supported VM operating systems** | SLES 12 with SP2 or SP3.
-**Supported HANA versions** | SSDC on HANA 1.x, MDC on HANA 2.x <= SPS03
-
+**Supported HANA versions** | SDC on HANA 1.x, MDC on HANA 2.x <= SPS03
 
 ### Current limitations
 
@@ -35,12 +33,9 @@ ms.author: raynew
 - You can only back up databases in Scale-Up mode.
 - You can back up database logs every 15 minutes. Log backups only begin to flow after a successful full backup for the database has completed.
 - You can take full and differential backups. Incremental backup isn't currently supported.
-- You can't modify the backup policy after you apply it for SAP HANA backups. If you want to back up with different settings, create a new policy, or assign a different policy. 
-    - To create a new policy, in the vault click **Policies** > **Backup Policies** > **+Add** > **SAP HANA in Azure VM**, and specify policy settings.
-    - To assign a different policy, in the properties of the VM running the database, click the current policy name. Then on the **Backup Policy** page you can select a different policy to use for the backup.
-
-
-
+- You can't modify the backup policy after you apply it for SAP HANA backups. If you want to back up with different settings, create a new policy, or assign a different policy.
+  - To create a new policy, in the vault click **Policies** > **Backup Policies** > **+Add** > **SAP HANA in Azure VM**, and specify policy settings.
+  - To assign a different policy, in the properties of the VM running the database, click the current policy name. Then on the **Backup Policy** page you can select a different policy to use for the backup.
 
 ## Prerequisites
 
@@ -53,14 +48,16 @@ Make sure you do the following before you configure backups:
 
         ![Package installation option](./media/backup-azure-sap-hana-database/hana-package.png)
 
-2.	On the VM, install and enable ODBC driver packages from the official SLES package/media using zypper, as follows:
+2. On the VM, install and enable ODBC driver packages from the official SLES package/media using zypper, as follows:
 
-    ``` 
+    ```unix
     sudo zypper update
     sudo zypper install unixODBC
     ```
-4.	Allow connectivity from the VM to the internet, so that it can reach Azure, as described in procedure below.
 
+3. Allow connectivity from the VM to the internet, so that it can reach Azure, as described in procedure [below](#set-up-network-connectivity).
+
+4. Run the pre-registration script in the virtual machine where HANA is installed as a root user. The script is provided [in the portal](#discover-the-databases) in the flow and is required to set up the [right permissions](backup-azure-sap-hana-database-troubleshoot.md#setting-up-permissions).
 
 ### Set up network connectivity
 
@@ -76,7 +73,7 @@ Onboard to the public preview as follows:
 - In the portal, register your subscription ID to the Recovery Services service provider by [following this article](https://docs.microsoft.com/azure/azure-resource-manager/resource-manager-register-provider-errors#solution-3---azure-portal). 
 - For PowerShell, run this cmdlet. It should complete as "Registered".
 
-    ```
+    ```powershell
     PS C:>  Register-AzProviderFeature -FeatureName "HanaBackup" –ProviderNamespace Microsoft.RecoveryServices
     ```
 
@@ -86,7 +83,6 @@ Onboard to the public preview as follows:
 
 ## Discover the databases
 
-
 1. In the vault, in **Getting Started**, click **Backup**. In **Where is your workload running?**, select **SAP HANA in Azure VM**.
 2. Click **Start Discovery**. This initiates discovery of unprotected Linux VMs in the vault region.
 
@@ -100,7 +96,7 @@ Onboard to the public preview as follows:
 6. Azure Backup discovers all SAP HANA databases on the VM. During discovery, Azure Backup registers the VM with the vault, and installs an extension on the VM. No agent is installed on the database.
 
     ![Discover SAP HANA databases](./media/backup-azure-sap-hana-database/hana-discover.png)
-    
+
 ## Configure backup  
 
 Now enable backup.
@@ -112,6 +108,7 @@ Now enable backup.
 5. Track the backup configuration progress in the **Notifications** area of the portal.
 
 ### Create a backup policy
+
 A backup policy defines when backups are taken, and how long they're retained.
 
 - A policy is created at the vault level.
@@ -185,6 +182,5 @@ If you want to take a local backup (using HANA Studio) of a database that's bein
 
 ## Next steps
 
+[Learn about](backup-azure-sap-hana-database-troubleshoot.md) how to troubleshoot common errors while using SAP HANA backup in Azure VMs.
 [Learn about](backup-azure-arm-vms-prepare.md) backing up Azure VMs.
-
-
diff --git a/articles/backup/toc.yml b/articles/backup/toc.yml
@@ -252,6 +252,8 @@
       href: troubleshoot-azure-files.md
     - name: SQL Server
       href: backup-sql-server-azure-troubleshoot.md
+    - name: SAP HANA backup in Azure VMs
+      href: backup-azure-sap-hana-database-troubleshoot.md
     - name: System State
       href: backup-azure-system-state-troubleshoot.md
   - name: Monitor Azure Backup workloads
