If a process was unable to report the extended error status as the final job status, the job exits with status 252. Extended error status numbers are above 255 and there are many possibilities. You will need to examine the job details display to determine if the issue gives you a clue there. You may need to turn on logs...etc. Verify through backup, archive and restore console to see if the job captured all of the files expected. You may have your jobs completed, and the error may be in the final Netbackup reporting and closure of the job status.

.... also, you may want to monitor the daemons during job completions to see if the deamons are running as expected. I once had a master server that a few daemons would stop at the end of the job. Daemon stopping could possibly generate the 252 error code.

 I could find some comments like there are known issues in NBU 6.5.4 EMM,RB.

Is that true?

Show  me:

bpps -a
vxlogview -X jobid=jobid_of_failed_job -d all