Merge pull request #95167 from dcurwin/saphana-nov2019

New SAP HANA documentation

Author: PMEds28

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

@@ -2,50 +2,29 @@
 title: Troubleshoot SAP HANA databases backup errors
 description: Describes how to troubleshoot common errors that might occur when you use Azure Backup to back up SAP HANA databases.
 ms.topic: conceptual
-ms.date: 08/03/2019
+ms.date: 11/7/2019
 ---
 
 # Troubleshoot backup of SAP HANA databases on Azure
 
-This article provides troubleshooting information for backing up SAP HANA databases on Azure virtual machines. The following section covers important conceptual data required to diagnose common error in SAP HANA backup.
+This article provides troubleshooting information for backing up SAP HANA databases on Azure virtual machines. For more information on the SAP HANA backup scenarios we currently support, see [Scenario support](sap-hana-backup-support-matrix.md#scenario-support).
 
-## Prerequisites
+## Prerequisites and Permissions
 
-As part of the [prerequisites](backup-azure-sap-hana-database.md#prerequisites), make sure the preregistration script has been run on the virtual machine where HANA is installed.
+Refer to the [prerequisites](tutorial-backup-sap-hana-db.md#prerequisites) and [setting up permissions](tutorial-backup-sap-hana-db.md#setting-up-permissions) sections before configuring backups.
 
-### Setting up permissions
-
-What the preregistration script does:
-
-1. Creates AZUREWLBACKUPHANAUSER in the HANA system and adds these required roles and permissions:
-    - DATABASE ADMIN: to create new DBs during restore.
-    - CATALOG READ: to read the backup catalog.
-    - SAP_INTERNAL_HANA_SUPPORT: to access a few private tables.
-2. Adds a key to Hdbuserstore for the HANA 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:
-
-    ``` hdbsql
-    hdbuserstore list
-    ```
-
-    The command output should display the {SID}{DBNAME} key, with the user shown as AZUREWLBACKUPHANAUSER.
-
-> [!NOTE]
-> Make sure you have a unique set of SSFS files under **/usr/sap/{SID}/home/.hdb/**. There should be only one folder in this path.
-
-### Setting up BackInt parameters
-
-After a database is chosen for backup, the Azure Backup service  configures 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]
+## Common user errors
 
-> [!NOTE]
-> Make sure these parameters are *not* present at HOST level. Host-level parameters will override these parameters and might cause unexpected behavior.
+| Error                                | Error message                    | Possible causes                                              | Recommended action                                           |
+| ------------------------------------ | -------------------------------- | ------------------------------------------------------------ | ------------------------------------------------------------ |
+| UserErrorInOpeningHanaOdbcConnection | Failed to connect to HANA system | The SAP HANA instance may be down. <br> The required permissions for Azure backup to interact with the HANA  database aren't set. | Check if the SAP HANA database is  up. If the database is up and running, check if all the required permissions are set. If any of the permissions are missing run the [preregistration script](https://aka.ms/scriptforpermsonhana) to add the missing permissions. |
+| UserErrorHanaInstanceNameInvalid | The specified SAP HANA instance is either invalid or can't be found | Multiple SAP HANA instances on a single  Azure VM can't be backed up. | Run the [preregistration script](https://aka.ms/scriptforpermsonhana) on the SAP HANA instance you  want to back up. If the issue still persists, contact Microsoft support. |
+| UserErrorHanaUnsupportedOperation | The specified SAP HANA operation isn't supported | Azure backup for SAP HANA doesn't support incremental backup and actions performed on SAP HANA native clients  (Studio/ Cockpit/ DBA Cockpit) | For more information, refer [here](sap-hana-backup-support-matrix.md#scenario-support). |
+| UserErrorHANAPODoesNotSupportBackupType | This SAP HANA database doesn't support the requested backup  type | Azure backup doesn't support  incremental backup and backup using snapshots | For more information, refer [here](sap-hana-backup-support-matrix.md#scenario-support). |
+| UserErrorHANALSNValidationFailure | Backup log chain is broken | The log backup destination may have  been updated from backint to file system or the backint executable may have  been changed | Trigger a full backup to resolve the  issue |
+| UserErrorIncomaptibleSrcTargetSystsemsForRestore | The source and target systems for restore are incompatible | The target system for restore is  incompatible with the source | Refer to the SAP Note [1642148](https://launchpad.support.sap.com/#/notes/1642148) to learn  about the restore types supported today |
+| UserErrorSDCtoMDCUpgradeDetected | SDC to MDC upgrade detected | The SAP HANA instance has been upgraded  from SDC to MDC. Backups will fail after the update. | Follow the steps listed in the [Upgrading from SAP HANA 1.0 to 2.0 section](#upgrading-from-sap-hana-10-to-20) to resolve the issue |
+| UserErrorInvalidBackintConfiguration | Detected invalid backint configuration | The backing parameters are incorrectly  specified for Azure backup | Check if the following (backint) parameters are set: <br> * [catalog_backup_using_backint:true] <br>  * [enable_accumulated_catalog_backup:false] <br> * [parallel_data_backup_backint_channels:1] <br>* [log_backup_timeout_s:900)] <br> * [backint_response_timeout:7200] <br> If backint-based parameters are present in HOST, remove  them. If parameters aren't present at HOST level but have been manually  modified at a database level, revert them to the appropriate values as  described earlier. Or, run  [stop protection and retain backup data](sap-hana-db-manage.md#stop-protection-for-an-sap-hana-database) from the Azure portal, and then select **Resume backup**. |
 
 ## Restore checks
 
@@ -60,24 +39,33 @@ Assume an SDC HANA instance "H21" is backed up. The backup items page will show
 Note the following points:
 
 - By default, the restored db name will be populated with the backup item name i.e., h21(sdc)
-- Selecting the target as H11 will NOT change the restored db name automatically. **It should be edited to h11(sdc)**. In case of SDC, the restored db name will be the target instance ID with lowercase letters and 'sdc' appended in brackets.
+- Selecting the target as H11 will NOT change the restored db name automatically. **It should be edited to h11(sdc)**. Regarding SDC, the restored db name will be the target instance ID with lowercase letters and 'sdc' appended in brackets.
 - Since SDC can have only single database, you also need to click the checkbox to allow override of the existing database data with the recovery point data.
-- Linux is case-sensitive and therefore make sure to preserve the case.
+- Linux is case-sensitive. Therefore, be careful to preserve the case.
 
 ### Multiple Container Database (MDC) restore
 
-In multiple container databases for HANA, the standard configuration is SYSTEMDB + 1 or more Tenant DBs. Restoring an entire SAP HANA instance means to restore both SYSTEMDB and Tenant DBs. One restores SYSTEMDB first and then proceeds for Tenant DB. System DB essentially means to override the system information on the selected target. This also overrides the BackInt related information in the target instance. Therefore, after the system DB is restored to a target instance, one needs to run the pre-registration script again. Only then the subsequent tenant DB restores will succeed.
+In multiple container databases for HANA, the standard configuration is SYSTEMDB + 1 or more Tenant DBs. Restoring an entire SAP HANA instance means to restore both SYSTEMDB and Tenant DBs. One restores SYSTEMDB first and then proceeds for Tenant DB. System DB essentially means to override the system information on the selected target. This restore also overrides the BackInt related information in the target instance. Therefore, after the system DB is restored to a target instance, one needs to run the pre-registration script again. Only then the subsequent tenant DB restores will succeed.
 
-## Common user errors
+## Upgrading from SAP HANA 1.0 to 2.0
+
+If you're protecting SAP HANA 1.0 databases and wish to upgrade to 2.0, then perform the steps outlined below:
+
+- [Stop protection](sap-hana-db-manage.md#stop-protection-for-an-sap-hana-database) with retain data for old SDC database.
+- Rerun [pre-registration script](https://aka.ms/scriptforpermsonhana) with correct details of (sid and mdc).
+- Re-register extension (Backup -> view details -> Select the relevant Azure VM -> Re-register).
+- Click Rediscover DBs for the same VM. This action should show the new DBs in step 2 with correct details (SYSTEMDB and Tenant DB, not SDC).
+- Protect these new databases.
+
+## Upgrading without an SID change
 
-### UserErrorInOpeningHanaOdbcConnection
+Upgrades to OS or SAP HANA that don't cause a SID change can be handled as outlined below:
 
-data| Error message | Possible causes | Recommended action |
-|---|---|---|
-| Failed to connect to HANA system. Verify that your system is up and running.| The Azure Backup service can't connect to HANA because the HANA database is down. Or HANA is running but not allowing the Azure Backup service to connect. | Check whether the HANA database or service is down. If the HANA database or service is up and running, check whether [all permissions are set](#setting-up-permissions). If the key is missing, rerun the preregistration script to create a new key. |
+- [Stop protection](sap-hana-db-manage.md#stop-protection-for-an-sap-hana-database) with retain data for the database
+- Rerun the [pre-registration script](https://aka.ms/scriptforpermsonhana)
+- [Resume protection](sap-hana-db-manage.md#resume-protection-for-an-sap-hana-database) for the database again
 
-### UserErrorInvalidBackintConfiguration
+## Next steps
 
-| 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 whether [the parameters are set](#setting-up-backint-parameters). If backInt-based parameters are present in HOST, remove them. If parameters are not present at HOST level but have been manually modified at a database level, revert them to the appropriate values as described earlier. Or, run **Stop protection and retain backup data** from the Azure portal, and then select **Resume backup**.|
+- 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]