Direct links to fixes
7.1.10.000-TIV-TSMSRV-WIN
7.1.10.000-TIV-TSMSRV-SolarisSPARC
7.1.10.000-TIV-TSMSRV-Linuxx86_64
7.1.10.000-TIV-TSMSRV-Linuxs390x
7.1.10.000-TIV-TSMSRV-Linuxppc64
7.1.10.000-TIV-TSMSRV-HP-UX
7.1.10.000-TIV-TSMSRV-AIX
7.1.7.500-TIV-TSMSRV-WIN
7.1.7.500-TIV-TSMSRV-SolarisSPARC
7.1.7.500-TIV-TSMSRV-Linuxx86_64
7.1.7.500-TIV-TSMSRV-Linuxs390x
7.1.7.500-TIV-TSMSRV-Linuxppc64
7.1.7.500-TIV-TSMSRV-HP-UX
7.1.7.500-TIV-TSMSRV-AIX
8.1.1.400-IBM-SPSRV-WindowsX64
8.1.1.400-IBM-SPSRV-Linuxx86_64
8.1.1.400-IBM-SPSRV-Linuxs390x
8.1.1.400-IBM-SPSRV-Linuxppc64le
8.1.1.400-IBM-SPSRV-AIX
7.1.9.300-TIV-TSMSRV-WIN
7.1.9.300-TIV-TSMSRV-SolarisSPARC
7.1.9.300-TIV-TSMSRV-Linuxx86_64
7.1.9.300-TIV-TSMSRV-Linuxs390x
7.1.9.300-TIV-TSMSRV-Linuxppc64
7.1.9.300-TIV-TSMSRV-HP-UX
7.1.9.300-TIV-TSMSRV-AIX
7.1.9.300-TIV-TSMOC-Windows
7.1.9.300-TIV-TSMOC-Linuxx64
7.1.9.300-TIV-TSMOC-LinuxS390
7.1.9.300-TIV-TSMOC-LinuxPPC64
7.1.9.300-TIV-TSMOC-AIX
7.1.9.300-TIV-TSMCMS-Windows64
7.1.9.300-TIV-TSMCMS-Windows32
7.1.9.300-TIV-TSMCMS-Linuxx64
IBM Spectrum Protect Server V8.1.1.X interim fix downloads
IBM Spectrum Protect Server V7.1.7.X interim fix downloads
IBM Spectrum Protect Server V7.1.9.X interim fix downloads
IBM Spectrum Protect Server V8.1.6.X interim fix downloads
IBM Spectrum Protect Server V7.1 Fix Pack 10 (7.1.10.000) Downloads
APAR status
Closed as program error.
Error description
During the backup of a client using client-side deduplication the following may be seen in the activity log: 04/10/19 23:06:34 ANR9999D_0756002150 SdWriteDedupData(sdcreate.c:3416) Thread<149260>: 4096000 last bytes of buffer (196a21000, 4096000) is not consumed,first deduped chunk id 0, last 0. Index pairs: recorded ( 1120, 1119 ) vs processed ( 0, 0 ), leadinglinkchunk 0, paddinglinkchunk 0.(SESSION: 84879) The exact numbers of bytes, chunk IDs, and index pairs, as well as file and line number may vary based on the version of the Spectrum Protect server running at the time the error is encountered. When this error message occurs, the Spectrum Protect server encounters a boundary condition that may cause the storage of extents that are unrestorable. This boundary condition is encountered when the client references extents on the Spectrum Protect server that were removed during the course of the backup or archive operation. Due to improper return code handling on the Spectrum Protect server, the data extents that the Spectrum Protect server writes to storage are misaligned relative to the data stream from the client. If the client then retries the backup or archive, the backup or archive operation may succeed. In addition, any parallel or subsequent backup session by any client storing data in the same storage pool may reference the extents created by the session encountering the boundary condition which were created in error. As a result of referencing these extents, these objects may be unrecoverable. L2/Customer diagnostics: 1. Look for the above ANR9999D message in the server activity log. 2. Use AUDIT CONTAINER to validate the extents in the storage pool. If this APAR applies, AUDIT CONTAINER will mark extents damaged and the ANR9999D message above will be seen in the activity log. In addition, the following FFDC log entries may be seen: [04-12-2019 10:54:43.474][ FFDC_GENERAL_SERVER_ERROR ]: (sdutil.c:9467) Chunk Error digest recalculate mismatch chunkId: 0 Container: /tsm/dedup_ora009/48/00000000000048ee.dcf, Offset: 7391145984 The combination of #1 and #2 indicates the boundary condition creating unrecoverable extents has occurred. Note that this FFDC message may not be seen due to other FFDC messages obscuring the availability of this message in the existing FFDC log files. In particular, defect 183906 may flood the FFDC log and entries for this boundary condition may not be visible. Please contact IBM Support for a fix if the FFDC log is filled with the following message: [04-12-2019 22:49:23.935][ FFDC_GENERAL_SERVER_ERROR ]: (admactlg.c:5684) Client Type for node=DRAC_NIPRD_RAC_ORA is not system nor VM. Skipping. 3. This error can occur on a replication target server as a result of a REPLICATE NODE operation. These messages and diagnostics apply to a replication target server as well. Platform version affected: Spectrum Protect Server on all supported platforms
Local fix
Disable client deduplication by adding the following line to the client options file: DEDUPLICATION NO
Problem summary
**************************************************************** * USERS AFFECTED: * * All IBM Spectrum Protect server users of container storage * * pools and client-side deduplication * **************************************************************** * PROBLEM DESCRIPTION: * * See error description * **************************************************************** * RECOMMENDATION: * * Apply fixing level when available. After applying the fixing * * level use AUDIT CONTAINER to detect all damaged extents, and * * AUDIT CONTAINER with the ACTION=REMOVEDAMAGED parameter to * * delete all affected objects. This problem is projected to be * * fixed in the following levels: * * * * 7.1.7.500 * * 7.1.9.300 * * 7.1.10 * * 8.1.1.400 * * 8.1.6.200 * * 8.1.7.100 * * 8.1.8 * * * * Note that this is subject to change at the discretion of * * IBM. * ****************************************************************
Problem conclusion
This problem was fixed. Fixed platforms: AIX, Solaris, Linux, and Windows.
Temporary fix
Comments
APAR Information
APAR number
IT29362
Reported component name
TSM SERVER
Reported component ID
5698ISMSV
Reported release
71A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-06-06
Closed date
2019-06-06
Last modified date
2019-06-06
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
R71A PSY
UP
R71S PSY
UP
R71L PSY
UP
R71W PSY
UP
R81A PSY
UP
R81L PSY
UP
R81W PSY
UP
Document Information
Modified date:
27 September 2021