IBM Support

IT12381: BACKUP FAILS WHEN PROCESSING A MIGRATED FILE WHOSE ATTRIBUTES HAVE CHANGED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When performing a backup of a space-managed filesystem, the
    client will check the attributes of all migrated files to
    determine if any of these attributes (eg. permissions) have
    changed.  If the attributes have changed for any of the migrated
    files, the client will, by default, attempt to update the
    corresponding attributes for those files on the server.  There
    is a parameter (SKIPMIGRATED) that, when enabled, prevents the
    client from attempting to backup or update the attributes for
    any migrated files.  However, when the backup operation
    encounters a migrated file whose attributes have changed,
    instead of skipping the attempted update of this file as
    expected, the backup of the entire filesystem is aborted.  When
    this occurs, the following error message may be generated
    against the affected filesystem:
    
       ANS1999E Incremental processing of '/hsmfs' stopped.
    
    There are some instances where the backup operation may fail and
    no corresponding error messages are generated.  The logs will
    show the backup of the filesystem is initiated and the ending
    statistics, but no messages indicating whether the backup of the
    filesystem completed successfully or not:
    
       Incremental backup of volume '/hsmfs'
    
       Total number of objects inspected:           10
       Total number of objects backed up:            0
       Total number of objects updated:              0
       Total number of objects rebound:              0
       Total number of objects deleted:              0
       Total number of objects expired:              0
       Total number of objects failed:               0
       Total number of objects encrypted:            0
       Total number of objects grew:                 0
       Total number of retries:                      0
       Total number of bytes inspected:           1.46 GB
       Total number of bytes transferred:            0  B
       Data transfer time:                        0.00 sec
       Network data transfer rate:                0.00 KB/sec
       Aggregate data transfer rate:              0.00 KB/sec
       Objects compressed by:                        0%
       Total data reduction ratio:              100.00%
       Elapsed processing time:               00:00:03
    
    A SERVICE trace of the backup operation will show entries
    similar to the following:
    
       backmigr.cpp( 983): procBackMigr(/hsm/dir/file.txt): file is
       skipped due to SKIPMIGRATED option, request(0)!
       txnprod.cpp(2697): tlAbort: Aborting backup transactions
    
    Tivoli Storage Manager Versions Affected:
    o 7.1 B/A client on AIX and Linux x86, which is the release
      where the SKIPMIGRATED option was first documented
    o previous client releases on AIX and Linux, where the
      undocumented SKIPMIGRATED option was used under the direction
      of IBM Support
    
    Initial Impact:
    High
    
    Additional Keywords:
    hsm ans1999 aborted skip skipped skipmigrate
    

Local fix

  • Temporarily disable the SKIPMIGRATED parameter by adding the
    following entry to the dsm.opt file:
    
       SKIPMIGRATED NO
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Tivoli Storage Manager backup-archive client versions 6.3,   *
    * 6.4 and 7.1 running on AIX and Linux platforms while backing *
    * up an HSM managed file system.                               *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See ERROR DESCRIPTION.                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply fixing level when available. This problem is currently *
    * projected to be fixed in level 7.1.6.                        *
    * Note that until this level is available, this information is *
    * subject to change at the discretion of IBM.                  *
    ****************************************************************
    

Problem conclusion

  • Upon the fix, the incremental backup operation (with
    "SKIPMIGRATED=yes" setting) finishes successfully. All the
    eligible files (if any) are backed up. All the HSM stubs
    encountered (if any) are skipped as per the SKIPMIGRATED option
    setting.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT12381

  • Reported component name

    TSM CLIENT

  • Reported component ID

    5698ISMCL

  • Reported release

    71A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-11-20

  • Closed date

    2016-01-11

  • Last modified date

    2016-03-15

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • dsmc
    

Fix information

  • Fixed component name

    TSM CLIENT

  • Fixed component ID

    5698ISMCL

Applicable component levels

  • R71A PSY

       UP

  • R71L PSY

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"71A","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
15 March 2016