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: docs/AZURE_BACKUP.md
+21-16Lines changed: 21 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,18 +1,20 @@
1
-
# Azure Backup Functional Testing for SAP HANA
1
+
# Functional Test for Azure Backup for SAP HANA
2
2
3
-
The SAP Testing Automation Framework includes an Azure Backup testing component that validates backup and restore operations for SAP HANA databases deployed on Azure. It exercises the [Azure Backup for SAP HANA](https://learn.microsoft.com/azure/backup/sap-hana-database-about) service through the Python SDK (`azure-mgmt-recoveryservicesbackup`) and native HANA recovery commands.
3
+
The SAP Testing Automation Framework includes an Azure Backup testing component that validates the configuration of Azure Backup infrastructure and functionality of restore operations by performing actual restore for SAP HANA databases deployed on Azure.
4
+
5
+
> **Important:** This is a **testing and validation tool only**. It is designed to verify that Azure Backup is correctly configured and that restore operations function as expected. It should **not** be used as a substitute for actual SAP HANA database restore procedures in any scenario.
4
6
5
7
## Supported Scenarios
6
8
7
9
The framework supports both **HA (two-node cluster)** and **Non-HA (single-node)** HANA deployments. Five test cases cover the end-to-end backup-restore lifecycle:
8
10
9
11
| # | Test Case | Task Name | Description |
10
12
|---|-----------|-----------|-------------|
11
-
| 1 | Azure Backup Setup Verification|`backup-setup-verification`| Discovers all protected HANA databases in the Recovery Services vault, verifies backup configuration health, and checks that recent restore points exist. |
13
+
| 1 | Azure Backup Configuration Validation|`backup-setup-verification`| Discovers all protected HANA databases in the Recovery Services vault, verifies backup configuration health, and checks that recent restore points exist. |
12
14
| 2 | Restore Backup to HANA DB |`restore-to-db`| Triggers a full or point-in-time restore to the original HANA database via Azure Backup, monitors the restore job, then validates HANA is running. |
13
15
| 3 | Restore Backup to FileSystem |`restore-to-filesystem`| Restores the HANA backup as files to a filesystem path, verifies the files are present, then recovers the HANA DB from those files and validates it is operational. |
14
16
| 4 | Recover DB using Database Commands |`recover-db-commands`| Tests native HANA recovery using `recoverSys.py` / `RECOVER DATA`. Queries the backup catalog, stops HANA, performs recovery, restarts, and validates consistency. |
15
-
| 5 | Cross-VM Restore |`restore-cross-vm`| Restores a HANA backup from VM-1 to VM-2 (AlternateWorkloadRestore). Validates the target HANA instance starts and the database is consistent. Requires ≥ 2 HANA nodes. |
17
+
| 5 | Cross-VM Restore |`restore-cross-vm`| Restores **tenant databases only** from VM-1 to VM-2 (AlternateWorkloadRestore). SYSTEMDB is not restored in cross-VM scenarios. Validates the target HANA instance starts and the databases are consistent. |
16
18
17
19
## Prerequisites
18
20
@@ -40,7 +42,7 @@ For identity setup, see [Setup Guide — Identity and Authorization](./SETUP.MD#
40
42
- The management server must have SSH connectivity to all HANA DB hosts.
41
43
- The `<sid>adm` user must be able to run `HDB stop`, `HDB start`, `sapcontrol`, and `hdbsql` commands.
42
44
- For test case 3 (restore-to-filesystem), the target filesystem path must be writable.
43
-
- For test case 5 (cross-VM restore), at least 2 HANA nodes must be in the inventory.
45
+
- For test case 5 (cross-VM restore), target VM information must be provided.
0 commit comments