Skip to main content
Discover databases
Updated over a week ago

Enterprise Workloads Editions: βœ… Business | βœ… Enterprise | βœ… Elite

Druva provides an intelligent database discovery mechanism that allows you to discover databases running on the Oracle Server host. With Druva, the databases can be discovered using the following ways at various stages:

With the discovery mechanism, Druva fetches details of the following database types running on the Oracle Server hosts:

  • Container databases (CDB)

  • Pluggable databases (PDB) for each container database

  • Standalone database

  • RAC databases

  • Standby database (Physical)

The following video illustrates the process.

Automatic discovery

When you register an Oracle Server host with Druva and activate the Hybrid Workloads agent on the host, Druva automatically discovers databases running on the registered Oracle Server host and lists all the databases on the Databases page. The database discovery gives cloud administrators insight into the Oracle databases that are currently protected and the ones that need attention.


πŸ“ Note
​In case of disaster recovery, make sure that you re-register a node instead of registering it as a new server. If you register the already registered RAC node as a new server, the database and cluster details are not updated on the server and the database is not discovered. As a result, you will not be able to perform backup using this newly registered node.


Along with the discovered databases, Druva also lists details of the databases, such as the database type, the server name on which the database is hosted, the archive log, the status of the connection with Druva, and the status of configuration. It also gives an option to authenticate the database.

Periodic discovery

Druva triggers discovery periodically on the registered Oracle Server hosts and lists the discovered databases on the Management Console. This discovery operation fetches any databases added to the server host after the host was registered with Druva.

On-demand discovery

Druva also allows you to discover any databases that were added to the Oracle Server host after its registration with Druva and the periodic discovery has not triggered yet. When you add a database and its credentials manually to the Oracle Server, the on-demand discovery feature fetches details of the newly added databases to the host and lists the databases on the Databases page.

Procedure

  1. Log in to the Management Console.

  2. Click Oracle > Direct to cloud from the Protect menu. Note that if the All Organizations menu is enabled, you have to first select an organization and then click Oracle > Direct to Cloud.
    The Oracle Servers page opens.

  3. In the Server Name column select the server, click the following icon, and then click Discover Databases:

  4. Click Yes to proceed with database discovery.

Druva lists the discovered databases on the Databases page.

The following table summarizes the discovery mechanisms that Druva provides.

Discovery Type

Action

Druva Behavior

Automatic discovery

Administrator registers Oracle Server host and activates the Hybrid Workloads agent on the host.

Druva discovers all the databases running on the Oracle Server host and lists them on the Databases page.

Periodic discovery

Druva runs periodic discovery on the registered Oracle Server host.

Druva discovers databases that were either skipped from the Automatic discovery or 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 Oracle Server host and triggers the on-demand discovery.

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


❗ Important

To configure these databases for backup, you must authenticate each database. For more information, see Authenticate a database.


After you authenticate databases, Druva populates database details on the Databases page. The details include database type, Oracle server that is added to, database version, archive log, authentication type, connection status with Druva, and the database size.

Did this answer your question?