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: 83
Explanation: The tape manager (bptm) or disk manager (bpdm) did not open the device or file that the backup or restore must use.
Recommended Action: For additional information, check the following:
NetBackup Problems report
Event Viewer Application log (Windows)
System log (UNIX)
Typically, this status code indicates a drive configuration problem that allows more than one process at a time to open the device. On UNIX, the problem may be due one or more of the following:
Two (or more) devices were configured that are the same physical device (for different densities perhaps). Verify that none of the
/dev
files that were used for these devices have the same major or minor numbers.Links exist in the file system that allows users access to the drives.
The configuration for the drives was modified (in the administrator interface or
vm.conf
) and the Media Manager device daemon, ltid, was not restarted. Verify the configuration and then start ltid.
On Windows, the problem may be that the Media and Device Management device configuration was modified but the NetBackup Device Manager service was not restarted. Verify the configuration and restart the NetBackup Device Manager service.
On Windows, make sure that the tapes are not write protected.
For detailed troubleshooting information:
Create a debug log directory for bpdm (if the device is disk) or bptm (if the device is tape).
On UNIX, restartltid in the verbose mode by running the following:
/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 Windows, to enable verbose logging, add VERBOSE on a line by itself in the
install_path\Volmgr\vm.conf
file. Then, stop and restart the NetBackup Device Manager service.Retry the operation and check the resulting debug log files.
On Windows systems, look at the
install_path\VERITAS\NetBackup\db\media\errors
log for a drive that frequently produces errors.On UNIX systems, look at the
/usr/openv/netbackup/db/media/errors
log (which is also included in the/usr/openv/netbackup/bin/goodies/support/support
script output) for a drive that frequently produces errors.
Click here to view technical notes and other information in the Veritas Knowledge Base about this status code.