danguss
There should be another bpbkar log or more entries in bpbkar log.
The log ends at 08:52:16.
Job Details shows this entry:
22/08/2019 08:52:18 - Info bpbkar (pid=46861) 0 entries sent to bpdbm.
If bpbkar on backup host srv15453 'crashed', there should be a core file.
Can you please check on the media server / backup host ?
Question - do you have file level recovery option selected in the policy?
If so, have you tried without this option?
bpbkar log also shows errors returned by VxMS.
Looking at VxMS logs, we see errors such as these:
08/22/2019 08:52:16 : readFileDataIntoBuffer:RvpUnixFile.cpp:265 <ERROR> : Unable to read file of type: 5
08/22/2019 08:52:16 : readFileDataIntoBuffer:RvpUnixFile.cpp:266 <WARN> : Returning: 3
08/22/2019 08:52:16 : FSOLogCallback:RvpFsoFileSystemMgr.cpp:94 <ERROR> : Initialize: Invalid superblock header
08/22/2019 08:52:16 : FSOLogCallback:RvpFsoFileSystemMgr.cpp:94 <WARN> : FileSystemObject::claimFileSystem - unknown filesystem
08/22/2019 08:52:16 : g_vixInterfaceLogger:libvix.cpp:1805 <DEBUG> : [VFM_ESINFO] VixDiskLib: VixDiskLib_GetMetadataKeys: Insufficient buffer size (has 1, need 203). Error 24 (Buffer is too small) at 5930.
(There are multiple buffer errors).
I don't know if this is coincidence, but it looks like the same time that bpbkar process crached.
VxMS carried on after this timestamp.
Last VxMS entry:
08/22/2019 08:52:29 : FSOLogCallback:RvpFsoFileSystemMgr.cpp:94 <WARN> : Retrieving inode 135110846 failed
You will be better off logging a Support call with Veritas - they are better equipped to read and understand the errors in VxMS log.