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 Feb 10, 2022

SP move data out of CLOUD containers

Once TSM/SP data ends up in a CLOUD pool, there is no way to every move it anywhere else. We should be able to move data out of a cloud pool.

MOVE NODADATA might be relevant, but would only work if you could specify source and destination pools. That's a big change.

MOVE CONTAINER to another pool would not be right, because you might move half of an object. This might be okay if there were code overlaps with tiering stgrules to ensure whole objects got moved, etc.

Changing TIER stgrules to allow CLOUD as a source pool would probably be the best option. This would already do everything desired/needed. The main concern with this now is the data recall costs, but that would be expected when moving from CLOUD to DIRECTORY, or CLOUD to CLOUD pools. It might require STGPOOLDIRs on both source and target pools of some multiple of the largest single object in the pool for proper chunk reassembly.

Idea priority High
  • Guest
    Reply
    |
    Feb 11, 2022

    This request may not be delivered within the release currently under development, but the theme is aligned with the current multi-year strategy. IBM may consider and evaluate any RFE Community feedback for this request through activities such as voting. IBM will update this request in the future.