Incremental VMware Backups to deduplication pool are failing with Status 13/84

Article:TECH190326  |  Created: 2012-06-04  |  Updated: 2013-09-24  |  Article URL http://www.symantec.com/docs/TECH190326
Article Type
Technical Solution

Product(s)


Issue



Incremental VMware Backups to deduplication pools are failing with Status 13/84 due to compressed index files within the Windows VM causing problem.


Error



Status Code: 13

Status Code: 84

Detailed Status:
4/18/2012 1:03:04 PM - begin writing
4/18/2012 1:27:36 PM - Critical bptm(pid=9628) image write failed: error 2060022: software error      
4/18/2012 1:27:42 PM - Error bptm(pid=9628) cannot write image to disk, Invalid argument      
4/18/2012 1:27:42 PM - Info bptm(pid=9628) EXITING with status 84 <----------        
4/18/2012 1:27:42 PM - Critical bpbrm(pid=6304) from client VMCLIENT01: FTL - tar file write error (0)

4/18/2012 2:09:36 PM - Info bpbkar32(pid=0) done. status: 13: file read failed

bpbkar:
12:16:57.510 PM: [1540.6204] <2> tar_base::V_vTarMsgW: INF - File System Name to catalog VMFILE0.
12:17:06.122 PM: [1540.6204] <4> tar_base::V_vTarMsgW: INF - tar message received from flash_bridge::get_buffer
12:17:06.122 PM: [1540.6204] <2> tar_base::V_vTarMsgW: FTL - tar file write error (0)
12:17:07.385 PM: [1540.6204] <4> tar_base::V_vTarMsgW: INF - tar message received from vxms_shutdown

PDPlugin.log:
01/26/12 12:16:58 [9232] [5104] [DEBUG] fbu_fill_bitmap (296) stream_offset=4890624, file_offset=8192, length=4608, fsize=4198912
01/26/12 12:16:58 [9232] [5104] [DEBUG] vxms_transadr: starting adr=236407
01/26/12 12:16:58 [9232] [5104] [DEBUG] vxms_transadr: bmw=0xffffff80, map_part=0, part_index=7387, pix=7387
01/26/12 12:16:58 [9232] [5104] [DEBUG] fbu_fill_bitmap (297) stream_offset=4890624, file_offset=0, length=8192, fsize=4198912
01/26/12 12:16:58 [9232] [5104] [ERROR] fbu_fill_bitmap ERROR (296) stream_offset(4890624) + length(4608) > (297) stream_offset(4890624)
01/26/12 12:16:58 [9232] [5104] [ERROR] fbu_scan_buf fbu_fill_bitmap failed: software error
01/26/12 12:16:58 [9232] [5104] [ERROR] write_special_buf fbu_scan_buf failed : (2060022:software error)
01/26/12 12:16:58 [9232] [5104] [ERROR] write_unknown_len_buf - write_special_buf failed: byteswritten: <0>, status: <0x1>,  (2060022:software error)
01/26/12 12:16:58 [9232] [5104] [ERROR] impl_write_image: STAT contents:
st_type=0 [NONE]
st_len=320
st_flags=0x1 [SIZE_UNKNOWN]
st_seqno=5
flags=0 [OTHER]
extents=[1]
offset=9699328
length=128000
fname=NULL
 

01/26/12 12:16:58 [9232] [5104] [ERROR] impl_write_image error exit (0 0x1 2060022:software error)
01/26/12 12:16:58 [9232] [5104] [DEBUG] pi_write_image_v7 exit (2060022:software error)

bptm:
12:16:58.025 [9232.5104] <2> 66015:bptm:9232:vmbackuphost.test.com: fbu_fill_bitmap (296) stream_offset=4890624, file_offset=8192, length=4608, fsize=4198912
12:16:58.025 [9232.5104] <2> 66015:bptm:9232:vmbackuphost.test.com: vxms_transadr: starting adr=236407
12:16:58.025 [9232.5104] <2> 66015:bptm:9232:vmbackuphost.test.com: vxms_transadr: bmw=0xffffff80, map_part=0, part_index=7387, pix=7387
12:16:58.025 [9232.5104] <2> 66015:bptm:9232:vmbackuphost.test.com: fbu_fill_bitmap (297) stream_offset=4890624, file_offset=0, length=8192, fsize=4198912
12:16:58.025 [9232.5104] <16> 66015:bptm:9232:vmbackuphost.test.com: fbu_fill_bitmap ERROR (296) stream_offset(4890624) + length(4608) > (297) stream_offset(4890624)
12:16:58.025 [9232.5104] <16> 66015:bptm:9232:vmbackuphost.test.com: fbu_scan_buf fbu_fill_bitmap failed: software error
12:16:58.025 [9232.5104] <16> 66015:bptm:9232:vmbackuphost.test.com: write_special_buf fbu_scan_buf failed : (2060022:software error)
12:16:58.025 [9232.5104] <16> 66015:bptm:9232:vmbackuphost.test.com: write_unknown_len_buf - write_special_buf failed: byteswritten: <0>, status: <0x1>,  (2060022:software error)
12:16:58.025 [9232.5104] <16> 66015:bptm:9232:vmbackuphost.test.com: impl_write_image: STAT contents:
12:16:58.025 [9232.5104] <16> 66015:bptm:9232:vmbackuphost.test.com: impl_write_image error exit (0 0x1 2060022:software error)
12:16:58.025 [9232.5104] <2> 66015:bptm:9232:vmbackuphost.test.com: pi_write_image_v7 exit (2060022:software error)
12:16:58.025 [9232.5104] <32> do_write_image: sts_write_image failed: byteswritten = 0, len = 128000
12:16:58.025 [9232.5104] <32> do_write_image: sts_write_image failed: error 2060022 (9699328 128000 0)

 


Environment



The issue has been reported in the following versions of NetBackup:

  • NetBackup 7.1.0.2 through 7.5.0.3

Cause



The issue was caused by NTFS compression on already compressed database files, which resulted in a HOLE extent whose InitializedSize is less than the DataSize.


Solution



The formal resolution for this issue (Etrack 2772726) is included in the following release: 

  •   NetBackup 7.5 Maintenance Release 4 (7.5.0.4)

Information on NetBackup 7.5.0.4 is available in the Related Article linked below.

Workaround:
Please contact Symantec technical support, referencing this document ID and the Etrack referenced below to request an Emergency Engineering Binary (EEB) bundle replacemane containing a fix for this issue:

  • For NetBackup 7.1.0.4, please reference Etrack 2677495
  • For NetBackup 7.5.0.3, please reference Etrack 2833456

Please note they are similar issues that are not currently solved and additional logs maybe needed.

 


Supplemental Materials

SourceETrack
Value2772726
Description

VMware incremental backups fail with status 13,84 to MSDP STU only


SourceError Code
Value13
Description

file read failed


SourceError Code
Value84
Description

media write error




Article URL http://www.symantec.com/docs/TECH190326


Terms of use for this information are found in Legal Notices