IC68814: OFFSITE RECLAMATION BEHAVIOR CHANGE OF DEDUPLICATED COPYPOOL NOT DOCUMENTED

IBM Tivoli Storage Manager V6.1 Fix Pack 4 (6.1.4) Server Downloads

APAR status

• Closed as documentation error.

Error description

• Post Deduplication:  It is now possible to have a dedup chunk
  logically removed from the primary pool though the chunk still
  exists.   Chunk dependencies are only checked within its pool
  before deletion.   An offsite volume bitfile/chunk may now be
  linked to a primary chunk that no longer exists thus requiring
  dedup'd offsite volumes to be brought onsite for reclamation.
  Customer/L2 Diagnostics:
  None
  
  Platforms affected:
  TSM 6.1, 6.2 all platforms
  
  Initial Impact: Low
  Additional Keywords: dedup ZZ61 ZZ62 vol chunk extent
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Tivoli Storage Manager server users.     *
  ****************************************************************
  * PROBLEM DESCRIPTION: See error description.                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  *
  

Problem conclusion

• The message text for ANR1163W will be updated with the
  following information:
  
  In the Explanation section, the following paragraph will be
  added:
  
  "If the files in the storage pool are deduplicated, they could
  be skipped due to the unavailability of an on-site copy.
  This can occur if the file has been logically deleted from
  all other storage pools due to policy settings but must
  remain in the offsite storage pool due to deduplication
  dependencies."
  
  In the User Response section, the following sentence will be
  added:
  
  "If the storage pool is deduplicated and all primary storage
  pool volumes are available, this is the recommended solution."
  
  This is the entire message now, including the added text:
  
  Explanation
  During processing of a MOVE DATA command or reclamation, the
  server determined that the indicated offsite volume contained
  one or more files that could not be moved.  One or more files
  could not be copied from the other available volumes.
  
  The server might not move some files if the storage pool is
  collocated and the volume being moved or reclaimed contains
  files that require different output volumes. The server will
  skip these files and no messages are issued identifying the
  skipped files. The files are skipped to honor the collocation
  attribute of the storage pool.
  
  If the files in the storage pool are deduplicated, they could
  be skipped due to the unavailability of an on-site copy. This
  can occur if the file has been logically deleted from all other
  storage pools due to policy settings but must remain in
  the offsite storage pool due to deduplication dependencies.
  
  System action
  None.
  
  User response
  Check for messages that indicate why files could not be moved.
  To complete the move operation, you have several options;
  
  Bring the volume back on-site and reissue a MOVE DATA command
  to reclaim the volume. If the storage pool is deduplicated and
  all primary storage pool volumes are available, this is the
  recommended solution. Make the primary volumes available and
  reissue a MOVE DATA command to reclaim the volume.
  Delete the files by using the DELETE VOLUME command.
  
  If the server is skipping files to honor the collocation
  attribute of the storage pool, run the MOVE DATA command,
  or wait until reclamation runs again. In either case, the
  server will move files to the appropriate output volumes
  until the volume being moved or reclaimed is empty. It might
  take more than one attempt to totally empty the volume.
  
  Recommendation:
  Apply fixing level when available. This
  problem is currently projected to be fixed
  in levels 6.1.4 and 6.2.2. Note that this is
  subject to change at the discretion of IBM.
  
  Affected platforms:  AIX, HP-UX, Sun 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

Applicable component levels