Troubleshooting guide

Troubleshooting Installation and Configuration Problems
14 NetBackup Troubleshooting Guide - UNIX
1. Check for the following device configuration problems:
◆ Configuration for robotic drive does not specify the robot.
◆ Drive is configured as wrong type or density.
◆ Incorrect Robotic Drive Number.
◆ SCSI ID for the robotic control is specified instead of the logical Robot Number
assigned to the robot.
◆ The same robot number is used for different robots.
◆ SCSI ID for the drive is specified instead of a unique Drive Index number.
◆ A platform does not support a device or was not configured to recognize it.
◆ Robotic device is not configured to use LUN 1, which is required by some robot
hardware.
◆ On UNIX, drive no-rewind device path is specified as a rewind path.
◆ On UNIX, tape devices are not configured with “Berkeley style close.”
This is configurable on some platforms and is required by NetBackup (see the
Media Manager Device Configuration Guide for more information).
◆ On UNIX, tape devices (other than QIC) are not configured as “variable mode.”
This is configurable on some platforms and is required by NetBackup.
When this condition exists, you can frequently perform backups but not restores.
“Status Code: 174” on page 144 provides further explanation. Also see the Media
Manager Device Configuration Guide.
2. Check for the following problems with the daemons:
◆ Daemons do not start during reboot (configure system so this occurs).
◆ Wrong daemons are started (problems with media server start up scripts).
◆ Configuration was changed while daemons were running.
◆ On Windows NT/2000, the
%SystemRoot%\System32\drivers\etc\services file does not have an
entry for vmd, bprd, bpdbm and bpcd. Also, ensure there are entries for the
processes for configured robots (see the Media Manager System Administrator’s
Guide - Windows NT/2000 for a list of these processes).
◆ On UNIX, the /etc/services file (or NIS or DNS) does not have an entry for
vmd, bprd, bpdbm, or robotic daemons.
3. If you found and corrected any configuration problems, retry the operation and check
for NetBackup status codes or messages.