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
Perform a SAP HANA full backup on a Multitenant SYSTEMDB database.
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.
You can perform a restore on the instances, database details, DbBackupset details, or job details page.
Instances: From the navigation pane, go to Protect > Databases > DB Instances. Select the instance, and then in the upper-right of the page click Restore.
Database Details: From the navigation pane, go to Protect > Databases > DB Instances > instance. In the Recovery points section, click Restore. In the Databases section, you can also select the database that you want to restore, and then, click Restore.
DbBackupset Details: From the navigation pane, go to Protect > Databases > DB Instances > instance > database. In the Recovery points section, 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.
To perform an in-place restore, in the Destination Database, select the database where you want to restore.
To perform an out-of-place restore, complete the following steps:
Click the Out of place tab.
In the Source database, select the source database from where you to restore.
From the Destination Server list, select the destination host to use for the restore.
From the Destination instance list, select the destination instance to use for the restore.
To restore from a snapshot backup, in the HANA data directory box, click Browse and select the HANA directory.
The full path where the destination instance resides. For example, if the SAP HANA SID path is hana/data/SID, then set the Destination Instance SAP HANA directory to: /hana/data.
Note: This is required for IntelliSnap cross instance and cross machine restores.
Choose the database recover option.
To recover the database to a point-in-time, click Up to, and then select the date and time.
To restore by specifying the backup prefix, in the Backup prefix box, type the backup prefix for the backup that you want to restore.
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.
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.
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 .
To verify that all the backups required for the recovery operation are available, select the Check Access check box.
To initialize the log area after the restore, select the Initialize log area check box.
To recover using Delta backups, select the Use delta backups check box. If you do not use a delta backup for the recovery option, the software only uses the log backups for recovery.
To send a notification email when the restore job completes, select the When the job completes, notify me via email.
The software restores the SYSTEMDB database to the specified location.
If you did not select the Initialize Log area 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:  recovery could not be completed, volume 1, reached log position 0,  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>
hdbsql -U BACKUPM
On the command line, type the following command:
hdbsql SYSTEMDB=> alter system start database <Tenant_Database_Name>
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.