BUG REPORT: NetBackup 6.5 backups of Windows clients to PureDisk Deduplication Option (PDDO) fail with status 84 reporting 'software error'.
| Article:TECH62083 | | | Created: 2009-01-02 | | | Updated: 2009-01-02 | | | Article URL http://www.symantec.com/docs/TECH62083 |
Problem
BUG REPORT: NetBackup 6.5 backups of Windows clients to PureDisk Deduplication Option (PDDO) fail with status 84 reporting 'software error'.
Error
Status 83 media open error or status 84 media write error with "Critical bptm(pid=n) image write failed: error 2060022: software error"
Solution
Overview:
NetBackup 6.5 backups of Windows clients to PureDisk Deduplication Option (PDDO) fail with status 84 reporting 'software error' when encountering files on a Microsoft NTFS file system containing objectid's.
When the issue is seen, the Activity Monitor's Detailed status tab for the failed backup job will show the following line:
Critical bptm(pid=n) image write failed: error 2060022: software error
Media Server Log Files:
The bptm log will report the following at the point of failure (note also the file involved at point of failure):
09:24:50.989 [6948.8472] <16> 192.168.1.109: backupread_xlate stream Offset (0) !=save Offset (500)
09:24:50.989 [6948.8472] <16> 192.168.1.109: write_unknown_len_bufbackupread_xlate failed (0 0x1 2060022:software error)
09:24:50.989 [6948.8472] <16> 192.168.1.109: impl_write_image: STAT contents:
09:24:50.989 [6948.8472] <16> 192.168.1.109: impl_write_image error exit (0 0x12060022:software error)
09:24:50.989 [6948.8472] <2> 192.168.1.109: pi_write_image_v7 exit(2060022:software error)
09:24:50.989 [6948.8472] <32> do_write_image: sts_write_image failed:byteswritten = 0, len = 0
09:24:50.989 [6948.8472] <32> do_write_image: sts_write_image failed: error 2060022
pdplugin.log will report the following at point of failure:
07/01/08 09:24:50 [6948] [4] backupread_xlate stream Offset (0) != save Offset (500)
07/01/08 09:24:50 [6948] [4] write_unknown_len_buf backupread_xlate failed (0 0x1 2060022:software error)
07/01/08 09:24:50 [6948] [4] impl_write_image: STAT contents:
st_type=1 [TAR]
st_len=408
st_flags=0x1 [SIZE_UNKNOWN]
st_seqno=16
flags=5 [BACKUP_READ_FILE]
extents=[1]
offset=100352
length=161792
fname=example.dat
07/01/08 09:24:50 [6948] [4] impl_write_image error exit (0 0x1 2060022:software error)
07/01/08 09:24:50 [6948] [3] pi_write_image_v7 exit (2060022:software error)
Troubleshooting:
Upon examining the file involved with the failure (in this example the file in question is "example.dat"), an alternate data stream was found.
NetBackup 6.5 backups of Windows clients to PureDisk Deduplication Option (PDDO) fail with status 84 reporting 'software error' when encountering files on a Microsoft NTFS file system containing objectid's.
When the issue is seen, the Activity Monitor's Detailed status tab for the failed backup job will show the following line:
Critical bptm(pid=n) image write failed: error 2060022: software error
Media Server Log Files:
The bptm log will report the following at the point of failure (note also the file involved at point of failure):
09:24:50.989 [6948.8472] <16> 192.168.1.109: backupread_xlate stream Offset (0) !=save Offset (500)
09:24:50.989 [6948.8472] <16> 192.168.1.109: write_unknown_len_bufbackupread_xlate failed (0 0x1 2060022:software error)
09:24:50.989 [6948.8472] <16> 192.168.1.109: impl_write_image: STAT contents:
09:24:50.989 [6948.8472] <16> 192.168.1.109: impl_write_image error exit (0 0x12060022:software error)
09:24:50.989 [6948.8472] <2> 192.168.1.109: pi_write_image_v7 exit(2060022:software error)
09:24:50.989 [6948.8472] <32> do_write_image: sts_write_image failed:byteswritten = 0, len = 0
09:24:50.989 [6948.8472] <32> do_write_image: sts_write_image failed: error 2060022
pdplugin.log will report the following at point of failure:
07/01/08 09:24:50 [6948] [4] backupread_xlate stream Offset (0) != save Offset (500)
07/01/08 09:24:50 [6948] [4] write_unknown_len_buf backupread_xlate failed (0 0x1 2060022:software error)
07/01/08 09:24:50 [6948] [4] impl_write_image: STAT contents:
st_type=1 [TAR]
st_len=408
st_flags=0x1 [SIZE_UNKNOWN]
st_seqno=16
flags=5 [BACKUP_READ_FILE]
extents=[1]
offset=100352
length=161792
fname=example.dat
07/01/08 09:24:50 [6948] [4] impl_write_image error exit (0 0x1 2060022:software error)
07/01/08 09:24:50 [6948] [3] pi_write_image_v7 exit (2060022:software error)
Troubleshooting:
Upon examining the file involved with the failure (in this example the file in question is "example.dat"), an alternate data stream was found.
1. Within Windows Explorer,
right-click the file and choose Properties > Summary tab. Note
whether any of the fields such as Title, Subject, Author, Category, Keywords or
Comments are completed
2. From command-line,
run:
fsutil
objectid query example.dat
Object
ID
: a35eb8fb0f5add1196e2000c296db9bf
BirthVolume
ID : 261ec36f17c2874a92c7d1dd30550edb
BirthObjectId
ID : a35eb8fb0f5add1196e2000c296db9bf
Domain
ID
: 00000000000000000000000000000000
NOTE: if an object id is returned by the fsutil
command, then this file would trigger the backup
failure.
Resolution:
Symantec Corporation is committed to product quality and satisfied customers.
This issue is currently being considered by Symantec Corporation to be addressed in Point Patch NB_PDE_6.5.0.1.tar. Please see the document id 307927 in the Related Documents section below. Or visit:
http://support.veritas.com/menu_ddProduct_NBUESVR_view_DOWNLOAD.htm
Resolution:
Symantec Corporation is committed to product quality and satisfied customers.
This issue is currently being considered by Symantec Corporation to be addressed in Point Patch NB_PDE_6.5.0.1.tar. Please see the document id 307927 in the Related Documents section below. Or visit:
http://support.veritas.com/menu_ddProduct_NBUESVR_view_DOWNLOAD.htm
|
|
| Source | ETrack |
| Value | 1316686 |
| Description | PDDO backups fail w/status 84, reporting software error: "<32> write_data: image write failed: error 2060022" |
Related Articles
Legacy ID
306791
Article URL http://www.symantec.com/docs/TECH62083
Terms of use for this information are found in Legal Notices









Thank you.