IBM Support

IT04803: DELETED CLIENT FILES ARE STILL MARKED AS ACTIVE ON THE SERVER

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After directory name is renamed between lower and upper case
    characters, previous directory backup is changed to INACTIVE
    version as expected after a full incremental backup. Then
    directory together with client files under this directory are
    deleted from client system. The client file backup version is
    still shown as ACTIVE on the server even a full incremental
    backup has been run. For example, query backup shows:
    
    tsm> q backup c:\39336_test\* -ina -subdir=yes
               Size        Backup Date                Mgmt Class
    A/I File
               ----        -----------                ----------
    --- ----
                 0  B  09/25/2014 16:00:06            TEST_MGMTC
    A  \\tsmdom\c$\39336_test\Data
                 0  B  09/25/2014 15:59:36            TEST_MGMTC
    I  \\tsmdom\c$\39336_test\data
                 1  B  09/25/2014 15:59:36            DEFAULT
    A  \\tsmdom\c$\39336_test\data\39336_test_file.txt
    
    This file no longer exists on the file system. A full
    incremental backup of this filespace does not mark this file as
    INACTIVE. When this condition occurs, the deleted files will not
    be expired.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Backup-archive client versions 5.5.3, 5.5.4, 6.1, 6.2, 6.3,  *
    * 6.4 and 7.1 running on the Windows and Mac platforms         *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See ERROR DESCRIPTION.                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply fixing level when available. This problem is currently *
    *                                                              *
    * projected to be fixed in levels 6.3.2.4, 6.4.3 and 7.1.2.    *
    *                                                              *
    * Note that this is subject to change at the discretion of IBM.*
    ****************************************************************
    *
    

Problem conclusion

  • The problem described in this APAR has been fixed so that it no
    longer occurs.
    

Temporary fix

  • 6.3.2.4 interim fix for Mac and Windows clients
    

Comments

APAR Information

  • APAR number

    IT04803

  • Reported component name

    TSM CLIENT

  • Reported component ID

    5698ISMCL

  • Reported release

    64W

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-10-08

  • Closed date

    2014-11-27

  • Last modified date

    2016-02-09

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

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

Modules/Macros

  • DSM      DSMC     DSMCSVC  DSMAGENT
    

Fix information

  • Fixed component name

    TSM CLIENT

  • Fixed component ID

    5698ISMCL

Applicable component levels

  • R63W PSY

       UP

  • R64W PSY

       UP

  • R71W PSY

       UP

  • R63M PSY

       UP

  • R64M PSY

       UP

  • R71M PSY

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"64W","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
08 January 2022