IC88831: THE OFF-SITE RECLAMATION PROCESS MIGHT INVALIDLY MARK ON-SITE COPIES AS DAMAGED IF THE OFFSITE STORAGE POOL HAS BEEN DEDUP

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • If an off-site copy storage pool has been enabled for
    deduplication, and off-site reclamation is run, it might result
    in primary storage pool copies being marked damaged. This is a
    false report since the on-site copies are not really damaged.
    The following error
    message will be issued if this problem is being encountered:
    11/09/2012 11:59:01      ANR4895E Deduplicated bitfile XXXXXXXX
    on volume
                              XXXXXXX has invalid links. (SESSION:
    XXX, PROCESS: XX)
    The key element here is that the process # will be from the
    offsite reclamation. Any subsequent reclamation process for
    either the offsite process, or on-site, will result in either
    ANR4895E messages or a ANR1167E message indicating that the
    files in the primary pool were marked as damaged.
    11/08/2012 18:48:08      ANR1167E Space reclamation for offsite
    volume
                              XXXXXXXX cannot copy damaged file in
    storage
                              pool XXXXXX: Node XXXXX, Type XXXXX,
    File
                              space XXXXXXX,fsId XX, File name
    XXXXXXXX.
                             (SESSION: XX, PROCESS: XX)
    Initial Inpact: Medium
    Versions affected: All platforms on version 6.1, 6.2 or 6.3.
    

Local fix

  • 1) If files in the primary storage pool have been marked
    damaged, those volumes can be audited with AUDIT VOLUME
        to reset the damaged status.
    2) Do not have an offsite copy storage pool enabled for
    deduplication:
        UPDATE VOLUME * WHERESTG=<Offsite copy pool name>
    ACCESS=READONLY
    Note: Due to apar IC88411, you need to be at 6.3.3.0 of the
    TSM Server before running the AUDIT VOLUME command.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Tivoli Storage Manager server users.     *
    ****************************************************************
    * PROBLEM DESCRIPTION: See error description.                  *
    ****************************************************************
    * RECOMMENDATION: Apply fixing level when available. This      *
    *                 problem is currently projected to be fixed   *
    *                 in levels 6.2.6 and 6.3.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 number

    IC88831

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    63W

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-12-04

  • Closed date

    2013-01-21

  • Last modified date

    2013-01-23

  • 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

  • R63A PSY

       UP

  • R63H PSY

       UP

  • R63L PSY

       UP

  • R63S PSY

       UP

  • R63W PSY

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

Tivoli Storage Manager

Software version:

63W

Reference #:

IC88831

Modified date:

2013-01-23

Translate my page

Machine Translation

Content navigation