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 Submitted
Created by Guest
Created on Dec 3, 2025

Extend node replication to allow it to also replicate decommissioned state of nodes

In a replication environment (data and metadata is replicated from source to target server) it is currently not possible to "decomm node" for nodes that are replicated. One has to first disable replication for nodes before being able to decommission them (on the source server). In addition, afterwards, one has to separately do the same (disable replication and then decommission) for the nodes on the target server. This is inconvenient. It would be much better if we could decommission a node that is replicated and have that decommissioned state being replicated to the target server so that no extra steps are needed and expiration would automatically take care of deactivating and expiring data for decommissioned nodes also on the target server.

Idea priority High