SAP HANA

Este conteúdo não está disponível em sua língua ainda.

Native SAP HANA protection through the Backint interface (and file-based backups), with incremental/differential deltas, continuous log backup for point-in-time recovery, MDC multitenant and encryption awareness — enterprise-grade HANA backup driven by NGBackup, no shell wrappers.

Capabilities

Backint streaming backup (zero-staging) and file-based backup
Full, incremental and differential data backups
Continuous log backup for point-in-time recovery
Backint restore and delete — recover through the same zero-staging pipe, and let HANA’s catalog drive backint housekeeping
MDC multitenant (SYSTEMDB + tenants) and scale-out aware
NGBackup-native restore automation (no external scripts)

Prerequisites

A HANA backup user reachable via an hdbuserstore key (no inline password):
Terminal window
```
hdbuserstore SET BACKUPKEY <host>:3<inst>13 SYSTEM <password>
```
The user needs BACKUP ADMIN + CATALOG READ (in SYSTEMDB for FOR FULL SYSTEM; per-tenant otherwise).
For mode=backint, register the agent in global.ini [backup] (data_backup_parameter_file, log_backup_parameter_file, catalog_backup_using_backint = true, log_backup_using_backint = true) and point /usr/sap/<SID>/SYS/global/hdb/opt/hdbbackint at the NGBackup agent.

Configure

Add the plugin to a Content on the client you want to protect:

Content {
  Name = "hana"
  Include {
    Options { Plugin = "hana: mode=backint sid=HXE instance=90 userstore_key=BACKUPKEY" }
  }
}

All parameters are space-separated key=value pairs (not colon-separated). See the Content reference for Content options.

Parameter	Meaning
`mode`	`backint` (default, zero-staging) · `file` (`BACKUP DATA USING FILE`) · `logbackup` (ship log backups) · `topology` (discover only)
`sid`	SAP system id, e.g. `HXE` — required
`instance`	instance number, e.g. `90`
`userstore_key`	hdbuserstore key for the backup user — required
`staging_dir`	staging directory for `mode=file`
`hdbsql_path`	absolute path to `hdbsql` (default: resolve from `PATH`)
`metrics_addr`	Prometheus bind address, e.g. `0.0.0.0:9119` (default: off)

Backup level follows the Job (Full / Incremental / Differential) → BACKUP DATA [INCREMENTAL|DIFFERENTIAL] USING {BACKINT|FILE}.

Restore

Restore is NGBackup-native via a restore configuration: recover a tenant to a specific backup or to a point in time.

Full recover: RECOVER DATA FOR <tenant> USING BACKUP_ID <id> CLEAR LOG
Point-in-time: RECOVER DATABASE FOR <tenant> UNTIL TIMESTAMP '<ts>' CLEAR LOG

The tenant is stopped automatically before recovery (ALTER SYSTEM STOP DATABASE <tenant>) and comes back online when recovery completes.

For mode=backint, recovery drives the same NGBackup agent in reverse: HANA requests each stored object by its external backup id and NGBackup streams it back through the pipe — no staging, no scripts. Catalog housekeeping (deleting obsolete backups) flows through the same agent.