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 Future consideration
Workspace Storage Protect Family
Categories Spectrum Protect (Server)
Created by Guest
Created on Aug 23, 2019

RELATED IDEAS

Replicate retentionset and retention rules

I have found a pretty bad design flaw in the retentionset.
We use replication to move data off old SP servers to new hardware (or between OS).
If the source server have retentionsets, then the data is replicated to the target server but not the retentionrules and the retentionset.
Once data is in sync and remove replnode is run to move the node to the use the old target server as the new source server, then all retained data will expire next time expire inventory is run.
The manual states that you should recreate all retentionrules and retentionsets before expire inventory in the new source server is run but in the case where the old source server fo some reason is unavailable, then there is no way of knowing what rules and retset were in use there.
I also sent a note on this on the slack channel for sp_beta

Idea priority Urgent
  • Guest
    Reply
    |     Aug 28, 2019

    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.

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.