About the NetBackup Discovery Service
The NetBackup Discovery Service (nbdisco) discovers Oracle database instances throughout the NetBackup environment. The discovery service reports to the master server when it finds instances of applications to help you build an Oracle Intelligent Policy. The service polls the clients upon NetBackup installation and periodically after installation (every 4 hours). Instance management collects the discovered instances in an instance repository. The user can access this repository on the NetBackup Administration Console or by using the nboraadm command.
By default, this service is enabled to report instances. However, you can use the REPORT_CLIENT_DISCOVERIES client configuration entry to shut down or restart the service on a particular client. By default, REPORT_CLIENT_DISCOVERIES is not present in the Windows registry or the UNIX bp.conf file.
The NetBackup Discovery Service searches for instances and databases in different areas where Oracle is installed. The following areas are where the Discovery Service searches:
Non-RAC Single instances 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) in the Oracle Clusterware high availability API.
To change the default setting, use bpsetconfig to add or change the entry:
In the Windows registry.
In the
/usr/openv/netbackup/bp.conffile on UNIX.
Use the following format: REPORT_CLIENT_DISCOVERIES = TRUE | FALSE
Set REPORT_CLIENT_DISCOVERIES to FALSE to shut down the discovery service. The service shuts down within 10 minutes and remains down on the client. To turn on the discovery service on that client, set REPORT_CLIENT_DISCOVERIES to TRUE or remove the entire entry. Then run bp.start_all on the client to restart the service.
To set this value on a client remotely, run the following command from the master server:
echo REPORT_CLIENT_DISCOVERIES=FALSE | bpsetconfig -h clientname