IBM Support

IT18676: MODIFICATION TIME (MTIME) OF THE RESTORED DIRECTORY MAY DIFFER FROM THE ORIGINAL ONE WHEN DOING RESTORE BACKUPSET.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After completing restore backupset by the following command for
    example,
    # dsmc restore backupset /source_filespace/
    /destination_directory/ -backupsetname=backupset_name
    modification timestamp (mtime) of a restored directory in
    destination_directory might be set to the different timestamp
    from the original one in source_filespace.  The mtime might be
    changed to new timestamp when child objects under the directory
    were just restored.
    This symptom might occur only when the parent directory and
    child objects were restored in the following order:
    Restoring /parent -> /parent/child/file -> /parent/child/
    It is expected that modification timestamp (mtime) of the
    parent directory is also restored as it is in source_filespace.
    IBM Spectrum Protect Versions Affected:
    Tivoli Storage Manager and IBM Spectrum Protect Client all
    supported versions on all supported platform
    Initial Impact:
    Low
    

Local fix

  • None. It can be safely ignored because no data is corrupted but
    only mtime of the restored directory might be set to new
    timestamp.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Spectrum Protect backup-archive client versions 6.4.3,       *
    * 7.1.0-7.1.6 and 8.1.0 on all Unix and Linux platforms.       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See ERROR DESCRIPTION.                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply fixing level when available. This problem is projected *
    * to be fixed in level 7.1.8 and 8.1.2. Note that this is      *
    * subject to change at the discretion of IBM.                  *
    ****************************************************************
    

Problem conclusion

  • After the fix, the mtime of a restored directory will be always
    accurate i.e. the mtime taken at the time of the backup
    operation.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT18676

  • Reported component name

    TSM CLIENT

  • Reported component ID

    5698ISMCL

  • Reported release

    64L

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-01-06

  • Closed date

    2017-03-16

  • Last modified date

    2017-04-07

  • 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

  • R81A PSY

       UP

  • R81L PSY

       UP

  • R81M PSY

       UP

  • R81H PSY

       UP

  • R81S 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":"64L","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
07 January 2022