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 Jan 20, 2016

mark recovery points as corrupt if volume/container is irretrievably destroyed or damaged

If a volume is destroyed, is audited with discarddata=yes or otherwise cause to or found to be damaged but cannot be repaired, there are potentially corrupt recovery points. In the case of TSM for VE, the ideal behavior would be to mark all potentially corrupt recovery points as dirty (based upon the backup date of data stored in the volume) as well as signal that the next backup of the VM should take a full backup (as if the CBT was incorrect, which it is as it may not reach back to the date of the data in the volume). This behavior should reach any type of recovery point, such as any that may come up with future logical backupset features which create logical recovery points out of physical backups.

Idea priority Medium