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.

Add a new idea Subscribe
Status Submitted
Workspace Defender Data Protect/Replica
Created by Guest
Created on Oct 2, 2026

RELATED IDEAS

Support Node-Targeted DataMover Scheduling for Backup & Restore on OpenShift / Kubernetes

Currently, DataProtect requires DataMover services to be running across all worker nodes in an OpenShift cluster. If a customer scopes DataMover pods to a subset of worker nodes using nodeSelector or tolerations in the DaemonSet specification, multi-stream and parallel namespace backup operations fail whenever a backup task is dispatched to a node lacking an active DataMover instance.

We request an enhancement allowing DataProtect to intelligently schedule backup and data movement tasks exclusively onto worker nodes where DataMover pods are running and healthy, rather than assuming cluster-wide availability.

Restricting DataMover pods to specific nodes is necessary for several real-world architectures:

  • Specialized Node Protection: Preventing backup overhead and noisy-neighbor workloads on GPU, AI/ML accelerator, or dedicated compute nodes.

Storage Fabric & Protocol Constraints: Accommodating environments where persistent volumes can only be attached to designated nodes, such as: IBM Block CSI deployments using Fibre Channel attachments, where storage connectivity is restricted to FC-equipped worker nodes. IBM Storage Scale configurations requiring specific kernel modules present only on designated worker nodes.

IBM Block CSI deployments using Fibre Channel attachments, where storage connectivity is restricted to FC-equipped worker nodes.

IBM Storage Scale configurations requiring specific kernel modules present only on designated worker nodes.

Idea priority High

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.