netbackup process monitoring

For the master:

http://seer.entsupport.symantec.com/docs/297548.htm

For a media server:

http://seer.entsupport.symantec.com/docs/297551.htm

DOCUMENTATION: How to verify the required Veritas NetBackup (tm) 6.5 daemons / services are up and running on a master server
http://seer.entsupport.symantec.com/docs/297548.htm

DOCUMENTATION: How to verify the required Veritas NetBackup (tm) 6.5 daemons / services are up and running on a media server
http://seer.entsupport.symantec.com/docs/297551.htm

and for completeness:

DOCUMENTATION: How to verify the required Veritas NetBackup (tm) 6.5 daemons / services are up and running on a client
http://seer.entsupport.symantec.com/docs/297553.htm

***EDIT***
Touché  rj!

thanks, but a lot of these processes spawn child processes when the server is busy, are there any processes that i can set up monitoring against that dont spawn child processes?

is busy" ?

A lot of these 'processes' will result in further processes when active & backups are running e.g. bptm, bpbrm etc. otherwise it wouldn't work!

Essentially the only relevance are the actual services & there are a limited number of these (per the original T/N's quoted).

May be worth looking through the following:
DOCUMENTATION: Details on the VERITAS NetBackup (tm) 6.0 Backup and Restore Process Flow. Covers all backup and restore processes from beginning to end.
http://seer.entsupport.symantec.com/docs/282015.htm

Why not have your server up and running normally, without restore or backup running and look in the activity monitor->daemons and thats your list. Works for me every time.
Use something like serversalive and unix plugin to monitor if you dont like nom. I use both.

but my point is being missed

bprd and bpdbm are running multiple versions of themselves now on my system, and it is a quiet period now.  If i ever got to a stage where there were no backups (unlikely), i know there would only be 1 version of these 'services' running.
So my question is, are there any of these 'services' that dont spawn extras?

any readily available info.

e.g the following is from the Admin Guide but it DOESN'T expand any further on the part(s) that I believe you are interested in:

"...
Stand-alone daemons: These NetBackup daemons always run and listen to accept connections. Examples include bpdbm, bprd, bpjobd, and vmd.
Multiprocess stand-alone daemons: NetBackup daemons that “fork” a child process to handle requests. Examples include bpdbm and bprd.
Single-process stand-alone daemons: NetBackup daemons that accept connections and handle requests in the same process.
inetd daemons: NetBackup daemons usually launched by inetd(1m)or bpinetd. Examples include bpcd, bpjava-msvc, and vnetd.
..."

This obviously appears to confirm what you don't want (i.e. bprd & bpdbm) but doesn't expand on what you do (single-process standalone daemons) - unless I really am missing the point......

no, thats my point.
at some stage i'll write a script to monitor which daemons appear and disappear, but until that point...........

(If UNIX servers) To go back to your original point what processes to monitor. I would have a look at the /etc/init.d/netbackup script - in there is all the scripts for the parent processes that are started and remain running for the duration and would be what I would be looking to check in your monitoring.