SAP HANA 2.0 Administration · Backup & Recovery

Encrypted HANA backups are spiking CPU/memory on an already-loaded system. Which parameter eases the impact, and what do you trade away — and what does it NOT change?

Answer locked. Get the free KnowCard app to reveal it — plus spaced-repetition review so it actually sticks.

This is one card from the KnowCard library — thousands more across SAP, Linux, Python and more. In the app you get the answer, AI explanations, and cards that come back right before you would forget them. Free to start on iOS, Android or the web.

More in Backup & Recovery

You take a storage snapshot of a running HANA system without telling the database. On recovery, why does HANA treat it as a crash, and what would a database-aware snapshot have done differently?

Before a restore you want to confirm the backup files are not just present but actually uncorrupted. Why is hdbbackupdiag not enough, and which tool do you use?

Under sustained high transaction load, single-segment log backups start queuing up. What HANA feature fixes this, and what is the consequence of leaving max_log_backup_size at its default?

From the system database you need to back up only tenant S14. What is the statement, and what is the easily-skipped detail that changes which database gets backed up?

For a production database you must lose as little data as possible. Which HANA recovery mode do you pick, and why is "to a specific data backup" the wrong choice there?

You want your third-party (Backint) HANA backups to land on a specific path. Why does the usual file-backup path parameter not help here?

Start learning today

Free to start — download the app or use it in your browser.