The doubt about the too many unexpected processes of the "bpcd -standalone" on some media server

[liuyl]

NBU environment: Master/Media/Client 8.1.1
OS environment: RHEL 6.9

We just sometimes would encounter the following backup jobs hang with too many unexpected processes of the "bpcd -standalone"...
So what would mean about those too many unexpected processes of the "bpcd -standalone", despite the system network normally running.

root 5562 23706 0 07:50 ? 00:00:00 /usr/openv/netbackup/bin/bpcd -standalone
root 5644 23706 0 08:40 ? 00:00:00 /usr/openv/netbackup/bin/bpcd -standalone
root 6204 23706 0 17:10 ? 00:00:00 /usr/openv/netbackup/bin/bpcd -standalone
root 6413 23706 0 18:00 ? 00:00:00 /usr/openv/netbackup/bin/bpcd -standalone
root 6712 23706 0 18:50 ? 00:00:00 /usr/openv/netbackup/bin/bpcd -standalone
root 6756 1 0 15:28 ? 00:00:00 /usr/openv/netbackup/bin/bpclntcmd -refresh_use_at
root 7252 23706 0 16:20 ? 00:00:00 /usr/openv/netbackup/bin/bpcd -standalone
root 7282 23706 0 13:50 ? 00:00:00 /usr/openv/netbackup/bin/bpcd -standalone
root 7553 23706 0 14:40 ? 00:00:00 /usr/openv/netbackup/bin/bpcd -standalone
root 7575 1 0 05:20 ? 00:00:00 /usr/openv/netbackup/bin/bpclntcmd -refresh_use_at
root 8030 23706 0 15:30 ? 00:00:00 /usr/openv/netbackup/bin/bpcd -standalone
root 8692 23706 0 13:00 ? 00:00:00 /usr/openv/netbackup/bin/bpcd -standalone
root 9499 23706 0 10:30 ? 00:00:00 /usr/openv/netbackup/bin/bpcd -standalone
root 9540 23706 0 09:40 ? 00:00:00 /usr/openv/netbackup/bin/bpcd -standalone
root 9553 23706 0 11:20 ? 00:00:00 /usr/openv/netbackup/bin/bpcd -standalone
root 9606 23706 0 12:10 ? 00:00:00 /usr/openv/netbackup/bin/bpcd -standalone
root 11379 23706 0 10:33 ? 00:00:00 /usr/openv/netbackup/bin/bpcd -standalone
root 12011 23706 0 08:00 ? 00:00:00 /usr/openv/netbackup/bin/bpcd -standalone
root 12085 23706 0 08:50 ? 00:00:00 /usr/openv/netbackup/bin/bpcd -standalone
root 12185 1 0 11:24 ? 00:00:00 /usr/openv/netbackup/bin/bpclntcmd -refresh_use_at
root 12350 1 0 Dec17 ? 00:00:00 /usr/openv/netbackup/bin/bpclntcmd -refresh_use_at
root 12532 1 0 06:20 ? 00:00:00 /usr/openv/netbackup/bin/bpclntcmd -refresh_use_at
root 12564 1 0 16:29 ? 00:00:00 /usr/openv/netbackup/bin/bpclntcmd -refresh_use_at
root 12708 23706 0 17:20 ? 00:00:00 /usr/openv/netbackup/bin/bpcd -standalone
root 12942 23706 0 18:10 ? 00:00:00 /usr/openv/netbackup/bin/bpcd -standalone
root 13320 23706 0 16:30 ? 00:00:00 /usr/openv/netbackup/bin/bpcd -standalone
root 13521 23706 0 19:00 ? 00:00:00 /usr/openv/netbackup/bin/bpcd -standalone
root 14080 23706 0 14:00 ? 00:00:00 /usr/openv/netbackup/bin/bpcd -standalone
root 14418 23706 0 14:50 ? 00:00:00 /usr/openv/netbackup/bin/bpcd -standalone
root 14754 23706 0 13:10 ? 00:00:00 /usr/openv/netbackup/bin/bpcd -standalone
root 14926 23706 0 15:40 ? 00:00:00 /usr/openv/netbackup/bin/bpcd -standalone
root 16076 23706 0 09:50 ? 00:00:00 /usr/openv/netbackup/bin/bpcd -standalone
root 16104 23706 0 10:40 ? 00:00:00 /usr/openv/netbackup/bin/bpcd -standalone
root 16138 23706 0 11:30 ? 00:00:00 /usr/openv/netbackup/bin/bpcd -standalone
root 16202 23706 0 12:20 ? 00:00:00 /usr/openv/netbackup/bin/bpcd -standalone

#
#
# bpps -a|grep -Ei "/bin/bpcd -standalone"|wc -l
72
#
#

[Nicolai]

Hi @liuyl 

I have seen something like that on older version of Netbackup. In all cases the root cause was missing ressources, eiter memory, swap space or kernel ressources. Talk to your Linux admin about monitoring of memory and swap space.

For kernel ressources, I would see if Veritas recommendation are followed. If you go to https://sort.veritas.com/checklist/install a check list will be generated. The checklist contain Veritas recommended kernel setting. 

If not done so already, try using the sort data collector. Really nice feature and fairly easy to use.

[liuyl]

There are almost all the kernel resources configurations with their own default values in my Linux hosts environment, but I find that just always some fixed  hosts systems would encounter such problem ！