IBM Support

IT06080: EXPLANATION OF THE "QUERY CONTENTS" OUTPUT AND "MOVE DATA" PROCESS WHEN DEDUPLICATION IS IN PLACE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • For a storage pool volume, where Deduplication is in place,  the
    "QUERY CONTENTS" command may return the message
    
    ANR2034E QUERY CONTENT: No match found using this criteria
    
    even if the volume is still storing data which can not be
    deleted (and which are "visible" by "QUERY OCCUPANCY").
    This is because some files are logically "deleted" but some of
    their data chunks, still saved on the volume , are referred to
    by other files.
    The chunks occupy space on volumes for Deduplication reference,
    however they are non-existent from the original object anymore
    logically.
    In this case, when using the "MOVE DATA" command in order to
    move the contents of a Deduplicated Storage Pool to  a
    non-Deduplicated Storage Pool, the "deleted" files are not
    written to new volume since they are not existed logically, and
    they are kept on original volumes for other files reference.
    This means that the MOVE DATA process will end successfully but
    no data will be moved to the new target volume.
    
    The option "FOLLOWLINKS=YES" of the "QUERY CONTENTS" command may
    help to understand if the volume contains this kind of file
    references.
    For example running the Server command
    
    "QUERY CONTENTS X:\TSMDEDUPLICATED\1234DFB.BFS FOLLOWLINKS=YES"
    
    you will obtain an output similar to the following:
    
    Node Name   Type     Filespace       Hexadecimal    FSID
                         Name            Filespace
                                         Name
    ----------  ------   -----------     -----------    ----
    NODE01      Bkup     \\abcd\c$       12345678       18
    
    
    Client's           Hexadecimal           Aggregated?
    Name for File      Client's Name
                       for File
    ---------------    ----------------      -------------
    \MYFILE\FILE.MDB   12345678910111213141  No
    
    
    Stored Size        Segment      Cached   Linked
                       Number       Copy?
    -----------        -------      -------  -------------
    1.80 M                          No       Yes
    
    
    Moving data inside the same Deduplicated Storage Pool, will work
    without any problems.
    
    The Tivoli Storage Manager documentation will be improved to
    detail the above options and scenario,  highlighting that when
    the volume still contains links to other file,  as shown by
    "FOLLOWLINKS=YES"  option, the volume must not be deleted.
    
    
    
    
    Tivoli Storage Manager Versions Affected:
    Tivoli Storage Manager Server all supported versions
    
    
    
    
    Initial Impact:
    Medium
    
    
    
    
    Additional Keywords:
    TSM query contents empty output move data followlinks yes query
    occupancy
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Tivoli Storage Manager server users.                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See error description.                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * This problem is projected to be fixed in a future version of *
    * the Tivoli Storage Manager server. Note that this is subject *
    * to change at the discretion of IBM.                          *
    ****************************************************************
    

Problem conclusion

  • In the Administrator's Reference, the MOVE DATA command will be
    updated to include the following text:
    
    "A volume in a deduplicated storage pool might contain files
    that are logically deleted but are still linked by files on
    other volumes. If you use the MOVE DATA command to move the
    contents of a deduplicated storage pool volume to a
    non-deduplicated storage pool, the logically deleted files are
    not written to the new volume since they do not exist logically.
    The deleted files are kept on the original volumes for other
    files to reference. The MOVE DATA process ends successfully but
    none of the deleted files are moved to the new target volume and
    the source volume is not deleted. You can issue the QUERY
    CONTENT command with the FOLLOWLINKS=YES or
    FOLLOWLINKS=JUSTLINKS parameter to verify whether the volume
    contains files that are linked by files on other volumes."
    
    Affected platforms: AIX, HP-UX, Solaris, Linux, and Windows.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT06080

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    63W

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-12-15

  • Closed date

    2015-01-27

  • Last modified date

    2015-01-27

  • 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

  • R63A PSY

       UP

  • R63H PSY

       UP

  • R63L PSY

       UP

  • R63S PSY

       UP

  • R63W PSY

       UP

  • R71A PSY

       UP

  • R71H PSY

       UP

  • R71L PSY

       UP

  • R71S PSY

       UP

  • R71W 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":"63W","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
27 January 2015