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. Performance and troubleshooting
  4. Reporting of unsuccessful filegroup or file backups
Veritas NetBackup™ for Microsoft SQL Server Administrator's Guide

Reporting of unsuccessful filegroup or file backups

If you select specific databases and specific filegroups or files in a backup policy, NetBackup reports any unsuccessful filegroup or file backups differently than if you select an entire instance (DATABASE $ALL). Consider the following scenarios:

  • Scenario 1 - For SQLINSTANCE1 (DATABASE $ALL or all the databases), back up the filegroups FG1, FG2, and FG3. If NetBackup cannot back up FG1, FG2, or FG3, NetBackup skips the backup of the filegroup for that database. The parent job completes with a status 0.

  • Scenario 2 - For DATABASEA and DATABASEC in SQLINSTANCE1, back up the filegroups FG1, FG2, and FG3. If NetBackup cannot back up any of these filegroups for DATABASEA or DATABASEC, the parent job completes with a status 2. The job details indicate that one or more of the filegroups that you selected were not backed up.

Feedback

Was this page helpful?
Previous

Troubleshooting credential validation

Next

About minimizing timeout failures on large SQL Server database restores

Feedback

Was this page helpful?