Symantec NetBackup status code 76 to status code 80


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 76 to Status Code 80 which may be received while using the Symantec NetBackup tool.

NetBackup status code: 76
Message: client timed out reading file
Explanation: A fifo was specified in the file list and no data was produced on the
fifo within the allotted time.
RecommendedAction: Make sure that the process that is to produce the data on
the named fifo is started correctly. Add an entry to the
/usr/openv/netbackup/bp.conf file on the server to setCLIENT_READ_TIMEOUT
to a larger value than the default.

NetBackup status code: 77
Message: execution of the specified system command returned a nonzero status
Explanation: An immediate command returned a nonzero status.
Recommended Action: Do the following, as appropriate:
Verify that the command is specified correctly.
For NetBackup Snapshot Client only, do the following:
The policy file list may contain the files that do not reside within a file system
that was designated as the snapshot source. To apply a snapshot method to
the backup of individual files, the snapshot source must be a file system. (It
cannot be a raw partition or Volume Manager volume.) The files in the policy
file list must reside within that file system.
Run the command manually to see if the wanted result is produced.
For detailed troubleshooting information, set up debug logging, as follows:
On UNIX, Linux, and Windows clients, create a debug log directory for
On other PC clients except Macintosh, create a debug log directory for bpcd
(the bpcd log is created automatically on Macintosh).
Increase the amount of information that appears in the logs.
See “Changing the logging level on Windows and NetWare clients” in the
Troubleshooting Guide.
Retry the operation and check the resulting debug log.

NetBackup status code: 78
Message: afs/dfs command failed
Explanation: Indicates an AFS vos command failure.
Recommended Action: Do the following, as appropriate:
Check the NetBackup Problems Report for additional information on why the
command failed.
The bpbkar debug log shows the command that was run. Create a debug log
directory for bpbkar. Retry the operation and retry the resulting debug log.
Try running the vos command manually to duplicate the problem.

NetBackup status code: 79
Message: unsupported image format for the requested database query
Explanation: One or more of the images to be synthesized was encrypted. These
images cannot be synthesized.
Recommended Action: Ensure that none of the images was encrypted.

NetBackup status code: 80
Message: Media Manager device daemon (ltid) is not active
Explanation: If the server is UNIX or Linux, the NetBackup device manager
daemon, ltid, is not running. If the server is Windows, the NetBackup Device
Manager service is not running.
Recommended Action: Do the following, as appropriate:
On Windows, use the Activity Monitor or the Services application in the
Windows Control Panel to see if the NetBackup Device Manager service is
running. If it is not running, start it. To enable verbose logging, place VERBOSE
on a line by itself in the install_path\Volmgr\vm.conf file before you start
the service.
On UNIX and Linux, use vmps to see if ltid is running and if necessary start
ltid in verbose mode with the following command:
/usr/openv/volmgr/bin/ltid -v
Or, add a VERBOSE entry to the /usr/openv/volmgr/vm.conf file. Create the
vm.conf file if necessary.
On UNIX and Linux, check the system logs to verify that ltid starts.

Hope this was helpful.

SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup status codes, SQL Server Frequently asked questions, SQL Server Trainings.


Leave a Reply

Your email address will not be published. Required fields are marked *