NetBackup Troubleshooting Guide - Zedat

Preliminary Troubleshooting
/usr/openv/netbackup/bin/nbjm
/usr/openv/netbackup/bin/nbpem
If both nbjm and nbpem are not running, they must be started in the above
sequence. If only one is not running, start it using the above command.
c. If either the NetBackup request daemon (bprd) or database manager daemon
(bpdbm) are not running, execute this command to start them:
/usr/openv/netbackup/bin/initbprd
d. If any of the following media and device management processes are not running:
◆ ltid (device; ltid only needs to be running if drives are configured on the
server)
◆ vmd (volume)
◆ avrd (automatic volume recognition)
◆ processes for all configured robots
Stop the device daemon, ltid, by executing:
/usr/openv/volmgr/bin/stopltid
Verify that the ltid, avrd, and robotic control daemons have been stopped by
executing:
/usr/openv/volmgr/bin/vmps
Note If you are using ACS robotic control, the acsssi and acssel processes will
remain running when ltid is stopped. For more information about stopping
these daemons, refer to the Automated Cartridge System (ACS) Appendix in
the NetBackup Media Manager System Administrator’s Guide.
Stop any robot control daemons that remain running when ltid is terminated.
Then, start all daemons by executing:
/usr/openv/volmgr/bin/ltid
For debugging, it is best to start ltid with the -v (verbose) option.
On Windows NetBackup servers
a. The following services must be running. If these services are not running, start
them using the NetBackup Activity Monitor, or using the Services application in
the Windows Control Panel:
Note To start all of them, execute install_path\NetBackup\bin\bpup.exe.
12 NetBackup Troubleshooting Guide