Skip to main content

How can we help you?

Druva Documentation

Restore a database to a different SAP HANA System

Overview

Using Enterprise Workloads for SAP HANA, you can restore a backup to a different SAP HANA system.

Apart from the direct benefit of disaster recovery, you can also use this feature to create database copies.  This capability is particularly useful for creating cloned databases for training, testing, or development scenarios.

Copying a database using a backup facilitates the effortless creation of multiple database instances on demand, enhancing operational agility and minimizing downtime risks. You can copy a system database or tenant databases within the same system or another system using backup and recovery. Even though you can use only complete data backup for copying, you can also use delta backups (differential or incremental backups) and log backups to copy your database to a specific point in time.

Considerations

  • System ID (SID): The SID should be different and unique for the source and destination in the same Enterprise Workloads organization.

  • Tenant Name: The tenant name can be the same or different between the source and destination.

  • Software Version: The source and destination systems should have the same HANA and Backint versions.

  • Backup Configuration: Both the databases (source and destination) should be configured for backup. For more information, refer to Configure SAP HANA databases for backup.

  • Number of Index Servers: The number of index servers in the source and destination databases should be the same.

  • Backups: Previous backups are still linked to the old database. If you need to restore those backups, do not remove these from Druva.

For detailed information, see Prerequisites for the Target Database and Prerequisites for the Source Database in the SAP HANA Administration Guide for SAP HANA Platform.

Copying a tenant database

Copying a tenant database involves the following steps:

  1. Register the Destination System: Begin by registering the destination server with Enterprise Workloads. For more information, see Register SAP HANA Systems.

  2. Create an Empty Tenant Database: Create an empty tenant database at the destination. 

  3. Run Deep Discovery: Execute a deep discovery operation on the destination system. For more information, see Discover databases. 

  4. Configure New Tenant for Backup: For more information, see Configure SAP HANA databases for backup

  5. Initiate Database Copy: Use SAP HANA Tools such as Cockpit at the destination system to initiate the copying of the tenant database. For more information on this process, see SAP HANA’s Guide on Copying a Database Using Backup and Recovery.

Copying a system database

Copying a system database involves the following steps:

  1. Register the Destination System: As with the tenant database, start by registering the destination server with Enterprise Workloads. For more information, see Register SAP HANA Systems.

  2. Run Deep Discovery: Carry out a deep discovery operation on the destination server. For more information, see Discover databases.

  3. Configure the System Database for Backup: Configure the system database for backup. For more information, see Configure SAP HANA databases for backup

  4. Initiate Database Copy: Use SAP HANA Tools, such as Cockpit, at the destination system to initiate the copying of the system database. For more information, refer to "Copying a Database Using Backup and Recovery." 

  5. Copy Every Tenant: Repeat the steps outlined in the previous section to copy each tenant database from the source system.

  • Was this article helpful?