Search <book_title>...

Veritas NetBackup™ Troubleshooting Guide

Last Published: 2019-07-01

Product(s): NetBackup (8.2)

Verifying that all processes are running on UNIX servers

For NetBackup to operate properly, the correct set of processes (daemons) must be running on your UNIX servers. This procedure determines which processes are running and shows how to start the processes that may not be running.

To verify that all processes are running on UNIX servers

To see the list of processes (daemons) running on the master server and on the media server, enter the following command:
```
/usr/openv/netbackup/bin/bpps -x
```

Ensure that the following processes are running on the NetBackup servers:

Master server

bpcd -standalone
bpcompatd
bpdbm
bpjobd
bprd
java
nbars
nbatd
nbdisco (discovery manager)
nbemm
nbevtmgr
nbim (index manager)
nbjm

nbpem
nbproxy
nbrb
nbrmms
nbsl
nbstserv
nbsvcmon
nbwmc
NB_dbsrv
pbx_exchange
vmd
vnetd -standalone

Media server

avrd (automatic volume recognition, only if drives are configured 
on the server)
bpcd  - standalone
bpcompatd
ltid  (needed only if tape devices are configured on the server)
mtstrmd (if the system has data deduplication configured)
nbrmms
nbsl
nbsvcmon
pbx_exchange
spad (if the system has data deduplication configured)
spoold (if the system has data deduplication configured)
vmd  (volume)
vnetd  - standalone
Any tape or robotic processes, such as tldd, tldcd

Note:

Additional processes may also need to be running if other add-on products, database agents, and so forth are installed. For additional assistance, see https://www.veritas.com/support/en_US/article.100002166.

If either the NetBackup request daemon (bprd) or database manager daemon (bpdbm) is not running, start them by entering the following command:
```
/usr/openv/netbackup/bin/initbprd
```
If the NetBackup Web Management Console (nbwmc) is not running, start it with the following command:
```
/usr/openv/netbackup/bin/nbwmc
```
If any of the media server processes are not running, stop the device process ltid by running the following command:
```
/usr/openv/volmgr/bin/stopltid
```
To verify that the ltid, avrd, and robotic control processes are stopped, run the following command:
```
/usr/openv/volmgr/bin/vmps
```
If you use ACS robotic control, the acsssi and the acssel processes may continue to run when ltid is terminated. Use the UNIX kill command to individually stop those robotic control processes.
Then, start all device processes by running the following command:
```
/usr/openv/volmgr/bin/ltid
```
For debugging, start ltid with the -v (verbose) option.
If necessary, you can use the following to stop and restart all the NetBackup server processes:
```
/usr/openv/netbackup/bin/bp.kill_all
/usr/openv/netbackup/bin/bp.start_all
```