Skip to main content


 

 

How can we help you?

 

Druva Documentation

Discover databases

Better Help Ahead

Redirecting to our improved help portal. If you're not redirected, click here.

Enterprise Workloads Editions: File:/tick.png Business File:/cross.png Enterprise File:/tick.png Elite

Hybrid Workloads for SAP HANA provides an intelligent database discovery mechanism to discover databases running on the SAP HANA host. Hybrid Workloads for SAP HANA can discover the databases using the following ways at various stages:

  • Automatic discovery

  • Periodic discovery

  • On-demand discovery

With the discovery mechanism,  Hybrid Workloads agent fetches details of the following database types running on the SAP HANA nodes:

  • SYSTEMDB Database

  • Tenant Database

Automatic discovery 

The automatic discovery process discovers all the systems when you install and activate the Hybrid Workloads agent on a node. After that, when you assign credentials to register that system, the automatic discovery process discovers the databases on that system.

The database discovery gives cloud administrators insight into the SAP HANA databases that are currently protected and the ones that need attention. 

Along with the discovered databases, Hybrid Workloads for SAP HANA also lists details of the databases, such as the following:

  • Database name

  • SAP HANA system (SID) that this database belongs to

  • Number of Nodes on which this database is located, along with the number of nodes registered and unregistered with Druva. Note that all the nodes should be registered for backup.

  • Database size

  • Configuration status

The automated discovery runs only once when in the above-described conditions. 

Periodic discovery 

Hybrid Workloads for SAP HANA triggers discovery periodically on the registered SAP HANA hosts and lists the discovered databases on the Management Console. This discovery operation fetches any databases added to the system after the system was last discovered.

The results of periodic discovery are the same as automatic discovery. The only difference is that automatic discovery runs only once, while periodic discovery runs multiple times daily.

If you do not want to wait for the new changes to reflect, such as addition or deletion or a new node addition or deletion of a new database, you can run an on-demand discovery.

On-demand discovery 

Hybrid Workloads for SAP HANA also lets you discover any new databases you add to the SAP HANA host. This process lets you discover the database immediately without waiting for the periodic discovery to run.

Prerequisites

You must register the nodes that host the SAP HANA system. See Register SAP HANA Systems for more details.

Procedure 

  1. Log in to the Management Console.

  2. Click Protect > SAP HANA. If the All Organizations menu is enabled, select an organization and click Protect > SAP HANA.

  3. Locate the SAP HANA system you want to run discovery for, click the more icon, and then click Discover Databases.

disover_database.jpg

  1. Click Yes to proceed with database discovery. You will see a list of the discovered databases on the Databases page. 

Required privileges

For discovery to run successfully, the minimum privileges required for the database user are as follows:

  • System privilege: DATA ADMIN 

  • Object privilege: SELECT privilege on _SYS_XS_schema

Comparison of discovery mechanisms

The following table summarizes the discovery mechanisms that Hybrid Workloads for SAP HANA provides. 

Discovery Type

Action

Behavior

Automatic discovery

Administrator registers the SAP HANA host and activates the Hybrid Workloads agent on the host.

Druva discovers all the databases on the SAP HANA host and lists them on the Databases page.

Periodic discovery

Druva runs periodic discovery on the registered SAP HANA host.

Druva discovers databases that were added after the automatic discovery was completed and lists them on the Databases page.

On-demand discovery

Administrator manually adds a new database to the registered SAP HANA host and triggers the on-demand discovery.

Druva discovers the newly added database and lists it on the Databases page.