
Chapter 2, Troubleshooting Procedures 19
General Test and Troubleshooting Procedures
3. Verify that the NetBackup daemons are running on the master server:
◆ To check the daemons on a UNIX system, execute:
/usr/openv/netbackup/bin/bpps -a
◆ To check the services on a Windows NT/2000 system, use the NetBackup Activity
Monitor or the Services application in the Windows NT/2000 Control Panel.
4. Start a manual backup of a class by using the manual backup option in the NetBackup
administration interface. Then, restore the backup.
This verifies:
◆ NetBackup server software is functional, including all daemons, programs, and
databases.
◆ Media Manager can mount the media and use the drive you configured.
If a failure occurs, first check the NetBackup All Log Entries report. For failures
relating to drives or media, verify that the drive is in an UP state and the hardware is
functioning.
To further isolate the problem, use the activity and debug logs. Appendix A explains
the basic sequence of events (log messages are more detailed than the information in
that appendix).
If the activity logs do not reveal the problem, check the following:
◆ System logs
◆ Event Viewer Application logs (Windows NT/2000)
◆ vmd debug logs on the volume database host for the device
◆ bptm 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 NetBackup server, you can verify only the Media Manager part of the
configuration, by using the tpreq command to request a media mount and then
assigning the drive. If this works, the problem is probably with the class or storage
unit configuration. When you are done, don’t forget to tpunmount the media.
Comentarios a estos manuales