IC77801: GENERATE BACKUPSET STORES INCOMPLETE SET OF FILES IN THE BACKUP SET WITHOUT ERROR WHEN RUNNING WITH ANOTHER DATA MOVEMENT PROCES

APAR status

• Closed as program error.

Error description

• When GENERATE BACKUPSET and SPACE RECLAMATION run at the same
  time in TSM Server 6.x, GENERATE BACKUPSET completes without any
  errors even though it actually stores incomplete set of backup
  files into the backup set.
  
  Here is steps we found the problem.
  1. Do backup file01 in volume vol01
  2. Do backup file02 in volume vol02
  3. Do backup file03 in volume vol02
  4. Delete backup file02 from vol02
  5. Run SPACE RECLAMATION for vol02 and GENERATE BACKUPSET at the
     same time.
  6. GENERATE BACKUPSET is successfully done with no error.
  7. Run QUERY BACKUPSETCONTENTS, then notice only file01 is in
     the backup set even though file01 and file03 should be there.
  
  GENERATE BACKUPSET fails to retrieve file03 when it is just
  deallocated by SPACE RECLAMATION.  The expected behavior is that
  GENERATE BACKUPSET should fail with an error because  it could
  not write the file to the backup set.
  
  
  Versions affected:
  TSM Server 6.x on all supported platform
  
  
  Additional Keywords
  None.
  
  
  Additional L2 info:
  The following trace is found in the trace file with BKSET
  BFRTRV.
  ---
  hh:mm:ss [nnn][bfrtrv.c][1872][bfRtrv]:Exiting, bitfile nnnnnn,
  rc=4.
  ---
  This trace indicates the GENERATE BACKUPSET could not retrieve
  the file because it was already deallocated by the reclamation.
  
  
  Initial Impact:
  Medium
  

Local fix

• Avoid running GENERATE BACKUPSET when any other data movement
  processes are running.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Tivoli Storage Manager V6.2 server       *
  *                 users.                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION: See error description.                  *
  ****************************************************************
  * RECOMMENDATION: Apply fixing level when available. This      *
  *                 problem is currently projected to be fixed   *
  *                 in level 6.2.4. Note that this is            *
  *                 subject to change at the discretion of IBM.  *
  ****************************************************************
  *
  

Problem conclusion

• This problem was fixed.
  Affected platforms:  AIX, HP-UX, Solaris, Linux,  and Windows.
  

Temporary 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 SERVER

• Fixed component ID

  5698ISMSV

Applicable component levels

• R62A PSY

     UP

• R62H PSY

     UP

• R62L PSY

     UP

• R62S PSY

     UP

• R62W PSY

     UP