Recovering a SAP HANA Cloud Database

In this lesson, you'll know why you may perform a database recovery. You'll also see the tasks you need to be perform before starting the recovery process to resolve an error, in an SAP HANA database instance.

You've discovered that during the daily data import cycle on September 21, 2021 at 09:33:08 AM the wrong import file was used. This logical problem needs to be corrected by a database recovery one second before the import started.

There are many reasons to recover a database. The following, not exhaustive, list gives the most common reasons.

• Infrastructure failure: The cloud consists of hardware and software, such as servers, network components, storage, visualization software, operating systems, and management tools, and they can fail. It is up to the cloud provider to setup safeguards and redundancies to make sure the failures have minimal to zero impact on the applications running in the cloud.
• Logical error: Often created by a fault in an application, or report, or a mistake of a database user.
• Database reset: Often used to rollback the database to a known state after a testing scenario. This way you can rerun a test several times from the beginning and try out different configuration settings.

When a database error has occurred, you can recover an SAP HANA database to a Point In Time just before the database error occurred. This will fix the problem, but maybe not the root cause. A best practice should be to first investigate the root cause before you start the database recovery.

See the following video for the checks before you start a recovery.

See the following video to perform a database recovery.