You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/backup/sap-hana-database-restore.md
+13-3Lines changed: 13 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Restore SAP HANA databases on Azure VMs
3
3
description: In this article, you'll learn how to restore SAP HANA databases that are running on Azure virtual machines. You can also use Cross Region Restore to restore your databases to a secondary region.
4
4
ms.topic: how-to
5
-
ms.date: 06/20/2023
5
+
ms.date: 07/14/2023
6
6
ms.service: backup
7
7
ms.custom: ignite-2022
8
8
author: jyothisuri
@@ -13,11 +13,11 @@ ms.author: jsuri
13
13
14
14
This article describes how to restore SAP HANA databases that are running on Azure virtual machines (VMs) and that the Azure Backup service has backed up to a Recovery Services vault. You can use the restored data to create copies for development and test scenarios or to return to a previous state.
15
15
16
-
Azure Backup now supports backup and restore of SAP HANA System Replication (HSR) instance (preview).
16
+
Azure Backup now supports backup and restore of SAP HANA System Replication (HSR) instance.
17
17
18
18
>[!Note]
19
19
>- The restore process for HANA databases with HSR is the same as the restore process for HANA databases without HSR. As per SAP advisories, you can restore databases with HSR mode as *standalone* databases. If the target system has the HSR mode enabled, first disable the mode, and then restore the database.
20
-
>- Original Location Recovery (OLR) is currently not supported for HSR.
20
+
>- Original Location Recovery (OLR) is currently not supported for HSR. Select **Alternate location** restore, and then select the source VM as your *Host* from the list.
21
21
>- Restore to HSR instance isn't supported. However, restore only to HANA instance is supported.
22
22
23
23
For information about the supported configurations and scenarios, see the [SAP HANA backup support matrix](sap-hana-backup-support-matrix.md).
@@ -85,6 +85,16 @@ To restore a database, you need the following permissions:
85
85
86
86
:::image type="content" source="./media/sap-hana-db-restore/hana-restore-configuration.png" alt-text="Screenshot that shows where to restore the configuration.":::
87
87
88
+
>[!Note]
89
+
>During restore (applicable to Virtual IP/ Load balancer frontend IP scenario only), if you’re trying to restore a backup to target node after changing the HSR mode as standalone or breaking HSR before restore as recommended by SAP and, ensure that Load Balancer is pointed to the target node.
90
+
>
91
+
>**Example scenarios**:
92
+
>
93
+
>- If you’re using *hdbuserstore set SYSTEMKEY localhost* in your preregistration script, there will be no issues during restore.
94
+
>- If your *hdbuserstore set `SYSTEMKEY <load balancer host/ip>` in your preregistration script and you’re trying to restore the backup to target node, ensure that the load balancer is pointed to the target node that needs to be restored.
95
+
>
96
+
>
97
+
88
98
### Restore to an alternate location
89
99
90
100
1. On the **Restore** pane, under **Where and how to Restore?**, select **Alternate Location**.
Copy file name to clipboardExpand all lines: articles/backup/sap-hana-database-with-hana-system-replication-backup.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -120,6 +120,11 @@ To discover the HSR database, follow these steps:
120
120
121
121
To view the details about all the databases of each discovered VM, select **View details** under the **Step 1: Discover DBs in VMs section**.
122
122
123
+
>[!Note]
124
+
>During discovery or configuration of backup on the secondary node, ignore the status if the **Backup Readiness** state appears **Not Ready** as this is an expected state for the secondary node on HSR.
125
+
>
126
+
> :::image type="content" source="./media/sap-hana-database-with-hana-system-replication-backup/backup-readiness-state.png" alt-text="Screenshot shows the different backup readiness state." lightbox="./media/sap-hana-database-with-hana-system-replication-backup/backup-readiness-state.png":::
0 commit comments