Backup
Backing up SAP HANA protects the database, the store of all application data, so it can be recovered after failure or corruption. HANA has specific backup mechanisms (data + log) that enable point-in-time recovery.
As always, a backup is only proven by a successful restore.
- Data backups capture a point in time; log backups capture every change since.
- Backups are performed via the HANA cockpit, SQL, or (commonly) integrated with enterprise backup tools through Backint.
- Data backups: full (and delta/incremental) snapshots of the in-memory data persisted to disk.
- Watch out: Backing up data but not logs, no point-in-time recovery.
What HANA backup covers
- Data backups: full (and delta/incremental) snapshots of the in-memory data persisted to disk.
- Log backups: continuous backups of the redo log, essential for point-in-time recovery.
- Configuration: so the system can be reconstructed.
Why logs are critical
Data backups capture a point in time; log backups capture every change since. Together they let you recover to any moment (point-in-time recovery), for example just before a corruption. Frequent log backups mean minimal data loss, aligning to your RPO.
How backups are run
Backups are performed via the HANA cockpit, SQL, or (commonly) integrated with enterprise backup tools through Backint. They should be automated, monitored for success, stored securely/offsite, and their retention managed.
Test restores
As always, a backup is only proven by a successful restore. Regularly test HANA restores in a non-production environment to validate the backups and the recovery procedure.
Common pitfalls
- Backing up data but not logs, no point-in-time recovery.
- Never testing a restore.
- Unmonitored backups that silently fail.