IBM Support

IT04919: SOME VOLUMES IN DEDUP STORAGE POOL ARE ALWAYS SKIPPED DURING RECLAIM ALTHOUGH THEY ARE BACKED UP

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Some volumes in dedup storage pool are consistently skipped
    during reclaim although they are valid candidates for
    reclamation.  The data in those volumes are backed up from
    primary pool to copy pool prior to reclaim.  Running BACKUP
    STGPOOL does not correct the problem.  Below message is reported
     during reclamation:
    
    ANR3633I Process <process number> skipped volume <volume name>
    because the volume contains files that have not been backed up.
    
    
    There are below message in trace;
    
    17:01:43.553
    [537369][afbackup.c][2054][AfGetBackupOptimization]:Initial
    backup optimization data: VolId=<Volume ID>,
    CopyPoolId/ActiveDataPoolId=-1, Start=1, Offset=0
    17:01:43.553
    [537369][afbackup.c][2166][AfSetBackupOptimization]:Updated
    backup optimization data: VolId=<Volume ID>,
    CopyPoolId/ActiveDataPoolId=-1, Start=2, Offset=0
    
    The problem in 7.1.0.100 was introduced with IT02717. When there
    are deleted bitfiles on the volume, the BACKUP STGPOOL will no
    longer clear the ANR3633I condition and volumes can become
    permanently stuck being unable to reclaim.
    
    | MDVREGR 7.1.0.100 |
    

Local fix

  • Users may temporarily disable DEDUPREQUIRESBACKUP using SETOPT
    DEDUPREQUIRESBACKUP NO. run reclamation to allow it to free up
    needed volumes, and re-enable DEDUPREQUIRESBACKUP using SETOPT
    DEDUPREQUIRESBACKUP YES.  Users should always ensure that
    regular storage pool backups are occurring to minimize the risk
    of data loss.  Alternatively, users may run MOVE DATA to empty a
     volume and DELETE VOLUME to delete it.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Tivoli Storage Manager 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.1.100 and      *
    * 7.1.3.  Note that this is subject to change at the           *
    * discretion of IBM.                                           *
    ****************************************************************
    

Problem conclusion

  • The problem was fixed.
    Affected Platforms: AIX, HP-UX, Solaris, Linux, and Windows.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT04919

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    71L

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-10-16

  • Closed date

    2014-10-27

  • Last modified date

    2015-01-28

  • 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

  • R71H PSY

       UP

  • R71L PSY

       UP

  • R71S PSY

       UP

  • R71W PSY

       UP



Document information

More support for: Tivoli Storage Manager

Software version: 7.1.3

Reference #: IT04919

Modified date: 28 January 2015