I need a solution
Using Netbackup 5230 appliance on 2.5.3
I seem to be getting status 14 errors on a few of our backups. The backups run for a few hours, then fail at various times.
12/27/2013 12:06:28 - Error bptm (pid=27347) image copy failed: error 2060017: system call failed
12/27/2013 12:06:32 - Critical bptm (pid=27347) sts_close_handle failed: 2060017 system call failed
12/27/2013 12:06:32 - Info wpbk11ho (pid=27347) StorageServer=PureDisk:master; Report=PDDO Stats for (master): scanned: 308099982 KB, CR sent: 263117 KB, CR sent over FC: 0 KB, dedup: 99.9%
12/27/2013 12:06:32 - Critical bptm (pid=27347) sts_close_server failed: error 2060005 object is busy, cannot be closed
12/27/2013 12:06:34 - Info bptm (pid=27347) EXITING with status 14 <----------
12/27/2013 12:06:35 - Info bpbkar (pid=3284) done. status: 14: file write failed
In most cases, the log shows as above, however, in some cases, I see as below.
12/26/2013 21:02:33 - Error bptm (pid=11612) image copy failed: error 2060002: memory allocation
12/26/2013 21:02:38 - Critical bptm (pid=11612) sts_close_handle failed: 2060002 memory allocation
12/26/2013 21:02:38 - Info wpbk11ho (pid=11612) StorageServer=PureDisk:master; Report=PDDO Stats for (master): scanned: 352620800 KB, CR sent: 147996 KB, CR sent over FC: 0 KB, dedup: 100.0%
12/26/2013 21:02:38 - Critical bptm (pid=11612) sts_close_server failed: error 2060005 object is busy, cannot be closed
12/26/2013 21:02:40 - Info bptm (pid=11612) EXITING with status 14 <----------
12/26/2013 21:02:42 - Info bpbkar (pid=8532) done. status: 14: file write failed
Or,
12/23/2013 11:35:58 - Error bptm (pid=19685) image copy failed: error 2060017: system call failed
12/23/2013 11:36:01 - Critical bptm (pid=19685) sts_close_handle failed: 2060011 offset invalid for object or context
12/23/2013 11:36:01 - Info wpbk11ho (pid=19685) StorageServer=PureDisk:master; Report=PDDO Stats for (master): scanned: 375044440 KB, CR sent: 381747 KB, CR sent over FC: 0 KB, dedup: 99.9%
12/23/2013 11:36:01 - Critical bptm (pid=19685) sts_close_server failed: error 2060005 object is busy, cannot be closed
12/23/2013 11:36:16 - Info bptm (pid=19685) EXITING with status 14 <----------
12/23/2013 11:36:18 - Info bpbkar (pid=9796) done. status: 14: file write failed