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 Dec 2, 2022

RELATED IDEAS

Provide additional protection when using the decommission command against Oracle or DB2 nodes.

Spectrum Protect Oracle and DB2 client decommission can lead to immediate data expiration and data loss.  Due to the copygroup settings required for Oracle and DB2, the risk of using the decommission node command can inadvertently lead to data loss.  This is due to the IBM recommended copygroup setting  which states to have version deleted set to 0 and retain only set to 0 to allow the Oracle and DB2 to manage the retention.   When the 'decommission node' command is run, all backup objects are switched from active to inactive.  This not only makes the data inaccessible to Oracle and DB2, it also forces the data to adhere to the retention set in the backup copygroup which in this case is 0 days.  The next expiration process will delete all data as a result.

 

Ideas to consider:

- IBM should consider disallowing of the 'decommission node' command for nodes containing Oracle and DB2 backups.

- IBM could add more explicit warnings when decommissioning a node that contains Oracle/DB2 backup data.

- Ensure the documentation reflects the risk in the 'decommission node' documentation online.

Idea priority Urgent
  • Admin
    Juan Carlos Jimenez Fuentes
    Reply
    |     Dec 9, 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.

  • Guest
    Reply
    |     Dec 5, 2022

    I have been thinking about this a bit. The main value of decommission node is the simple management of the various steps of decommissioning a node, most notably the graceful expiration of backups. I am speculating if the best way to keep the value of this command for all node types while still to provide extra protection is to treat "known good" node types (b/a client, VE, domino, MSEX and MSQL) one way, and for any other node type offer a chance to cancel out or provide a expiration period. Additionally, for known good types, any setting retention period lower than a pre-specified period (such as 7 days) can generate the same option. My logic is this: While we know Oracle and DB2 self-manage their retention, there is no reason any custom node type or even a standard node type could not be used with an application that self-manages it retention via the active/inactive flag. By checking against a white list of node types that work well with decommission AND checking for a short retention we can provide 2 safety checks while still allowing the value of decommission node to be maintained.

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.