Loading...

Restoring the SAP HANA SYSTEMDB Database

Restore the multitenant database container SYSTEMDB database. You can only recover the SYSTEMDB database to the most recent state.

If you need to restore a SYSTEMDB database and tenant databases, perform the SYSTEMDB database restore first, and then restore the tenant databases.

You can restore to the same destination, or to the following new destinations:

  • Restore to a new destination that has the same SYSTEMDB SID as the source
  • Restore to a new destination that has a different SYSTEMDB SID from the source

Before You Begin

  1. Perform a SAP HANA full backup on a Multitenant SYSTEMDB database.
  2. Verify that the SAP HANA software version that is used for restore is of the same version, or a later version than the software version used during backup.

Procedure

  1. You can perform a restore on the instances or job details page.
    • Instances: From the navigation pane, click Solutions > DB Instances, in the column for the instance, click  Restore.
    • Database Details: From the navigation pane, click Solutions > DB Instances > instance, in the upper right, click Restore.
    • Job details: From the navigation pane, click Jobs > job ID. Then, in the Job summary section, click Restore.

      The Restore Options page appears.

  2. From the Destination Client list, select the destination host to use for the restore.
  3. From the Destination instance list, select the destination instance to use for the restore.
  4. Choose the database recover option.
    • To recover the database, select Recover Database.
      • To recover to the latest backup job completion time, select Current time.
      • To recover to a point-in-time, select Point in Time, and type the date and time.
    • To recover only the data, select Recover data only.

      To use this option, you must perform the restore by using a full backup.

      If you restore by specifying the internal backup job ID, then you must have the catalog backup available with backint. SAP HANA creates the internal backup ID .

      If you restore by specifying the backup prefix, then you do not have to have the catalog backup available with backint. The Commvault software creates the backup prefix by pre-pending the job ID to the backup prefix. For example, 4815976_COMPLETE_DATA_BACKUP.

      1. Select the backup to use for the restore:
      • To restore by specifying the backup prefix, in the Backup prefix box, type the backup prefix for the backup that you want to restore.
      • To restore by specifying the internal backup job ID, in the Internal Backup ID box, type the internal backup job ID that you want to restore.
  5. To verify that all the backups required for the recovery operation are available, select the Check Access check box.
  6. To initialize the log area after the restore, select the Initialize log area check box.
  7. Click Submit.

Result

The software restores the SYSTEMDB database to the specified location.

If you did not select the Initialize Logs check box, then the job goes to pending with a job pending reason (JPR) that is similar to the following message:

Error Code: [18:146] Description: SAP HANA Error [2017-02-28T07:59:55-05:00 P003115 15a84cd9aa8 ERROR RECOVERY RECOVER DATA finished with error: [448] recovery could not be completed, volume 1, reached log position 0, [110058] The existing log area is not compatible to the log and data backups ]. Source: hana07, Process: ClHanaAgent

What to Do Next

You can control or view the job. For more information, see Jobs.

  • If you only restored the SYSTEMDB database, then after the restore the SYSTEMDB is in the Up state, but you need to manually start the tenant databases. On the command line, type the following command:

    hdbsql -U <hdbuserstore_key>

    Example

    hdbsql -U BACKUPM

    On the command line, type the following command:

    hdbsql SYSTEMDB=> alter system start database <Tenant_Database_Name>

    Example

    hdbsql SYSTEMDB=> alter system start database mn1
    0 rows affected (overall time 733.912 msec; server time 732.685 msec)

  • If you need to restore the system and tenant databases, perform a tenant database restore.

Last modified: 3/10/2018 8:02:07 PM