Skip to Main Content
IBM System Storage Ideas Portal


This portal is to open public enhancement requests against IBM System Storage products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Created by Guest
Created on May 3, 2018

audit container markdamaged needs to update inventory objects as damaged

Any process that marks extents damaged should queue a process to mark those objects damaged which rely on the extents.

AUDIT CONTAINER ACTION=MARKDAMAGED only marks extents damaged, so inventory objects stay not-damaged. Even later, if they are accessed, and the access fails because of the damaged extents, the inventory object is not marked damaged.

Because of that, replication and re-ingest do not repair container pools.

ACTION=DELETEDAMAGED reaches up to the object level. Some of that code could be reused.

If changing MARKDAMAGED is undesirable, then new options for MARKINVDAMAGED and REMINVDAMAGED could be used to shift the identification of invo to the mark instead of the remove.

Idea priority High
  • Guest
    Reply
    |
    Sep 10, 2018

    This is part of the "PROTECT TO THE CLOUD" enhancement wishlist, which was confirmed as *not* part of any plans through 2019.

  • Guest
    Reply
    |
    May 23, 2018

    At some point in the past, this was the strategy. It even exists in whitepapers from IBM. Many are gone in the great cleanup; however this one remains until someone edits or deletes it:

    http://www-01.ibm.com/support/docview.wss?uid=swg22003019
    "If a deduplicated extent is marked as damaged, IBM Spectrum Protect can take steps to repair that extent, for example, by bringing it back from a replicated copy if the PROTECT STORAGEPOOL or REPLICATE NODE commands are used."

    Dawson also was under the impression this was the functionality, and we started down the path of finding out why it was not happening. Once it was found to not be the case, it quickly changed to "Make an RFE and vote on it."

    Colvig (ex) thought this was omitted due to cloud cost concerns, but the decision happened long before object storage was being designed.

    Ayres (L2) thought this was omitted due to concerns of having data multiple-reingested, but that is no different of a concern than with multiple parallel backups of any type.

    Thompson (STSS) believes that a multi-week outage and a complex, manual procedure is a "performance" issue and not a functional issue. No running environment would accept that justification.

    Thompson also reported that PROTECT STG to VTL would be a good option, which is also not supported due to all of the limits on PROT STG.

    I feel this RFE is something that needs higher priority than "long term goals". This should have happened before PROTECT STG.

  • Guest
    Reply
    |
    May 7, 2018

    This request may not be delivered within the release currently under development, but the theme is aligned with the current multi-year strategy. IBM may consider and evaluate any RFE Community feedback for this request through activities such as voting. IBM will update this request in the future.

  • Guest
    Reply
    |
    May 4, 2018

    There is no way that customers coming from VTL environments where damaged objects on a volume can be dealt with automatically are going to accept IBM Spectrum Protect Directory Container pools as an adequate replacement with this defect in place. Yes this is a defect and needs to be fixed via patching as soon as possible.