Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. Veritas NetBackup™ for Microsoft SQL Server Administrator's Guide
  3. Managing SQL Server objects for use with SQL Server Intelligent Policies
  4. About discovery of SQL Server objects
Veritas NetBackup™ for Microsoft SQL Server Administrator's Guide

About discovery of SQL Server objects

discovery runs regularly and gathers information for instances and for advanced and basic availability groups in your environment. (Read-scale availability groups must be discovered manually.) The data expires after one hour. The Discovery Service (nbdisco) runs "shallow" discovery every 8 hours for instances and availability groups on the clients for that master server. The Agent Request Service (NBARS) polls the master server every 5 minutes for any non-expired data.

Deep discovery includes discovery of databases and is performed in the following circumstances:

  • After a full backup, an incremental backup, or a restore occurs

    The client sends details when database data is changed and not more than every 15 minutes.

  • When you run a manual discovery of databases or availability groups

  • After you add credentials for the instances or replicas

By default, this service reports to the master server when it finds SQL Server instances. However, the user can turn off discovery for a specific client, with the bpsetconfig utility. See the REPORT_CLIENT_DISCOVERIES option in the Administrator's Guide, Volume I.

The client maintains a cache file NB_instancename_cache_v1.0.dat in the NetBackup\dbext\mssql directory for each instance. The file can be deleted and recreates it after the next full backup when deep discovery data is sent again.

To discover the instances that you created since the last discovery, select Actions > Discover Instances. To update an AG with any new instances, select the AG and choose Actions > Rescan Availability Group.

Feedback

Was this page helpful?
Previous

About the Applications utility

Next

Discovering instances on demand

Feedback

Was this page helpful?