Skip to content

Commit 2da64c7

Browse files
authored
Merge pull request #104847 from dcurwin/saphana-feb2020
SAP HANA documentation updates
2 parents 16d070c + 022f5bd commit 2da64c7

5 files changed

+47
-85
lines changed

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

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,10 +11,17 @@ This article provides troubleshooting information for backing up SAP HANA databa
1111

1212
## Prerequisites and Permissions
1313

14-
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.
14+
Refer to the [prerequisites](tutorial-backup-sap-hana-db.md#prerequisites) and [What the pre-registration script does](tutorial-backup-sap-hana-db.md#what-the-pre-registration-script-does) sections before configuring backups.
1515

1616
## Common user errors
1717

18+
### UserErrorHANAInternalRoleNotPresent
19+
20+
| **Error Message** | <span style="font-weight:normal">Azure backup does not have required role privileges to carry out backup</span> |
21+
| ---------------------- | ------------------------------------------------------------ |
22+
| **Possible causes** | The role may have been overwritten. |
23+
| **Recommended action** | To resolve the issue, run the script from the **Discover DB** pane, or download it [here](https://aka.ms/scriptforpermsonhana). Alternatively, add the 'SAP_INTERNAL_HANA_SUPPORT' role to the Workload Backup User (AZUREWLBACKUPHANAUSER). |
24+
1825
### UserErrorInOpeningHanaOdbcConnection
1926

2027
| Error Message | <span style="font-weight:normal">Failed to connect to HANA system</span> |

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ In this article, you will learn how to:
2525
2626
## Prerequisites
2727

28-
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 to set up the database for backup.
28+
Refer to the [prerequisites](tutorial-backup-sap-hana-db.md#prerequisites) and the [What the pre-registration script does](tutorial-backup-sap-hana-db.md#what-the-pre-registration-script-does) sections to set up the database for backup.
2929

3030
### Set up network connectivity
3131

articles/backup/sap-hana-backup-support-matrix.md

Lines changed: 3 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -9,17 +9,6 @@ ms.date: 11/7/2019
99

1010
Azure Backup supports the backup of SAP HANA databases to Azure. This article summarizes the scenarios supported and limitations present when you use Azure Backup to back up SAP HANA databases on Azure VMs.
1111

12-
## Onboard to the public preview
13-
14-
Onboard to the public preview as follows:
15-
16-
* 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).
17-
* For PowerShell, run this cmdlet. It should complete as "Registered".
18-
19-
```PowerShell
20-
Register-AzProviderFeature -FeatureName "HanaBackup" –ProviderNamespace Microsoft.RecoveryServices
21-
```
22-
2312
> [!NOTE]
2413
> The frequency of log backup can now be set to a minimum of 15 minutes. Log backups only begin to flow after a successful full backup for the database has completed.
2514
@@ -28,9 +17,9 @@ Register-AzProviderFeature -FeatureName "HanaBackup" –ProviderNamespace Micros
2817
| **Scenario** | **Supported configurations** | **Unsupported configurations** |
2918
| -------------------------- | ------------------------------------------------------------ | ------------------------------------------------------------ |
3019
| **Topology** | SAP HANA running in Azure Linux VMs only | HANA Large Instances (HLI) |
31-
| **Geos** | **GA:**<br />**Europe**West Europe, North Europe, France Central, UK South, UK West, Germany North, Germany West Central, Switzerland North, Switzerland West<br />**Asia Pacific** – Australia Central, Australia Central 2, Australia East, Australia Southeast, Japan East, Japan West, Korea Central, Korea South<br /><br>**Preview:**<br />**Americas** – Central US, East US 2, East US, North Central US, South Central US, West US 2, West Central US, West US, Canada Central, Canada East <br />**Asia Pacific**East Asia, Southeast Asia, Central India, South India | China East, China North, China East2, China North 2, West India, Central Switzerland North, South Africa North, South Africa West, UAE North, UAE Central, Azure Government regions, France South, Brazil South |
32-
| **OS versions** | SLES 12 with SP2, SP3, or SP4 | SLES 15, RHEL |
33-
| **HANA versions** | SDC on HANA 1.x, MDC on HANA 2.x <= SPS04 Rev 44 | - |
20+
| **Geos** | **GA:**<br> **Americas**Central US, East US 2, East US, North Central US, South Central US, West US 2, West Central US, West US, Canada Central, Canada East, Brazil South <br> **Asia Pacific** – Australia Central, Australia Central 2, Australia East, Australia Southeast, Japan East, Japan West, Korea Central, Korea South, East Asia, Southeast Asia, Central India, South India, West India, China East, China North, China East2, China North 2 <br> **Europe**West Europe, North Europe, France Central, UK South, UK West, Germany North, Germany West Central, Switzerland North, Switzerland West, Central Switzerland North <br> **Africa / ME** - South Africa North, South Africa West, UAE North, UAE Central <BR> **Azure Government regions** | France South, Germany Central, Germany Northeast, US Gov IOWA |
21+
| **OS versions** | SLES 12 with SP2, SP3, or SP4; SLES 15 | RHEL |
22+
| **HANA versions** | SDC on HANA 1.x, MDC on HANA 2.x <= SPS04 Rev 45 | - |
3423
| **HANA deployments** | SAP HANA on a single Azure VM - Scale up only | Scale-out |
3524
| **HANA Instances** | A single SAP HANA instance on a single Azure VM – scale up only | Multiple SAP HANA instances on a single VM |
3625
| **HANA database types** | Single Database Container (SDC) ON 1.x, Multi-Database Container (MDC) on 2.x | MDC in HANA 1.x |

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -38,11 +38,11 @@ A renamed database is treated as a new database. Therefore, the service will tre
3838

3939
### What are the prerequisites to back up SAP HANA databases on an Azure VM?
4040

41-
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.
41+
Refer to the [prerequisites](tutorial-backup-sap-hana-db.md#prerequisites) and [What the pre-registration script does](tutorial-backup-sap-hana-db.md#what-the-pre-registration-script-does) sections.
4242

4343
### What permissions should be set for Azure to be able to back up SAP HANA databases?
4444

45-
Running the pre-registration script sets the required permissions to allow Azure to back up SAP HANA databases. You can find more about the permissions [here](tutorial-backup-sap-hana-db.md#setting-up-permissions).
45+
Running the pre-registration script sets the required permissions to allow Azure to back up SAP HANA databases. You can find more what the pre-registration script does [here](tutorial-backup-sap-hana-db.md#what-the-pre-registration-script-does).
4646

4747
### Will backups work after migrating SAP HANA from 1.0 to 2.0?
4848

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

Lines changed: 33 additions & 67 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Tutorial - Back up SAP HANA databases in Azure VMs
33
description: In this tutorial, learn how to back up SAP HANA databases running on Azure VM to an Azure Backup Recovery Services vault.
44
ms.topic: tutorial
5-
ms.date: 11/12/2019
5+
ms.date: 02/24/2020
66
---
77

88
# Tutorial: Back up SAP HANA databases in an Azure VM
@@ -17,36 +17,16 @@ This tutorial shows you how to back up SAP HANA databases running on Azure VMs t
1717
1818
[Here](sap-hana-backup-support-matrix.md#scenario-support) are all the scenarios that we currently support.
1919

20-
## Onboard to the public preview
21-
22-
Onboard to the public preview as follows:
23-
24-
* 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).
25-
26-
* For PowerShell, run this cmdlet. It should complete as "Registered".
27-
28-
```powershell
29-
Register-AzProviderFeature -FeatureName "HanaBackup" –ProviderNamespace Microsoft.RecoveryServices
30-
```
31-
3220
## Prerequisites
3321

3422
Make sure you do the following before configuring backups:
3523

36-
1. On the VM running the SAP HANA database, install and enable ODBC driver packages from the official SLES package/media using zypper, as follows:
37-
38-
```bash
39-
sudo zypper update
40-
sudo zypper install unixODBC
41-
```
42-
43-
>[!NOTE]
44-
> If you are not updating the repositories, make sure the version of unixODBC is minimum 2.3.4. To know the version of uniXODBC, run `odbcinst -j` as root
45-
>
46-
47-
2. Allow connectivity from the VM to the internet, so that it can reach Azure, as described in the [procedure below](#set-up-network-connectivity).
48-
49-
3. Run the pre-registration script in the virtual machine where HANA is installed as a root user. [This script](https://aka.ms/scriptforpermsonhana) will set the [right permissions](#setting-up-permissions).
24+
* Allow connectivity from the VM to the internet, so that it can reach Azure, as described in the [set up network connectivity](#set-up-network-connectivity) procedure below.
25+
* A key should exist in the **hdbuserstore** that fulfills the following criteria:
26+
* It should be present in the default **hdbuserstore**
27+
* For MDC, the key should point to the SQL port of **NAMESERVER**. In the case of SDC it should point to the SQL port of **INDEXSERVER**
28+
* It should have credentials to add and delete users
29+
* Run the SAP HANA backup configuration script (pre-registration script) in the virtual machine where HANA is installed, as the root user. [This script](https://aka.ms/scriptforpermsonhana) gets the HANA system ready for backup. Refer to the [What the pre-registration script does](#what-the-pre-registration-script-does) section to understand more about the pre-registration script.
5030

5131
## Set up network connectivity
5232

@@ -105,27 +85,13 @@ Use NSG service tags | Easier to manage as range changes are automatically merge
10585
Use Azure Firewall FQDN tags | Easier to manage as the required FQDNs are automatically managed | Can be used with Azure Firewall only
10686
Use an HTTP proxy | Granular control in the proxy over the storage URLs is allowed <br/><br/> Single point of internet access to VMs <br/><br/> Not subject to Azure IP address changes | Additional costs to run a VM with the proxy software
10787

108-
## Setting up permissions
109-
110-
The pre-registration script performs the following actions:
111-
112-
1. Creates AZUREWLBACKUPHANAUSER in the HANA system and adds these required roles and permissions:
113-
* DATABASE ADMIN: to create new DBs during restore.
114-
* CATALOG READ: to read the backup catalog.
115-
* SAP_INTERNAL_HANA_SUPPORT: to access a few private tables.
116-
2. Adds a key to Hdbuserstore for the HANA plug-in to handle all operations (database queries, restore operations, configuring and running backup).
117-
118-
To confirm the key creation, run the HDBSQL command on the HANA machine with SIDADM credentials:
88+
## What the pre-registration script does
11989

120-
```hdbsql
121-
hdbuserstore list
122-
```
90+
Running the pre-registration script performs the following functions:
12391

124-
The command output should display the {SID}{DBNAME} key, with the user shown as AZUREWLBACKUPHANAUSER.
125-
126-
>[!NOTE]
127-
> 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.
128-
>
92+
* It installs or updates any necessary packages required by the Azure Backup agent on your distribution.
93+
* It performs outbound network connectivity checks with Azure Backup servers and dependent services like Azure Active Directory and Azure Storage.
94+
* It logs into your HANA system using the user key listed as part of the [prerequisites](#prerequisites). This key is used to create a backup user (AZUREWLBACKUPHANAUSER) in the HANA system and can be deleted after the pre-registration script runs successfully. This backup user (AZUREWLBACKUPHANAUSER) will allow the backup agent to discover, backup and restore databases in your HANA system.
12995

13096
## Create a Recovery Service vault
13197

@@ -137,25 +103,25 @@ To create a Recovery Services vault:
137103

138104
2. On the left menu, select **All services**
139105

140-
![Select All services](./media/tutorial-backup-sap-hana-db/all-services.png)
106+
![Select All services](./media/tutorial-backup-sap-hana-db/all-services.png)
141107

142108
3. In the **All services** dialog box, enter **Recovery Services**. The list of resources filters according to your input. In the list of resources, select **Recovery Services vaults**.
143109

144-
![Select Recovery Services vaults](./media/tutorial-backup-sap-hana-db/recovery-services-vaults.png)
110+
![Select Recovery Services vaults](./media/tutorial-backup-sap-hana-db/recovery-services-vaults.png)
145111

146112
4. On the **Recovery Services** vaults dashboard, select **Add**.
147113

148-
![Add Recovery Services vault](./media/tutorial-backup-sap-hana-db/add-vault.png)
114+
![Add Recovery Services vault](./media/tutorial-backup-sap-hana-db/add-vault.png)
149115

150-
The **Recovery Services vault** dialog box opens. Provide values for the **Name, Subscription, Resource group,** and **Location**
116+
The **Recovery Services vault** dialog box opens. Provide values for the **Name, Subscription, Resource group,** and **Location**
151117

152-
![Create Recovery Services vault](./media/tutorial-backup-sap-hana-db/create-vault.png)
118+
![Create Recovery Services vault](./media/tutorial-backup-sap-hana-db/create-vault.png)
153119

154-
* **Name**: The name is used to identify the recovery services vault and must be unique to the Azure subscription. Specify a name that has at least two, but not more than 50 characters. The name must start with a letter and consist only of letters, numbers, and hyphens. For this tutorial, we've used the name **SAPHanaVault**.
155-
* **Subscription**: Choose the subscription to use. If you're a member of only one subscription, you'll see that name. If you're not sure which subscription to use, use the default (suggested) subscription. There are multiple choices only if your work or school account is associated with more than one Azure subscription. Here, we have used the **SAP HANA solution lab subscription** subscription.
156-
* **Resource group**: Use an existing resource group or create a new one. Here, we have used **SAPHANADemo**.<br>
157-
To see the list of available resource groups in your subscription, select **Use existing**, and then select a resource from the drop-down list box. To create a new resource group, select **Create new** and enter the name. For complete information about resource groups, see [Azure Resource Manager overview](https://docs.microsoft.com/azure/azure-resource-manager/resource-group-overview).
158-
* **Location**: Select the geographic region for the vault. The vault must be in the same region as the Virtual Machine running SAP HANA. We have used **East US 2**.
120+
* **Name**: The name is used to identify the recovery services vault and must be unique to the Azure subscription. Specify a name that has at least two, but not more than 50 characters. The name must start with a letter and consist only of letters, numbers, and hyphens. For this tutorial, we've used the name **SAPHanaVault**.
121+
* **Subscription**: Choose the subscription to use. If you're a member of only one subscription, you'll see that name. If you're not sure which subscription to use, use the default (suggested) subscription. There are multiple choices only if your work or school account is associated with more than one Azure subscription. Here, we have used the **SAP HANA solution lab subscription** subscription.
122+
* **Resource group**: Use an existing resource group or create a new one. Here, we have used **SAPHANADemo**.<br>
123+
To see the list of available resource groups in your subscription, select **Use existing**, and then select a resource from the drop-down list box. To create a new resource group, select **Create new** and enter the name. For complete information about resource groups, see [Azure Resource Manager overview](https://docs.microsoft.com/azure/azure-resource-manager/resource-group-overview).
124+
* **Location**: Select the geographic region for the vault. The vault must be in the same region as the Virtual Machine running SAP HANA. We have used **East US 2**.
159125

160126
5. Select **Review + Create**.
161127

@@ -180,15 +146,15 @@ Now that the databases we want to back up are discovered, let's enable backup.
180146

181147
1. Click **Configure Backup**.
182148

183-
![Configure backup](./media/tutorial-backup-sap-hana-db/configure-backup.png)
149+
![Configure backup](./media/tutorial-backup-sap-hana-db/configure-backup.png)
184150

185151
2. In **Select items to back up**, select one or more databases that you want to protect, and then click **OK**.
186152

187-
![Select items to back up](./media/tutorial-backup-sap-hana-db/select-items-to-backup.png)
153+
![Select items to back up](./media/tutorial-backup-sap-hana-db/select-items-to-backup.png)
188154

189155
3. In **Backup Policy > Choose backup policy**, create a new backup policy for the database(s), in accordance with the instructions in the next section.
190156

191-
![Choose backup policy](./media/tutorial-backup-sap-hana-db/backup-policy.png)
157+
![Choose backup policy](./media/tutorial-backup-sap-hana-db/backup-policy.png)
192158

193159
4. After creating the policy, on the **Backup menu**, click **Enable backup**.
194160

@@ -207,11 +173,11 @@ Specify the policy settings as follows:
207173

208174
1. In **Policy name**, enter a name for the new policy. In this case, enter **SAPHANA**.
209175

210-
![Enter name for new policy](./media/tutorial-backup-sap-hana-db/new-policy.png)
176+
![Enter name for new policy](./media/tutorial-backup-sap-hana-db/new-policy.png)
211177

212178
2. In **Full Backup policy**, select a **Backup Frequency**. You can choose **Daily** or **Weekly**. For this tutorial, we chose the **Daily** backup.
213179

214-
![Select a backup frequency](./media/tutorial-backup-sap-hana-db/backup-frequency.png)
180+
![Select a backup frequency](./media/tutorial-backup-sap-hana-db/backup-frequency.png)
215181

216182
3. In **Retention Range**, configure retention settings for the full backup.
217183
* By default, all options are selected. Clear any retention range limits you don't want to use and set those that you do.
@@ -225,9 +191,9 @@ Specify the policy settings as follows:
225191

226192
![Differential backup policy](./media/tutorial-backup-sap-hana-db/differential-backup-policy.png)
227193

228-
>[!NOTE]
229-
>Incremental backups aren't currently supported.
230-
>
194+
>[!NOTE]
195+
>Incremental backups aren't currently supported.
196+
>
231197
232198
7. Click **OK** to save the policy and return to the main **Backup policy** menu.
233199
8. Select **Log Backup** to add a transactional log backup policy,
@@ -236,9 +202,9 @@ Specify the policy settings as follows:
236202

237203
![Log backup policy](./media/tutorial-backup-sap-hana-db/log-backup-policy.png)
238204

239-
>[!NOTE]
240-
> Log backups only begin to flow after one successful full backup is completed.
241-
>
205+
>[!NOTE]
206+
> Log backups only begin to flow after one successful full backup is completed.
207+
>
242208
243209
9. Click **OK** to save the policy and return to the main **Backup policy** menu.
244210
10. After you finish defining the backup policy, click **OK**.

0 commit comments

Comments
 (0)