NBPEM_cleanup and NBPEM_Email

Hi all,

We've been experiencing a lot of issues after upgrading to 8.1.2 (and evidently there is no "downgrade" option). Specifically getting a lot of error code 233 (never had those prior to upgrading from 8.1.1). In any event, one of the issues was with nbpem. My question is: upon doing a bpps -x, I see the nbpem daemon, and some child daemons:

# bpps -x | grep pem
root 6361 1 0 Nov08 ? 00:37:22 /usr/openv/netbackup/bin/nbpem
root 6388 6361 0 Nov08 ? 00:00:26 /usr/openv/netbackup/bin/nbproxy dblib nbpem
root 7310 6361 0 Nov08 ? 00:07:29 /usr/openv/netbackup/bin/nbproxy dblib nbpem_email
root 19847 6361 0 Nov08 ? 00:00:01 /usr/openv/netbackup/bin/nbproxy dblib nbpem_cleanup

Is this output normal? Do the nbproxy child daemons have the same start time as nbpem? I would assume that "email" and "cleanup" would be start "as needed" verses contiuously running.

Thanks

Tags (2)
3 Replies

Re: NBPEM_cleanup and NBPEM_Email

You will need to dig into nbpem logs to see what those 2 processes are doing. Maybe with assistance from Veritas Support.

Re: NBPEM_cleanup and NBPEM_Email

Those processes are completely normal.  

The nbpem process, being multithreaded, can't connect directly to the single threaded bpdbm processes, it has to use nbproxy connections.  The connections used when doing various operations to retrieve information from the database.  The generic "nbproxy dblib nbpem" is the main interface that pem uses to retrieve the data it needs.  

The other two pxory processes are used for when pem initiaties cleanup and when it needs to generate an email.  Those have been seen in the past versions to block processing of the backup jobs, and hence, were given a separte proxy interface.

Deb

Highlighted

Re: NBPEM_cleanup and NBPEM_Email

Those processes are completely normal.  

The nbpem process, being multithreaded, can't connect directly to the single threaded bpdbm processes, it has to use nbproxy connections.  The connections used when doing various operations to retrieve information from the database.  The generic "nbproxy dblib nbpem" is the main interface that pem uses to retrieve the data it needs.  

The other two pxory processes are used for when pem initiaties cleanup and when it needs to generate an email.  Those have been seen in the past versions to block processing of the backup jobs, and hence, were given a separte proxy interface.

Deb

Tags (1)