How to verify the required NetBackup 7.x and 8.x daemons / services are up and running on a master server

How to verify the required NetBackup 7.x and 8.x daemons / services are up and running on a master server

Article: 100002166
Last Published: 2020-04-13
Ratings: 7 1
Product(s): NetBackup

Description

The following is a listing of the services / daemons which should be running on a NetBackup master server.  


Note: When checking for running services on a Windows NetBackup 7.x or later master server,  it is important to note that not all the services begin with "NetBackup." Starting with NetBackup 6.0, there are additional services for the Adaptive Server Anywhere (ASA) database service and the Private Branch exchange (PBX) service.  For Windows servers, these new services will not be grouped with the other NetBackup services when using the Services panel in Windows.  For UNIX servers, not all of these daemons will appear in the bpps output.  A new switch (-x) is available for the bpps command beginning in NetBackup 6.0 to see shared processes such as PBX.

The following is a listing of the services that need to be running on a NetBackup 7.x and later master server:

Veritas/veritas Private Branch Exchange ( pbx_exchange)
Adaptive Server Anywhere - VERITAS_NB - ASA Database service ( NB_dbsrv)
NetBackup Event Management Service ( nbevtmgr)
NetBackup Enterprise Media Manager ( nbemm)
NetBackup Agent Request Server ( nbars)
NetBackup Auditing Service ( nbaudit)
NetBackup Compatibility Service ( bpcompatd)
NetBackup Network Daemon ( vnetd)
NetBackup Request Manager ( bprd)
NetBackup Remote Manager and Monitor Service ( nbrmms)
NetBackup Policy Execution Manager ( nbpem)
NetBackup Storage Lifecycle Manager ( nbstserv)
NetBackup Resource Broker ( nbrb)
NetBackup Job Manager ( nbjm)
NetBackup Service Layer ( nbsl)
NetBackup Database Manager ( bpdbm)
NetBackup Service Monitor ( nbsvcmon)
NetBackup Client Service ( bpcd)
NetBackup Volume Manager ( vmd)

Additional daemons may also need to be running if other add-on products, database agents, etc. are installed. The above is the minimum listing of NetBackup daemons that should be active on the master server.

 

Example from a Windows server

The following screen shot is from a Windows 2008 server running NetBackup 7.x.  This example combines the various NetBackup processes that are displayed under the Windows Services panel.

Windows servers will also display entries for the NetBackup Bare Metal Restore Master Server and the NetBackup Vault Manager services.  These are installed by default as part of a NetBackup Windows server installation.

  

 

Example from a UNIX server

This example shows the output from the bpps -x command being run on a Solaris server, which includes NetBackup processes as well as the PBX service.  

UNIX servers will show additional entries for the nbproxy and bpjobd daemons.  The nbproxy daemon handles communication between the NetBackup services and the legacy daemons.  The bpjobd daemon handles updates to the jobs database.  These daemons also run on Windows servers but are not displayed in the Services GUI.

On UNIX servers, run the bpps -x command:

# cd /usr/openv/netbackup/bin
# ./bpps -x

Output will be similar to the following:

NB Processes

------------

   root  2768     1   0 16:12:00 ?           0:00 /usr/openv/netbackup/bin/nbevtmgr
   root  3011     1   1 16:12:41 ?           0:00 /usr/openv/netbackup/bin/bmrbd
   root  2866     1   1 16:12:07 ?           0:01 /usr/openv/netbackup/bin/nbemm
   root  2763     1   0 16:11:58 ?           0:02 /usr/openv/db//bin/NB_dbsrv @/usr/openv/var/global/server.conf @/usr/openv/var/
   root  2915  2911   1 16:12:19 ?           0:01 /usr/openv/netbackup/bin/nbproxy dblib nbpem
   root  2966     1   1 16:12:31 ?           0:00 /usr/openv/netbackup/bin/nbars
   root  2773     1   0 16:12:02 ?           0:01 /usr/openv/netbackup/bin/nbaudit
   root  2892     1   0 16:12:14 ?           0:00 /usr/openv/netbackup/bin/bpcompatd
   root  2707     1   0 16:11:55 ?           0:00 /usr/openv/netbackup/bin/vnetd -standalone
   root  2882     1   0 16:12:11 ?           0:00 /usr/openv/netbackup/bin/bprd
   root  2938     1   1 16:12:26 ?           0:01 /usr/openv/netbackup/bin/nbrmms
   root  2911     1   1 16:12:18 ?           0:00 /usr/openv/netbackup/bin/nbpem
   root  2898  2897   1 16:12:14 ?           0:01 /usr/openv/netbackup/bin/bpjobd
   root  2997  2901   3 16:12:38 ?           0:01 /usr/openv/netbackup/bin/nbproxy dblib nbjm
   root  2929     1   1 16:12:22 ?           0:00 /usr/openv/netbackup/bin/nbstserv
   root  2871     1   1 16:12:09 ?           0:01 /usr/openv/netbackup/bin/nbrb
   root  2901     1   1 16:12:16 ?           0:00 /usr/openv/netbackup/bin/nbjm
   root  2961     1   1 16:12:29 ?           0:00 /usr/openv/netbackup/bin/nbsl
   root  2897     1   0 16:12:14 ?           0:00 /usr/openv/netbackup/bin/bpdbm
   root  2996     1   1 16:12:38 ?           0:00 /usr/openv/netbackup/bin/nbsvcmon
   root  2712     1   0 16:11:56 ?           0:00 /usr/openv/netbackup/bin/bpcd -standalone


MM Processes
------------
   root  2887     1   0 16:12:12 ?           0:00 vmd


Shared Veritas Processes
-------------------------
   root  1456     1   1   Jul 01 ?           0:09 /opt/VRTSpbx/bin/pbx_exchange

 

Was this content helpful?