About Oracle discovery
In the NetBackup web UI, the Databases tab in the node contains the databases that NetBackup discovers and any databases that are added manually.
The NetBackup Discovery Service (nbdisco) discovers Oracle database instances throughout the NetBackup environment and collects the databases in a database repository. The user can access this repository with the NetBackup web UI, the nboracmd command, or the NetBackup APIs.
The Discovery Service reports to the primary server when it finds databases. It polls the clients upon NetBackup installation and periodically after installation (every 8 hours). By default, this service is enabled to report databases. You can also configure discovery of clients. The polling interval can be configured with the setting ORACLE_ASSET_INTERVAL on the primary server. On a periodic basis as a part of standard image cleanup activities, NetBackup removes any unregistered databases that were discovered more than 30 days ago.
See Configure discovery of Oracle clients.
See the NetBackup Administrator's Guide, Volume I.
The NetBackup Discovery Service searches for databases in different areas where Oracle is installed. The following areas are where the Discovery Service searches:
Non-RAC databases are discovered by searching the
oratabfile on UNIX and from the registry on Windows.NetBackup looks for the Oracle health check files that are found in the Oracle home. These are not cleaned up when a database is deleted. You may need to delete them manually otherwise NetBackup can continue to find the databases that are deleted.
Oracle RAC databases are discovered when NetBackup queries the Oracle Cluster Ready Services (CRS) using the Oracle Clusterware high availability API.
Oracle RAC in the web UI does not support upgrades from legacy script-based policies. Also, there is no web UI support for the configurations that are created using Appendix A: Deduplication best practices or Appendix B: Snapshot Client support of SFRAC.
To allow the NetBackup web UI to discover a RAC instance or cluster:
Remove the Oracle RAC from any configuration that is setup using Appendix A: Deduplication best practices or Appendix B: Snapshot Client support of SFRAC.
Remove any Oracle RAC from any existing OIP policies.
Note:
When an Oracle RAC database is discovered, that database does not have a Database ID. A Database ID is required to manually add additional RAC instances to the database. You must register the RAC database and provide a Database ID before adding additional instances.