Loading...

HDBSettings.sh Example: Performing SAP HANA 1.0 SYSTEMDB Restores for Disaster Recovery

Use this procedure when you need to perform a disaster recovery restore on a SAP HANA 1.0 Multitenant Database Container Database.

The following conditions apply to this procedure:

  • The SID on the destination database can be the same as, or different from the source database.
  • When you restore the SYSTEMDB, the destination database must be a SYSTEMDB.
  • When you restore the tenant databases, the destination must be a tenant database that has the same name as the source database.
  • You can only recover the SYSTEMDB to the latest backup because that is the only option SAP HAN 1.0 supports.

Note: You must restore the SYSTEMDB and all tenant databases.

SYSTEMDB Restore

Before You Begin

  1. Make sure that you have the following information:
    • The source instance SID name
    • The SAP HANA source physical client name
  2. Update the SAP HANA parameter file with the following entries:

    For more information, see Creating the SAP HANA Parameter File.

    • srcCrossClient - This is the source physical client name.
    • srcCrossDbName - This is the source database name.
  3. Stop the SAP HANA destination server. On the command line, type the following command:

    Note: If the database is a multinode database, then you must run this command on all nodes.

    HANA stop

Procedure

  • Recover to the most recent backup. On the command line, type the following command substituting the timestamp that is in the future and the source SID (in this example, W02).

    Note: If the source SID and the destination SID match, then you do not need the "USING SOURCE SID" phrase in the commands.

    HDBSettings.sh recoverSys.py --command= " RECOVER DATABASE UNTIL TIMESTAMP '2018-10-27 21:01:47' CLEAR LOG USING SOURCE 'W02' CHECK ACCESS USING BACKINT " --wait --timeout=600

What to Do Next

Recover the tenant databases. For more information, see HDBSQL Example: Recovering the SAP HANA 1.0 Tenant Databases for a Disaster Recovery.

Last modified: 2/26/2018 3:10:21 PM