IC91241: HSM FOR WINDOWS RECONCILIATION MIGHT CREATE ORPHAN IF FILE WAS RESTORED AND IS RE-MIGRATED DURING RECONCILIATION

IBM Tivoli Storage Manager (TSM) Client 7.1.0 Downloads
IBM Tivoli Storage Manager (TSM) Client 6.3.2 Downloads and READMEs

APAR status

• Closed as program error.

Error description

• When HSM for Windows reconciliation and migration run
  simultaneously files that were previously restored to the
  resident state can become orphans. The problem occurs if such a
  file is re-migrated during a short time interval between the end
  of reconciliation's file system scan and it's deletion of the
  file on the TSM server. If in this time interval the migration
  job re-stubs the file without sending the data to TSM server
  again, because it has detected that a valid file is stored on
  TSM server, the file becomes an orphan.
  The problem does not occur for files which have been recalled
  before the re-migration, because the file object id does not
  change in this case. Reconciliation does not select files on
  TSM server for deletion if the file on the TSM server and the
  corresponding resident file on the file system have the same
  file object id.
  
  TSM Versions Affected:
  Tivoli Storage Manager HSM for Windows versions
  5.5.0.0 - 5.5.3.1, 6.1.0.0 - 6.1.5.1,
  6.3.0.0 - 6.3.1.0, 6.4.0.0
  
  Customer/L2 diagnostics:
  
  
  Initial Impact:
  
  Additional Keywords: HSM for Windows, reconcile, orphan stubs
  

Local fix

• Do not run migration and reconciliation simultaneously.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: TSM HSM for Windows Client Versions          *
  *                 5.5.0.0 - 5.5.3.1, 6.1.0.0 -6.1.5.1,         *
  *                 6.3.0.0 - 6.3.1.0, 6.4.0.0                   *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * For detailed description see ERROR DESCRIPTION               *
  ****************************************************************
  * RECOMMENDATION: Apply fixing level when available. This      *
  *                 problem is currently projected to be fixed   *
  *                 in fixes later than 6.3.1 and later than     *
  *                 6.4.0, no interim fix is planned for versions*
  *                 5.5.x.x and 6.1.5.x                          *
  ****************************************************************
  

Problem conclusion

• In previous versions without this APAR fix an obsolete object
  was deleted in a single reconciliation process.
  With this APAR fix an object is deleted only after two
  reconciliation processes are run.
  After a stub is deleted, the first reconciliation marks the
  object on the Tivoli Storage Manager server. If the stub is not
  restored before the second reconciliation, the object is deleted
  from Tivoli Storage Manager server storage. If the stub is
  restored after the first reconciliation, the object is unmarked
  on the Tivoli Storage Manager server and is no longer a
  candidate for deletion. The reconciliation log file lists
  objects that are marked or unmarked or deleted during
  reconciliation.
  

Temporary fix

• see local fix
  

Comments

APAR Information

• 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 HSM FOR WIN

• Fixed component ID

  5698ICNCL

Applicable component levels

• R630 PSY

     UP

• R640 PSY

     UP