We just upgraded our Netbackup appliances from 2.5.3 to the latest 2.6.0.2, we noticed quite a few status code 87 errors which we did not see before the upgrade. Anybody has seen simliar issues or has any ideas?
An example failed job detail is like this:
05/23/2014 11:35:14 - Info bpbrm (pid=20806) from client daa21267app016: TRV - last message being suppressed after 10 occurrences
05/23/2014 11:39:04 - Info bpbkar (pid=6800) 30000 entries sent to bpdbm
05/23/2014 11:45:15 - Info bpbrm (pid=20806) from client daa21267app016: TRV - object not found for file system backup: D:
05/23/2014 11:45:15 - Info bpbkar (pid=6800) bpbkar waited 11523 times for empty buffer, delayed 81235 times.
05/23/2014 11:45:25 - Critical bptm (pid=20881) sts_close_handle failed: 2060017 system call failed
05/23/2014 11:45:25 - Critical bptm (pid=20881) cannot write image to disk, media close failed with status 2060017
05/23/2014 11:45:25 - Info ldcsymapp01 (pid=20881) StorageServer=PureDisk:ldcsymapp01; Report=PDDO Stats for (ldcsymapp01): scanned: 14276287 KB, CR sent: 9755 KB, CR sent over FC: 0 KB, dedup: 99.9%, cache hits: 126699 (95.3%)
05/23/2014 11:45:25 - Critical bptm (pid=20881) sts_close_server failed: error 2060005 object is busy, cannot be closed
05/23/2014 11:45:28 - Info bptm (pid=20881) EXITING with status 87 <----------
05/23/2014 11:45:28 - Info bpbkar (pid=6800) done. status: 87: media close error
05/23/2014 11:45:28 - end writing; write time: 0:44:59
05/23/2014 12:39:28 - job 129499 was restarted as job 129519
media close error (87)
Thanks,
Jason