Symantec NetBackup status code 71 to status code 75
Symantec NetBackup product is a backup and recovery product designed for enterprise users. Symantec NetBackup tool can be used to perform backups of SQL Server databases and provides various features.
Below are some of the NetBackup status error codes from Status Code 71 to Status Code 75 which may be received while using the Symantec NetBackup tool.
NetBackup status code: 71
Message: none of the files in the file list exist
Explanation: The files in the file list did not match any of the files on the client.
This error can occur with only one file in the file list and the file cannot be backed
up due to an I/O error.
Recommended Action: Do the following, as appropriate:
Verify that the correct file list is specified for this client.
On Windows clients, verify that the account used to start the NetBackup Client
service has read access to the files.
If you back up a network drive or a UNC (universal naming convention) path,
do the following: use the Services application in the Windows Control Panel
to verify that the NetBackup Client service does not start under the SYSTEM
account. The SYSTEM account cannot access network drives.
To back up network drives or UNC paths: change the NetBackup Client service
startup to log in as a user that has permission to access network drives.
Check the All Log Entries report for clues.
NetBackup status code: 72
Message: the client type is incorrect in the configuration database
Explanation: The policy type attribute in the policy configuration indicates that
the client is one type, but the installed software is for another type.
Recommended Action: Verify that the policy type attribute for the policy is
NetBackup status code: 73
Message: bpstart_notify failed
Explanation: The bpstart_notify script returned a nonzero exit code.
Recommended Action: Check the bpstart_notify script on the client to see if
it performs as expected.
NetBackup status code: 74
Message: client timed out waiting for bpstart_notify to complete
Explanation: The bpstart_notify script on the client takes too long.
Recommended Action: Try to speed up the bpstart_notify script or set the
BPSTART_TIMEOUT on the server to a value that is larger than the default. Set
BPSTART_TIMEOUT in the bp.conf file on a UNIX or Linux NetBackup server.
On a Windows NetBackup server, use Host Properties to set Backup Start Notify
See “Using the Host Properties window to access configuration settings” in the
NetBackup status code: 75
Message: client timed out waiting for bpend_notify to complete
Explanation: The bpend_notify script on the client takes too long.
Recommended Action: Try to speed up the bpend_notify script or
setBPEND_TIMEOUT on the server to a value that is larger than the default. Set
BPEND_TIMEOUT in the bp.conf file on a UNIX or Linux NetBackup server. On
a Windows NetBackup server, use Host Properties to set Backup End Notify
Hope this was helpful.
In-Depth Blogs on SQL Server, Information about NetBackup status codes, SQL Server Frequently asked questions, SQL Server Trainings.