
General Test and Troubleshooting Procedures
20 NetBackup Troubleshooting Guide - UNIX
5. If you previously configured a nonrobotic drive and your system includes a robot,
change your test class now to specify a robot. Add a volume to the robot. The volume
must be in the NetBackup volume pool on the volume database host for the robot.
Repeat this procedure starting with step 3, but this time for the robot. This verifies
that Media Manager can find the volume, mount it, and use the robotic drive.
If you have difficulties with the robot, 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. Add a user schedule to your test class (the backup window must be open while you
are testing). Use a storage unit and media that has been verified in previous steps.
7. Start a user backup and restore of a file by using the client-user interface on the master
server. Monitor the progress log for the operation. If successful, this operation verifies
that client software is functional on the master server.
If a failure occurs, check the NetBackup All Log Entries report. To further isolate the
problem, check the appropriate activity logs from those listed below. Chapter 3
explains which logs apply to specific client software.
Note These logs exist only if you enabled activity logging in step 1. On a UNIX system,
the activity logs are in the /usr/openv/netbackup/logs/ directory. On a
Windows NT/2000 system, the activity logs are in the
install_path\NetBackup\logs\directory.
◆ bparchive
◆ bpbackup
◆ bpbkar
◆ bpcd
◆ bplist
◆ bprd
◆ bprestore
◆ nbwin (Windows only)
◆ bpinetd (Windows NT/2000 only)
Comentarios a estos manuales