Troubleshooting guide

Chapter 2, Troubleshooting Procedures 23
General Test and Troubleshooting Procedures
◆ On a Windows NT/2000 server, the Event Viewer Application log
◆ vmd debug logs
See the vendor manuals for information on hardware failures.
If you are using a robot and this is an initial configuration, verify that the robotic drive
is configured correctly. In particular, verify that:
◆ The same robot number is used both in the Media Manager and storage unit
configurations.
◆ Each robot has a unique robot number.
On a UNIX system, you can verify only the Media Manager part of the configuration,
by using the tpreq command to request a media mount and then assign the drive.
Perform these steps from the media server. If this works, then the problem is probably
with the class or storage unit configuration on the media server or communications
between the master and media server. When you are done, tpunmount the media.
5. If you previously configured a nonrobotic drive and a robot attached to your media
server, change the test class to name the robot. Also, add a volume for the robot to the
volume database host for the robot. Verify that the volume is in the NetBackup
volume pool and in the robot.
Then, repeat this procedure starting with step 3, this time for a robot. This verifies that
Media Manager can find the volume, mount it, and use the robotic drive.
If a failure occurs, check the NetBackup All Log Entries report. Look for errors
relating to devices or media. If the All Log Entries report doesn’t help, check:
◆ UNIX system logs on the media server
◆ vmd debug logs on the volume database host for the robot
◆ On a Windows NT/2000 system, the Event Viewer Application log
In an initial configuration, verify that the robotic drive is configured correctly. Do not
use a robot number that is already configured on another server.
Try the test utilities described in Appendix C.
Note Do not use the Robotic Test Utilities when backups or restores are active. These
utilities prevent the corresponding robotic processes from performing robotic
actions, such as loading and unloading media. This can cause media mount
timeouts.
6. When the test class operates satisfactorily, repeat specific steps as necessary to verify
other clients and storage units.