NetBackup Status 14 for Linux client backup

[Kayhan]

We have an issue with agent base Linux machine backup. The backup seems to work and transfer data but the job would fail with status 14. Below is the job logs:

25/01/2018 7:50:53 AM - Info nbjm (pid=4604) starting backup job (jobid=2945070) for client auadlloep02, policy INT_OpenEdge, schedule Weekly
25/01/2018 7:50:53 AM - Info nbjm (pid=4604) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=2945070, request id:{B452DAE0-1A0C-4B9B-A82C-904DB982ABA3})
25/01/2018 7:50:53 AM - requesting resource Adam_msdp
25/01/2018 7:50:53 AM - requesting resource auadlnms01.NBU_CLIENT.MAXJOBS.auadlloep02
25/01/2018 7:50:53 AM - requesting resource auadlnms01.NBU_POLICY.MAXJOBS.INT_OpenEdge
25/01/2018 7:50:53 AM - granted resource auadlnms01.NBU_CLIENT.MAXJOBS.auadlloep02
25/01/2018 7:50:53 AM - granted resource auadlnms01.NBU_POLICY.MAXJOBS.INT_OpenEdge
25/01/2018 7:50:53 AM - granted resource MediaID=@aaabJ;DiskVolume=PureDiskVolume;DiskPool=auadlbms07_msdp;Path=PureDiskVolume;StorageServer=auadlbms07;MediaServer=auadlbms07
25/01/2018 7:50:53 AM - granted resource auadlbms07_msdp
25/01/2018 7:50:53 AM - estimated 0 kbytes needed
25/01/2018 7:50:53 AM - Info nbjm (pid=4604) started backup (backupid=auadlloep02_1516828853) job for client auadlloep02, policy INT_OpenEdge, schedule Weekly on storage unit auadlbms07_msdp
25/01/2018 7:50:55 AM - started process bpbrm (pid=12872)
25/01/2018 7:50:58 AM - Info bpbrm (pid=12872) auadlloep02 is the host to backup data from
25/01/2018 7:50:58 AM - Info bpbrm (pid=12872) reading file list for client
25/01/2018 7:51:00 AM - Info bpbrm (pid=12872) accelerator enabled
25/01/2018 7:51:04 AM - connecting
25/01/2018 7:51:06 AM - Info bpbrm (pid=12872) starting bpbkar32 on client
25/01/2018 7:51:06 AM - Info bpbkar32 (pid=15958) Backup started
25/01/2018 7:51:06 AM - connected; connect time: 0:00:00
25/01/2018 7:51:06 AM - Info bptm (pid=7828) start
25/01/2018 7:51:06 AM - Info bptm (pid=7828) using 262144 data buffer size
25/01/2018 7:51:06 AM - Info bptm (pid=7828) setting receive network buffer to 1049600 bytes
25/01/2018 7:51:06 AM - Info bptm (pid=7828) using 512 data buffers
25/01/2018 7:51:07 AM - Info bptm (pid=7828) start backup
25/01/2018 7:51:07 AM - Info bptm (pid=7828) backup child process is pid 12636.12432
25/01/2018 7:51:07 AM - Info bptm (pid=12636) start
25/01/2018 7:51:07 AM - begin writing
25/01/2018 11:09:33 AM - Warning bpbrm (pid=12872) from client auadlloep02: WRN - /opr is only being backed up as a symbolic link
25/01/2018 11:09:53 AM - Error bpbrm (pid=12872) from client auadlloep02: ERR - Cannot write to tir_info_file, fd is NULL.
25/01/2018 11:09:53 AM - Info bptm (pid=7828) waited for full buffer 297551 times, delayed 490471 times
25/01/2018 11:09:58 AM - Info auadlbms07 (pid=7828) StorageServer=PureDisk:auadlbms07; Report=PDDO Stats for (auadlbms07): scanned: 943917257 KB, CR sent: 458355 KB, CR sent over FC: 0 KB, dedup: 100.0%, cache disabled
25/01/2018 11:10:01 AM - Info bpbkar32 (pid=15958) done. status: 14: file write failed
25/01/2018 11:10:01 AM - end writing; write time: 3:18:54
file write failed (14)

Any idea what it may relat to?

[Marianne]

This seems to be the problem:

"ERR - Cannot write to tir_info_file, fd is NULL."

TIR is normally associated with the option explicitly selected in the policy attribute. Also automatically selected when BMR option is selected.
Can you verify that this is the case?
If so, have you tried this backup without BMR/TIR?

Do you have bpbkar log on the client to track backup activities? 
If not, please create the folder and add 
VERBOSE = 3
to bp.conf.

There are some forum posts and TNs that shows problem is related to filesystem types on the client.
Examples: 
https://vox.veritas.com/t5/NetBackup/can-t-backup-home-in-linux/td-p/626271
https://www.veritas.com/support/en_US/article.000028311

There was also this lengthy (extremely frustrating) discussion regarding Accelerator and BMR that was never really solved (although the backup worked with BMR and Accelerator de-selected):
https://vox.veritas.com/t5/NetBackup/Aix-client-backup-getting-code-14/td-p/705991

PS:
If you want to post bpbkar log here, please copy the log to bpbkar.txt and upload as attachment.

[Kayhan]

Thanks for your reply.

The backup is working fine after we removed /proc and /sys from the selection list. Apparently, these containers are used by Kernel itself and since we have a VM snapshot of the client we could remove them from the selection list.

So, the backup is now working fine.