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 Future consideration
Created by Guest
Created on Apr 1, 2021

Support ILM pool migrations in stretched cluster without killing WAN

Currently when migrating files between replicated storage pools in a stretched cluster, intense load is experienced on the WAN. This is because the migration is essentially a copy of the files (hopefully?? respecting readReplicaPolicy) and the writes are all synchronous - in other words, the data migrated is re-replicated.

Given that both sites already have synchronized data, it is reasonable customer expectation that pool migration could simply move data locally, sparing the WAN.

We could almost accomplish this today this way: Bring down one site. Run mmapplypolicy on surviving site. Bring up the second site and start disks. Bring down the first site and restripe, correcting pool memberships. Bring the first site back up and start disks. But this would be very painful... If it were even possible to confine mmapplypolicy and mmrestripefs to only operate on some set of disks or failuregroups, that might be a start at a better procedure than I've outlined. But ultimately it would be nice of mmapplypolicy could handle this itself. (It would also be necessary to make sure worker threads are running in the same site as the disks.)

Idea priority High