NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

Status Codes
NetBackup 4.5 Troubleshooting Guide for Windows
4. For detailed troubleshooting information, set up debug logging:
a. On UNIX and Windows clients, create a debug log directory for bpbkar.
b. On other PC clients except Macintosh, create a debug log directory for bpcd (the
bpcd log is created automatically on Macintosh).
To increase the amount of information that appears in the logs, see the logging
topics in Chapter 3.
c. 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:
1. Check the NetBackup Problems Report for additional information on why the
command failed.
2. The bpbkar debug log shows the command that was executed. Create a debug log
directory for bpbkar. Retry the operation and retry the resulting debug log.
3. Try executing the vos command manually to duplicate the problem.
NetBackup Status Code: 80
Message: Media Manager device daemon (ltid) is not active
Explanation: The NetBackup Device Manager service is not running.
Recommended Action:
1. 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 starting the service.
Note The NetBackup Device Manager service is used only if devices are attached to the
system.
NetBackup Status Code: 81
Message: Media Manager volume daemon (vmd) is not active
98 NetBackup Troubleshooting Guide - Windows NT/2000
NetBackup 4.5 Troubleshooting Guide for Windows