bptm image write failed: error 2060022: software error

[Pramod_Malawade]

Good day all,

One of my Hyper-V clients has been failing backup continously. Below is what i see in the logs.

Please help! 

Job details show:

26-Apr-2018 11:11:34 - Critical bptm (pid=9424) image write failed: error 2060022: software error
26-Apr-2018 11:11:35 - Info bpbkar32 (pid=30196) 33671 entries sent to bpdbm
26-Apr-2018 11:11:35 - Info bpbkar32 (pid=30196) 33682 entries sent to bpdbm
26-Apr-2018 11:11:36 - Info bpbkar32 (pid=30196) 33683 entries sent to bpdbm
26-Apr-2018 11:11:37 - Info bpbkar32 (pid=30196) 33696 entries sent to bpdbm
26-Apr-2018 11:11:37 - Info bpbkar32 (pid=30196) 33697 entries sent to bpdbm
26-Apr-2018 11:11:38 - Info bpbkar32 (pid=30196) 33710 entries sent to bpdbm
26-Apr-2018 11:11:39 - Error bptm (pid=9424) cannot write image to disk, Invalid argument
26-Apr-2018 11:11:40 - Info bptm (pid=9424) EXITING with status 84 <----------
26-Apr-2018 11:11:40 - Info bmc0258 (pid=9424) StorageServer=PureDisk:bmc0258; Report=PDDO Stats (multi-threaded stream used) for (bmc0258:( scanned: 75523 KB, CR sent: 2119 KB, CR sent over FC: 0 KB, dedup: 97.2%, cache disabled
26-Apr-2018 11:11:47 - Info bpbkar32 (pid=0) done. status: 84: media write error

BPTM logs show:

11:34.734 [9424.8508] <16> 424398:bptm:9424:bmc0258: [ERROR] PDSTS: fbu_fill_bitmap: (4606) stream_offset(1276608512) + length(4096) > (4607) stream_offset(1276608512)

11:11:34.734 [9424.8508] <16> 424398:bptm:9424:bmc0258: [ERROR] PDSTS: fbu_scan_buf: fbu_fill_bitmap() failed (2060022:software error)

11:11:34.734 [9424.8508] <16> 424398:bptm:9424:bmc0258: [ERROR] PDSTS: write_special_buf: fbu_scan_buf failed: (2060022:software error)

11:11:34.735 [9424.8508] <16> 424398:bptm:9424:bmc0258: [ERROR] PDSTS: write_unknown_len_buf: write_special_buf() failed, byteswritten:<0>, status:<0x1> (2060022:software error)

11:11:34.735 [9424.8508] <16> 424398:bptm:9424:bmc0258: [ERROR] PDSTS: impl_write_image: write_unknown_len_buf() failed (2060022:software error)

11:11:34.735 [9424.8508] <16> 424398:bptm:9424:bmc0258: [ERROR] PDSTS: impl_write_image: STAT contents: st_type=0 [NONE] st_len=320 st_flags=0x1 [SIZE_UNKNOWN] st_seqno=9 flags=0 [OTHER] extents=[1] offset=77332480 length=58368 fname=NULL

11:11:34.735 [9424.8508] <16> 424398:bptm:9424:bmc0258: [ERROR] PDSTS: impl_write_image: exit (0 0x1 2060022:software error)

11:11:34.735 [9424.8508] <16> 424398:bptm:9424:bmc0258: [ERROR] PDSTS: pi_write_image_v7: impl_write_image() failed (2060022:software error)

11:11:34.735 [9424.8508] <32> do_write_image: sts_write_image failed: byteswritten = 0, len = 58368

11:11:34.735 [9424.8508] <32> do_write_image: sts_write_image failed: error 2060022 (77332480 58368 0)

[Systems_Team]

Hi Pramod,

Always best to provide more details about your environment - eg:

• NetBackup versions (and patch level) for Master Server, Media Server and Client
• O/S versions (and patch levels)  for Master Server, Media Server and Client

Quite often "2060022: software error" messages relate to problems with OST plugin's, but as you seem to describe that this is only happening on one of your Hyper-V clients, I don't initially suspect this to be the case.

If your client is Linux, then have a look at this link: https://www.veritas.com/support/en_US/article.100009831.  The error messages are very similar.  This one relates to the quiesce tool from Veritas.  Note that as of NetBackup 8.1, this is no longer supported.  Also note that this relates to VMware, not Hyper-V which you are running - but could be worth checking if you are somehow getting a dirty (ie: non-quiesced) snapshot.

Here is a very similar one to the link above (https://www.veritas.com/support/en_US/article.100010632), but relates to Windows clients.  Once again it is targeted towards VMware, but again relates to a dirty (ie: non-quiesced) snapshot.

Another link, which relates to an issue with Accelerator (https://www.veritas.com/support/en_US/article.100009743) may also be helpful.  You've provided a snippet of the job details, so not sure if yours also includes the "accelerator verification failed" error as shown in this one.

Hope this helps,

Steve