Backup failure scenarios
Backup jobs can fail when the value for the storage unit (STU) is lower than the defined in a dynamic multi‑streaming standard policy.
This issue is most commonly associated with the Error code 5576.
In the section, you may see errors similar to the following:
Feb 10, 2026 5:33:49 PM - Error nbjm (pid=136759): NetBackup status 5576. The storage unit Maximum concurrent jobs setting is lower than the number of job streams specified in the policy configuration.
Workaround:
Configure the setting for the storage unit used in dynamic multi‑streaming backups so that it is greater than or equal to the number of streams specified in the policy configuration.
Example log entries:
db_send_FILES_LIST failed: network read failed (42)
db_send_FILES_LIST failed: a protocol error has occurred (232)
To resolve NetBackup backup job failures with status 42 (network read failed) or 232 (protocol error) related to the db_send_FILES_LIST, disable catalog optimization on the primary server. Add the following entry to bp.conf file:
ENABLE_CATALOG_OPTIMIZATION = NO
Partial backup failures can cause several issues. For example, if a backup job uses 10 streams and only 3 streams complete successfully while the remaining 7 are still running when the job fails, the resulting backup is incomplete. In this scenario, NetBackup saves only the data from the completed streams.
Workaround:
These incomplete backups cannot restore the entire dataset for the intended recovery point. As a result, NetBackup administrators must manually expire these backup images. Retaining partial backups can be misleading because they do not represent a complete backup and are not suitable for recovery purposes.