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 Nov 29, 2016

Allow individual filespaces to be decommissioned - specifically for use with NAS nodes and Netapp NDMP backups

Currently TSM (Spectrum Protect) offers two DECOMMISSION commands which are DECOMMISSION NODE and DECOMMISSION VM. However for NAS (NDMP) backups typically a node will be configured for each filer which will have numerous volumes being backed up via it. As is the case at EBRD over time a lot of volumes have been moved to different filers which then cause the old file spaces on the original filer node to show as not having been backed up, the same is true if a volume becomes obsolete and no longer requires backup. Over time it then becomes increasingly difficult to see the wood for trees in terms of filespaces that should be being backed up but have stopped working vs filespaces that have genuinely been "decommissioned" and can be safely ignored.

Idea priority High