Veritas NetBackup™ Status Codes Reference Guide
- NetBackup status codes
- NetBackup status codes
- NetBackup KMS status codes
- NetBackup status codes
- Media Manager status codes
- Media Manager status codes
- Media Manager status codes
- Device configuration status codes
- Device configuration status codes
- Device configuration status codes
- Device management status codes
- Device management status codes
- Device management status codes
- Robotic status codes
- Robotic status codes
- Robotic status codes
- Robotic error codes
- Robotic error codes
- Robotic error codes
- Security services status codes
- Security services status codes
- Security services status codes
- NetBackup alert notification status codes
NetBackup status code: 80
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, 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 thevm.conf
file if necessary.On UNIX, check the system logs to verify that ltid starts.
Note:
On UNIX systems, ltid, and on Windows systems, the NetBackup Device Manager service, is used only if devices are attached to the system.
Click here to view technical notes and other information in the Veritas Knowledge Base about this status code.