IBM Support

IT01994: MULTIPLE MOUNTS FOR SAME TAPE VOLUME OCCUR DURING SYSTEM STATE OR CLASSIC RESTORE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • During a classic restore, the Tivoli Storage Manager client
    compiles a list of objects to restore. The client may compile a
    non optimized list if the server-assigned restore order
    attribute for directories is not 0. This can happen if
    directories are located on tapes.
    
    Note: system state restore uses classic restore and thus is
    affected by this problem.
    
    Under the APAR condition, all the directories, sorted by name,
    are put at the top of the list of objects to restore, files
    follow directories in the correct restore order.
    As a result, directories are restored first and in case they are
    located on different tapes,  multiple undesired mounts may
    happen on server.
    The symptom, on the server, is seen as multiple mounts for the
    same volume during the restore session, e.g.:
    ..
    ANR0510I Session 47454 opened input volume F05056.
    ANR0510I Session 47454 opened input volume F06243.
    ANR0510I Session 47454 opened input volume F05056.
    ..
    This is seen in the initial phase of object restore, while there
    are only directory objects restored.
    
      Tivoli Storage Manager Versions Affected: Client versions
    6.2.4, 6.3.0 and newer
    
      Customer/L2 Diagnostics (If Applicable) You can verify the
    list of objects to restore from a trace generated with traceflag
    DIRDETAIL active. Search for
      "Restore List BEFORE sorting 'fs''hl''ll'..." and
      "Restore List after sorting 'fs''hl''ll'..."
    
      Initial Impact: Medium
      Additional Keywords: TSM performance 56470_1
    
      | MDVREGR 6.2.4.0-TIV_5698MCL |
    

Local fix

  • Include a wildcard in the restore command so NQR
    (no-query-restore) restore takes place. Under NQR condition, the
    server compiles the list of objects to restore and the symptom
    is circumvented.
    
    This workaround applies only for non system state restore
    operations. There is no workaround for system state restore.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Backup-archive client versions 5.5.4,        *
    *                 6.1.5, 6.2.4, 6.2.5, 6.3, 6.4 and 7.1 on     *
    *                 all 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.1. Note     *
    *                 that this is subject to change at the        *
    *                 discretion of IBM.                           *
    ****************************************************************
    *
    

Problem conclusion

  • The problem has been fixed so that directories are now sorted
    by restore order to minimize volumes mounting on the server.
    

Temporary fix

  • 6.3.2.3 for UNIX and Linux clients, 6.3.2.4 for Windows clients
    

Comments

APAR Information

  • APAR number

    IT01994

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    63L

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-05-23

  • Closed date

    2014-07-02

  • Last modified date

    2016-02-03

  • 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

  • R63A PSY

       UP

  • R63H PSY

       UP

  • R63L PSY

       UP

  • R63M PSY

       UP

  • R63S PSY

       UP

  • R63W PSY

       UP

  • R64A PSY

       UP

  • R64H PSY

       UP

  • R64L PSY

       UP

  • R64M PSY

       UP

  • R64S PSY

       UP

  • R64W PSY

       UP

  • R71A PSY

       UP

  • R71H PSY

       UP

  • R71L PSY

       UP

  • R71M PSY

       UP

  • R71S PSY

       UP

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

Document Information

Modified date:
08 January 2022