Back to section

/ HANA / SAP HANA Recovery Wizard

SAP HANA Backup & Recovery Validation

Recovery Validation — restore a SAP HANA tenant database to a selected recovery point following simulated business data loss and verify successful recovery using Complete Data Backups and Transaction Log Backups.

T-Code / Command
SAP HANA Recovery Wizard
System
SYSTEMDB@HDB → Tenant Database (NBU)
Objective
Demonstrate the complete SAP HANA backup and recovery lifecycle by creating business data, performing a Complete Data Backup, validating the Backup Catalog, simulating accidental data loss, restoring the tenant database using Point-in-Time Recovery, and verifying successful restoration of the original business records.

Operational Scenario

This investigation was performed in a sandbox SAP HANA environment. In production, database recovery is normally performed during an approved maintenance window because the target database must be offline during recovery. Before recovery begins, SAP Basis administrators validate backup availability, confirm the recovery strategy, coordinate planned downtime, and perform post-recovery validation before returning the database to service.

Business Impact

Reliable backup and recovery procedures are critical for protecting business data against hardware failures, software issues, and user errors. Regular recovery validation provides confidence that backups are usable and that business services can be restored within expected recovery objectives.

/ Tools Used

SAP HANA StudioSQL ConsoleSAP HANA Recovery WizardM_BACKUP_CATALOGSQL Commands

/ Step-by-Step Execution

01

Business Data Creation & Verification

A sample EMPLOYEE table was created and populated with five employee records to establish a known baseline before backup operations began.

sql — SYSTEMDB
sql>CREATE COLUMN TABLE EMPLOYEE (
sql> EMP_ID INTEGER,
sql> NAME NVARCHAR(50),
sql> DEPARTMENT NVARCHAR(50)
sql>);
sql>
sql>INSERT INTO EMPLOYEE VALUES
sql>(1,'John Smith','Sales'),
sql>(2,'Sarah Jones','Finance'),
sql>(3,'Michael Brown','IT'),
sql>(4,'Emma Wilson','HR'),
sql>(5,'David Taylor','Operations');
sql>
sql>SELECT * FROM EMPLOYEE;
01-employee-data-created.png
Operational Observation

Five employee records were successfully created and verified within the tenant database. This dataset served as the reference point for validating the recovery process.

02

Complete Database Backup

A Complete Data Backup was performed to create a consistent recovery point before any changes were made to the business data.

sql — SYSTEMDB
sql>BACKUP DATA USING FILE ('EMPLOYEE_FULL_BACKUP');
02-complete-backup.png
Operational Observation

The Complete Data Backup completed successfully without warnings or errors, establishing a valid recovery point for subsequent recovery operations.

03

Backup Catalog Validation

Before initiating the database recovery procedure, the SAP HANA Backup Catalog was reviewed to confirm that the Complete Data Backup had been successfully registered and that a valid recovery point was available. A detailed investigation of backup verification is documented separately in the Backup Verification (M_BACKUP_CATALOG) case study.

sql — SYSTEMDB
sql>SELECT
sql> ENTRY_TYPE_NAME,
sql> STATE_NAME,
sql> SYS_START_TIME
sql>FROM M_BACKUP_CATALOG
sql>ORDER BY SYS_START_TIME DESC;
03-backup-catalog.png
Operational Observation

The Backup Catalog confirmed that the Complete Data Backup completed successfully and was available for recovery. The backup status and timestamp verified that a valid recovery point existed before the recovery procedure was initiated.

04

Simulated Business Data Loss

Business records were intentionally deleted from the EMPLOYEE table to simulate accidental data loss as part of the recovery validation exercise.

sql — SYSTEMDB
sql>DELETE FROM EMPLOYEE;
sql>COMMIT;
04-simulated-data-deletion.png
Operational Observation

The DELETE transaction completed successfully and permanently removed all employee records from the database.

05

Data Loss Verification

Two verification queries were executed to confirm that the employee records had been deleted before the recovery procedure was initiated.

sql — SYSTEMDB
sql>SELECT * FROM EMPLOYEE;
sql>
sql>SELECT COUNT(*) AS TOTAL_ROWS FROM EMPLOYEE;
05-empty-employee-table.png
05B-row-count-verification.png
Operational Observation

The first query confirmed that no employee records were returned, while the second verified that the table contained 0 rows. Together, these results confirmed that the business data had been successfully removed while the EMPLOYEE table remained available for recovery validation.

06

Recovery Wizard Initialization

The SAP HANA Recovery Wizard was launched and the NBU tenant database selected as the recovery target.

06-recovery-wizard.png
Operational Observation

The recovery workflow successfully identified the tenant database and prepared the recovery environment for configuration.

07

Point-in-Time Recovery Configuration

Point-in-Time Recovery was configured by selecting a recovery timestamp immediately before the DELETE transaction occurred. Backup used: EMPLOYEE_FULL_BACKUP.

07-point-in-time-recovery.png
Operational Observation

The selected recovery point ensured that SAP HANA restored the Complete Data Backup while excluding the committed DELETE transaction.

08

Database Recovery Execution

The tenant database was restored using the selected Complete Data Backup together with the required transaction log backups to the selected recovery point.

08-recovery-successful.png
Operational Observation

The recovery completed successfully without errors, and the tenant database returned to an operational state.

09

Post-Recovery Data Verification

A final SQL verification was performed to confirm that the original employee records had been successfully restored.

sql — SYSTEMDB
sql>SELECT * FROM EMPLOYEE;
09-restored-employee-data.png
Operational Observation

The verification query returned all five employee records, confirming successful Point-in-Time Recovery and restoration of the original business data.

/ Technical Evidence Collected

ValidationResult / Status
Business Data CreatedFive records — successful
Complete BackupSuccessful
Backup CatalogRegistered
Data DeletionSuccessful
Data Verification0 rows
RecoverySuccessful
Data RestoredFive rows

/ Assessment

The recovery validation successfully demonstrated the complete SAP HANA backup and recovery lifecycle. The investigation confirmed that a valid Complete Data Backup was available within the Backup Catalog, and that Point-in-Time Recovery restored the tenant database to the selected recovery point. The exercise also highlighted the operational difference between Recover to Most Recent State, which replays all committed transactions, and Point-in-Time Recovery, which allows recovery to a precise moment before unwanted changes occurred.

/ Project Outcome

The recovery exercise successfully restored the original business records following simulated data loss. All recovery objectives were achieved, confirming that the backup strategy, transaction log processing, and recovery procedure functioned as expected. The investigation provided practical experience in SAP HANA backup administration, disaster recovery planning, recovery execution, and post-recovery validation.

/ Case Study PDF

/ Related Investigation

Backup Verification (M_BACKUP_CATALOG)

View the supporting investigation demonstrating how the Backup Catalog was verified before initiating database recovery and confirming recovery readiness.

View Related Case Study

Operational Summary

Lessons Learned
  • Complete Data Backups provide the baseline required for database recovery.
  • Transaction Log Backups enable recovery to a precise point in time.
  • Recover to Most Recent State replays all committed transactions, including unwanted deletions.
  • Point-in-Time Recovery allows administrators to recover data before accidental changes occur.
  • Post-recovery validation is essential before returning a database to production.
Skills Demonstrated
SAP HANA Backup AdministrationPoint-in-Time RecoverySAP HANA Recovery WizardBackup ValidationTransaction Log RecoverySQL AdministrationDisaster Recovery PlanningDatabase Recovery Testing