You can check manually, using the two files above, along the lines of:
...find backup image names, and the job that they belong to:
# grep -i "using the media server" backup-stats-err.txt
1436989095 1 33412 4 master01 114 113 0 client01 bptm Using the media server to write NetBackup data for backup client01_1436988145 to master01
1436989339 1 33412 4 master01 115 113 0 client01 bptm Using the media server to write NetBackup data for backup client01_1436989112 to master01
...in the output above we see two child jobs (114 and 115), both child jobs of parent job 113, and to the right shows the name of the backup image...
.
...now, using the job ID of the first image ID above (i.e. Job ID: 114), search the same file for how much was scanned by MSDP (you may need to change the search string for different storage unit types) for the child job:
# egrep -i "114.*scanned:" backup-stats-err.txt
1436989095 1 33412 4 master01 114 113 0 client01 bptm StorageServer=PureDisk:master01; Report=PDDO Stats for (master01): scanned: 9322641 KB, CR sent: 134399 KB, CR sent over FC: 0 KB, dedup: 98.6%, cache disabled
1436989109 1 33412 4 master01 114 113 0 client01 bptm StorageServer=PureDisk:master01; Report=PDDO Stats for (master01): scanned: 2969 KB, CR sent: 434 KB, CR sent over FC: 0 KB, dedup: 85.4%, cache disabled
...which shows there the backup image actually generated two 'sets' of data which were processed by MSDP, totalling 9325610 KB...
.
...now, check to see whether the backup image existed at the time the listing was taken:
# grep -i "client01_1436988145" backup-stats-ima.txt
Time: 15/07/2015 20:22:25 ID: client01_1436988145 FULL (0)
...which shows that the listing does contain an image of that name, and therefore does exist at the time the listing was taken....
.
...and to see if the image still exists, right now, do:
# bpimagelist -idonly -backupid client01_1436988145
HTH.