Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ Troubleshooting Guide
  3. Troubleshooting procedures
  4. Troubleshooting NetBackup problems
  5. Verifying that all processes are running on UNIX or Linux servers
NetBackup™ Troubleshooting Guide

Verifying that all processes are running on UNIX or Linux servers

For NetBackup to operate properly, the correct set of processes (daemons) must be running on your UNIX or Linux 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 or Linux servers

  1. To see the list of processes (daemons) running on the primary server and on the media server, enter the following command:
    /usr/openv/netbackup/bin/bpps -x
  2. Ensure that the following processes are running on the NetBackup servers:

    Primary 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
    pbx_exchange
    postgres
    vmd
    vnetd -standalone
    nbmqbroker
    

    Media server

    avrd (automatic volume recognition, only if drives are configured 
    on the server)
    bpcd  - standalone
    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://support.cohesity.com/s/article/article-100002166.

  3. If either the NetBackup Request Daemon (bprd) or the NetBackup Database Manager Daemon (bpdbm) is not running, start them by entering the following command:
    /usr/openv/netbackup/bin/initbprd
  4. If the NetBackup Web Management Console (nbwmc) is not running, start it with the following command:
    /usr/openv/netbackup/bin/nbwmc
  5. 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
  6. To verify that the ltid, avrd, and robotic control processes are stopped, run the following command:
    /usr/openv/volmgr/bin/vmps
  7. 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.
  8. Then, start all device processes by running the following command:
    /usr/openv/volmgr/bin/ltid

    For debugging, start ltid with the -v (verbose) option.

  9. 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

Feedback

Was this page helpful?
Previous

Troubleshooting NetBackup problems

Next

Verifying that all processes are running on Windows servers

Feedback

Was this page helpful?