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. NetBackup™ for Microsoft SQL Server Administrator's Guide
  3. Performance and troubleshooting
  4. Intelligent group backup completes with a status code 1 when database not found in the SQL Server environment
NetBackup™ for Microsoft SQL Server Administrator's Guide

Intelligent group backup completes with a status code 1 when database not found in the SQL Server environment

NetBackup maintains a list of SQL Server databases in its asset database. Consider a situation where a SQL Server database exists in the NetBackup asset database but not in the live SQL Server environment. In that case, when NetBackup performs an intelligent group backup that contains that database, logs a message, and reports a status code 1:

08:31:05.561 [5736.15584] <2> debuglog: <16> bphdb do_script: 
ERR - exit status: 5465 Could not find database objects during backup.

08:31:05.561 [5736.15584] <2> debuglog: <16> bphdb do_script: 
INF - Partial success status so switch status from <5465> to <1>

On the Databases tab, NetBackup indicates the Database state as Deleted for that database. To resolve this issue you can do one of the following:

  • Review the intelligent group in the policy and adjust the query.

  • Run the backup job again. NetBackup then marks the database as inactive.

  • If the database is now available, perform discovery.

Feedback

Was this page helpful?
Previous

SQL Server log truncation failure during VMware backups of SQL Server

Next

Set the maximum trace level for NetBackup for SQL Server

Feedback

Was this page helpful?