IBM Support

IT26966: CLIENT RESTORE OF DATA WHICH HAS BEEN IMPORTED TO AN AIX SERVER CAN FAIL

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • Error Description:
    
    Performing an export of client data to a Spectrum Protect server
    which is then imported to a Spectrum Protect server hosted on an
    AIX platform could result in the restore of the data by the
    backup archive client to subsequently fail.
    
    
    Customer/L2 Diagnostics (If Applicable)
    
    During the client restore, the following two different failures
    have so far been observed for different clients :
    
    1) ANS4020E The data format for object 'filename' is unknown.
    The unknown format usually occurs when the file was backed up or
    archived by a later version of IBM Spectrum Protect.
    
    2) ANS8013I Invalid encryption key password
    The encryption message will continue to prompt for the key for
    certain files. Other encrypted files might get restored with
    this key perfectly ok.
    
    
    This happens for objects that don't have a correct object
    header, which is a result of the exported data.
    
    From a client service trace, you will see the following from a
    failing restore :
    
    09/19/2018 14:27:08.504 [000920] [1996] :
    ..\..\common\com\session.cpp(2090):   Length:   654 Code:
    00000007 Type:    <- Data
    Contents of verb (0x7) Data, length: 654:
    09/19/2018 14:27:08.504 [000920] [1996] :
    ..\..\common\ba\restcore.cpp(2905): fdb: vers: 5, comp: 00,
    encr: 00, checksum: 00000000
    ...
    
    Seeing "fdb: vers: 5, comp: 00, encr: 00, checksum: 00000000"
    means that the client build is 0, which is not correct and so
    the File Decode Block (FDB)  is not correct.
    
    Also, the  Stream Decode Block (SDB) doesn't have the correct
    version information :
    ...
    09/19/2018 14:27:08.504 [000920] [1996] :
    ..\..\common\fio\fileio.cpp(2824): fioWrite(): File 'filename':
    Obtained Data Main Header
    
       SDB Version = '00'
    ...
    
    The problem is that the server has sent extra bytes of data in
    the FDB when encountering an object header size of 0. There can
    be 1, 2, or 3 extra bytes sent.
    
    A server side trace using classes "SESSION SESSIOND" will show
    the following :
    
    07:41:35.889 [279][smtrans.c][3345][SmSendData]: (1)sending
    rc(0) dataPtr(a00000003e0d050) dataLen(262058) rtrvLen(262061)
     newRetrieve(1) sendPartialData(0) noQueryRestore(0)
    sendClientHdr(0)
    ==> objectHeaderSize(0) verbHdrPushLen(3) objectHdrSkipped(3)
     metaDataSize(-1), dataType(1)
    07:41:35.908 [279][smtrans.c][3358][SmSendData]: Dumping
    addr=0xa00000003e0d050, len=0x190, contents=
    +0x0000  FFFFFFFF FFFFFFFF 00000000 00000000  ................
    +0x0010  00000000 00000000 00000000 00000000  ................
     -- 22 duplicate lines skipped --
    +0x0180  00000000 00000000 00000000 00000000  ................
    07:41:35.934 [279][smtrans.c][3643][SmSendData]:(1)1a:
    hdrSegLen(1) verbHdrPushLen(4) skipped(3)
    07:41:35.938 [279][smtrans.c][3673][SmSendData]:(1)1:
    verbType(2) verbLen(2) verbSize(4)
    07:41:35.942 [279][smtrans.c][3720][SmSendData]:(1)1b:
    objectHeaderSize(0) verbLen(2)
    07:41:35.947 [279][smtrans.c][4219][SmSendData]:(1)1e:
    objectHeaderSize(0) NQR(0) state(0)
    ==> 07:41:35.951 [279][smtrans.c][4279][SmSendData]:(1)1eb:
    objectHeaderSize(0) oldVerbHdrPushLen(4)
    
    The first
    ==> objectHeaderSize(0) verbHdrPushLen(3) objectHdrSkipped(3)
    verbHdrPushLen could also be 1 or 2
    
    
    The second
    ==> 07:41:35.951 [279][smtrans.c][4279][SmSendData]:(1)1eb:
    objectHeaderSize(0) oldVerbHdrPushLen(4)
    oldVerbHdrPushLen is 4
    
    Having an object header size of 0 is only found when data has
    been imported to a server and an incorrect attempt is made to
    interpret the data which results in additional byte(s) being
    sent to the client in the FDB.
    
    IBM Spectrum Protect Versions Affected:
    Spectrum Protect Server versions 7.1 and higher or 8.1 and
    higher on AIX only.
    
    Initial Impact:
    Medium
    
    Additional Keywords:
    baclient, restore, systemstate, corrupt, header, TS000849019
    

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 7.1.10 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.
    Platforms fixed:  AIX.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT26966

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    81A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-11-14

  • Closed date

    2018-12-03

  • Last modified date

    2018-12-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



Document information

More support for: Tivoli Storage Manager

Software version: 81A

Reference #: IT26966

Modified date: 03 December 2018


Translate this page: