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 Delivered
Created by Guest
Created on Nov 27, 2018

Spectrum Protect Node Replication - option to block DELETE BACKUP/ARCHIVE from replicating to target server

Add possibility to supress replicating "delete backup"/"delete archive" commands from node replication, possibly depending on setting "DISSIMILARPOLICIES" or "backdelete/archdelete=no for node on target server (possibly new parameter not to confuse established options)
When "delete backup" or "delete archive" commands are issued on the backup client side, as is the results are replicated(i.e., data are dropped) regardless of dissimilarpolicies, and/or backdelete/archdelete=no on target server. This is fine in some cases, but where there is concern about some admin at some point abusing the rights, node replication does not provide any meaningful protection (couple hours depending on replication settings) after which data are irrecoverable.
It is of course possible to disable backdelete/archdelete on source server, then the client won't be able to delete the data, but that's a problem for application backups.
It could potentially significantly improve benefits of node replication if target server could be set to
-Follow archive retention rules when deletion is issued by client to source server
-Inactivate the data and follow policies, but don't outright delete backups when deletion is issued by client to source server

Idea priority Medium