Direct links to fixes
8.1.7.000-IBM-SPSRV-Linuxppc64le
8.1.7.000-IBM-SPCMS-WindowsX64
8.1.7.000-IBM-SPCMS-WindowsI32
8.1.7.000-IBM-SPCMS-Linuxx86_64
8.1.7.000-IBM-SPOC-WindowsX64
8.1.7.000-IBM-SPOC-Linuxx86_64
8.1.7.000-IBM-SPOC-Linuxs390x
8.1.7.000-IBM-SPOC-LinuxPPC64le
8.1.7.000-IBM-SPOC-AIX
8.1.7.000-IBM-SPSRV-WindowsX64
8.1.7.000-IBM-SPSRV-Linuxx86_64
8.1.7.000-IBM-SPSRV-Linuxs390x
8.1.7.000-IBM-SPSRV-AIX
IBM Spectrum Protect Server V8.1.6.X interim fix downloads
IBM Spectrum Protect Server V8.1 Fix Pack 7 (V8.1.7) Downloads
APAR status
Closed as program error.
Error description
After upgrading the Spectrum Protect server to version 8.1.6.0, any environment which uses sequential storage pool volumes might show various different read errors, which can result in extents or files being incorrectly marked damaged and volumes going into an unavailable state. VE incremental forever backups might fail with ANS4174E. Node replication might succeed but issue ANR1165E errors. Customer/L2 Diagnostics: Errors are seen when an attempt to read data from the volume is performed. Examples of these are : ANR9999D_0917394942 RtrvFramed(sstrans.c:6845) Thread<nnnn>: Premature end of segment group ANR9999D_2133050718 FileReadNC(pvrfil64.c:2169) Thread<nnnn>: Insufficient bytes read: expected bytes (48), actual bytes (0) ANR9999D_1001984741 BfEndToEndSinkFunc(bfddedup.c:1910) Thread<nnnn>: Magic number mismatch for self-describing data of chunk ANR1165E Error detected for file in storage pool <poolname> ANR1330E The server has detected possible corruption in an object that is being restored or moved ANR1331E Invalid frame detected ANR1308W Incorrect bytes read 48 for offset 48. ANR9999D_3746744715 AfReconstruct(afcreate.c:1920) Thread<2716114>: Unexpected result code (9976) from ssReconstruct. If the following error is encountered with these specific found length, type and size values, this APAR might apply. ANR2338E smtrans.c(7848): Invalid header received for object aaa, length bbb. Size (ccc), pushed (ddd), skipped (eee), status (fff). Found length (21317), type (46), size (4). (SESSION: xxx, PROCESS: yyy) Any of the above errors might lead to data being incorrectly marked as damaged and volumes being made unavailable. This can affect deduplicated and non-deduplicated volumes, so the damage can be seen at an extent and/or file level. If a trace including the AS trace flag shows the following message including a very large size similar to the one seen here, this APAR applies. hh:mm:ss.xxx [12345][asrtrv.c][1273][AsReadSeg]:Input Segment size reduced by 262096 bytes, size is now 18446744073709050732 There are additional specific errors which might occur during VE client backups or replication: This issue can affect backups from VE clients due to the inability to read data from a previous incremental forever backup : ANS0361I DIAG: VmVerifyConfirmNeededDats(): Error: Unable to find dat MegaBlock=nnn JobNumber=nnnn needed for restore. ANS9915E The guest VE_BACKUP_NODE is missing expected data files from the previous backups. The backup operation continues based on the setting of the VMVERIFYAction option ANS4174E Full VM backup of VMware Virtual Machine ' VE_BACKUP_NODE' failed with RC=4379 mode=Incremental Forever - Incremental, target node name=' VE_BACKUP_NODE', data mover node name='DATAMOVER_NODE' ANS1228E Sending of object ' VE_BACKUP_NODE' failed. ANS5226E The virtual machine backup operation failed. During node replication, the following might be seen. 1. The ANR1165E message is logged in the server activity log. For example: ANR1165E Error detected for file in storage pool MYPOOL : Node NODE1, Type Backup, File space \\NODE1\DRIVE\ fsId 1, File name \DIR1\FILE1. (SESSION: 123, PROCESS: 456) 2. The replicate node process completes successfully. For example: ANR0986I Process 456 for Replicate Node running in the FOREGROUND processed nnn items for a total of xxx bytes with a completion state of SUCCESS at HH:MM:SS. (SESSION: 123, PROCESS: 456) This ANR1165E error can be ignored when both conditions are met. In all cases, applying a fixing level for this APAR will prevent these errors. Contact IBM support for assistance in correcting the data incorrectly marked damaged and volumes erroneously set to unavailable status.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * All IBM Spectrum Protect server users. * **************************************************************** * PROBLEM DESCRIPTION: * * See error description. * **************************************************************** * RECOMMENDATION: * * Apply fixing level when available. This problem is currently * * projected to be fixed in levels 8.1.6.100 and 8.1.7. Note * * that this is subject to change at the discretion of IBM. * ****************************************************************
Problem conclusion
This problem was fixed. Affected platforms for reported release: AIX, Linux, and Windows.
Temporary fix
Comments
APAR Information
APAR number
IT26726
Reported component name
TSM SERVER
Reported component ID
5698ISMSV
Reported release
81L
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-10-24
Closed date
2019-01-03
Last modified date
2019-01-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
TSM SERVER
Fixed component ID
5698ISMSV
Applicable component levels
R81A PSY
UP
R81L PSY
UP
R81W PSY
UP
Document Information
Modified date:
28 September 2021