IBM Support

IT25037: LOCAL PROTECT STGPOOL EXHIBITS POOR PERFORMANCE FOLLOWING PRIOR LOCAL PROTECT STGPOOL FAILURE OR CANCELATION DURING RECLAMATION

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • PROTECT STGPOOL processing to a local container-copy storage
    pool may exhibit poor performance following a prior local
    PROTECT STGPOOL process that was canceled or failed during
    reclamation phase processing. When a local PROTECT STGPOOL
    process terminates before completing reclamation, the database
    is not updated to indicate the last protection date for new
    extents. This can cause the next PROTECT STPGOOL process to scan
    all the containers in the pool to find those that actually have
    extents on them that need processing. When the prior PROTECT
    STGPOOL process completes successfully, the date is updated and
    only containers with new data since that date will be analyzed.
    

Local fix

  • Run local PROTECT STGPOOL with the reclaim=no option so that the
    protect phase can complete and the database can be updated with
    the last protection date. Then run protect with reclaim=only or
    onlylimited to reclaim as many volumes as possible.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All IBM Spectrum Protect server users of container-copy      *
    * storage pools                                                *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See error description.                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply fixing level when available. This problem is currently *
    * projected to be fixed in levels 7.1.10 and 8.1.6. Note that  *
    * this is subject to change at the discretion of IBM.          *
    ****************************************************************
    

Problem conclusion

  • The problem was fixed.
    
    Affected platforms: AIX, Linux, Solaris, Windows
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT25037

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    81A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-05-10

  • Closed date

    2018-07-10

  • Last modified date

    2018-07-10

  • 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



Document information

More support for: Tivoli Storage Manager

Software version: 81A

Reference #: IT25037

Modified date: 10 July 2018


Translate this page: