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-with-hana-system-replication-backup.md
+28-2Lines changed: 28 additions & 2 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: Back up SAP HANA System Replication databases on Azure VMs
3
3
description: In this article, discover how to back up SAP HANA databases with HANA System Replication enabled.
4
4
ms.topic: how-to
5
-
ms.date: 03/08/2023
5
+
ms.date: 07/06/2023
6
6
ms.service: backup
7
7
ms.custom: ignite-2022
8
8
author: jyothisuri
@@ -13,8 +13,11 @@ ms.author: jsuri
13
13
14
14
SAP HANA databases are critical workloads that require a low recovery-point objective (RPO) and long-term retention. This article describes how you can back up SAP HANA databases that are running on Azure virtual machines (VMs) to an Azure Backup Recovery Services vault by using [Azure Backup](backup-overview.md).
15
15
16
+
You can also switch the protection of SAP HANA database on Azure VM (standalone) on Azure Backup to HSR. [Learn more](#switch-database-protection-from-standalone-to-hsr-on-azure-backup).
17
+
16
18
>[!Note]
17
-
> For more information about the supported configurations and scenarios, see [SAP HANA backup support matrix](sap-hana-backup-support-matrix.md).
19
+
>- The support for HSR + Database scenario is currently not available because there is a restriction to have VM and Vault in the same region.
20
+
>- For more information about the supported configurations and scenarios, see [SAP HANA backup support matrix](sap-hana-backup-support-matrix.md).
18
21
19
22
## Prerequisites
20
23
@@ -227,6 +230,29 @@ Backups run in accordance with the policy schedule. Learn how to [run an on-dema
227
230
228
231
You can run an on-demand backup using SAP HANA native clients to local file-system instead of Backint. Learn more how to [manage operations using SAP native clients](sap-hana-database-manage.md#manage-operations-using-sap-hana-native-clients).
229
232
233
+
## Switch database protection from standalone to HSR on Azure Backup
234
+
235
+
You can now switch the protection of SAP HANA database on Azure VM (standalone) on Azure Backup to HSR. If you’ve already configured HSR and protecting only the primary node using Azure Backup, you can modify the configuration to protect both primary and secondary nodes.
236
+
237
+
Follow these steps:
238
+
239
+
1. On standalone VM, Primary node, or Secondary node (once protected using Azure Backup), go to *vault* > **Backup Items** > **SAP HANA in Azure VM** > **View Details** > **Stop backup**, and then select **Retain backup data** > **Stop backup** to stop backup and retain data.
240
+
241
+
2. (Mandatory) [Run the latest preregistration script](sap-hana-database-with-hana-system-replication-backup.md#run-the-preregistration-script) on both primary and condary VM nodes
242
+
243
+
The preregistration script contains the HSR attributes.
You can also configure the backup with clustering tools, such as **Pacemaker**.
247
+
248
+
Skip this step if HSR configuration is complete.
249
+
250
+
4. Add the Primary and secondary nodes to Azure Backup, [rediscover the databases](sap-hana-database-with-hana-system-replication-backup.md#discover-the-databases), and [resume protection](sap-hana-database-manage.md#resume-protection-for-an-sap-hana-database-or-hana-instance).
251
+
252
+
>[!Note]
253
+
>For HSR deployments, Protected Instance cost is charged to HSR container. Two nodes (primary and secondary) will form a single HSR logical container and storage cost is charged as applicable.
254
+
255
+
5. Before a planned failover, [ensure that both VMs/Nodes are registered to the vault (physical and logical registration)](sap-hana-database-manage.md#verify-the-registration-status-of-vms-or-nodes-to-the-vault).
0 commit comments