DOCUMENTATION: How to verify the required Veritas NetBackup (tm) 7.0 daemons / services are up and running on a media server

Article:TECH142421  |  Created: 2010-10-21  |  Updated: 2011-06-29  |  Article URL http://www.symantec.com/docs/TECH142421
Article Type
Technical Solution


Issue



DOCUMENTATION: How to verify the required Veritas NetBackup (tm) 7.0 daemons / services are up and running on a media server


Solution



Manuals:
Veritas NetBackup (tm) 7.0 Administrator's Guide for UNIX and Linux, Volume 1
Veritas NetBackup (tm) 7.0 Administrator's Guide for Windows, Volume 1

Chapter 20: Monitoring NetBackup Activity

Modification Type:  Supplement

Modification:

Chapter 20 of the NetBackup System Administration Guide lists the different NetBackup services along with a brief explanation of them. However,  it doesn't list which services should be running by default on a NetBackup media server.  The following is a listing of the services / daemons which should be running by default on a NetBackup 7.0 media server:

NetBackup Client Service (bpcd)
NetBackup Compatibility Service (bpcompatd)
NetBackup Remote Monitoring Management System (nbrmms)
NetBackup Service Layer (nbsl)
NetBackup Service Monitor (nbsvcmon)
NetBackup Volume Manager (vmd)
Veritas/Symantec Private Branch Exchange (pbx_exchange)
 

The “NetBackup Device Manager” (ltid) will only show as “started” if there are tape or VTL devices configured.

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 media server.

Example from a Windows server:

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

Figure 1 - Windows Services panel
 


Additional entries for NetBackup  will also appear in the Services GUI but will not show "Started."

Example from a UNIX/Linux server:

The following screen shot is from a Solaris 10 x64 server running NetBackup 7.0.  This example shows the output from the bpps -x command which includes NetBackup processes as well as the PBX service.  UNIX servers will now display NetBackup Client Daemon (bpcd) and Veritas Network Daemon (vnetd) in the output since they are stand-alone daemons. 
 

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  3826     1   0 13:22:21 ?           0:00 /usr/openv/netbackup/bin/bpcd -standalone

    root  3921     1   0 13:23:13 ?           0:00 /usr/openv/netbackup/bin/nbsvcmon

    root  3874     1   0 13:22:37 ?           0:00 /usr/openv/netbackup/bin/bpcompatd

    root  3885     1   0 13:22:44 ?           0:00 /usr/openv/netbackup/bin/nbrmms

    root  3902     1   0 13:22:48 ?           0:00 /usr/openv/netbackup/bin/nbsl

    root  3823     1   0 13:22:21 ?           0:00 /usr/openv/netbackup/bin/vnetd -standalone

 

 

MM Processes

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

    root  3880     1   0 13:22:39 ?           0:00 vmd

   

 

Shared Symantec Processes

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

    root  2573     1   0 13:10:57 ?           0:00 /opt/VRTSpbx/bin/pbx_exchange

 

Note: During the NetBackup startup process, several more daemons will initially be invoked; however, after it is determined that the running environment is that of a media server, these daemons will quickly terminate.





Article URL http://www.symantec.com/docs/TECH142421


Terms of use for this information are found in Legal Notices