Issues with NBPEM/NBJM
In the activity monitory, details would be visible as the job starts, which policyjob follower pod the job would be executed on.
The nbpemreq command can be used to verify the assignments. If the command is run on the primary or the leader, it will display information on the WorkDistributor leader. The - M option can be specified with the pod name to get the information on the specific pod. If no - M option is specified when executing the command from the primary pod, then the default gets routed to the leader pod.
Logging details: The
bp.confandnblog.conffiles are shared between all pods. NBPEM and NBJM verbose levels can be set using Web UI. The verbose level applies to all pods instances. Viewing logs and extracting logs fromfluentbitin detail is mentioned under Common Operations. Commands for increasing logs verbose are listed under Usability and Supportability.Debugging resources:
nbpem binary path:
/usr/openv/netbackup/bin/nbpemnbjm binary path:
/usr/openv/netbackup/bin/nbjmlibnbsubscriber path:
/usr/openv/lib/libnbsubscriber.so(In the primary main container)libmqclient path:
/usr/openv/lib/libmqclient.sobprdproxy path:
/usr/openv/netbackup/bin/bprdproxy(In the primary main container)