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 Submitted
Created by Guest
Created on Oct 16, 2026

Replicate Retention Set and Retention Rule metadata to the target Storage Protect server during replication.

Currently, IBM Storage Protect replication transfers backup data to the target server, but Retention Set and Retention Rule information is not replicated. In a disaster recovery scenario where the source server is unavailable, administrators may need to restore the source database before retained data can be managed or restored.

This enhancement would replicate Retention Set definitions, Retention Rule definitions, expiration attributes, and related metadata to the target server. This would allow the target server to maintain synchronized retention governance information and provide seamless access to retained data during recovery operations.

A common use case is when retention set data is stored on tapes that are vaulted offsite using WORM or non-WORM media. If the source server is lost, the target server could use the same tape media. However, without replicated retention metadata, additional recovery steps are required. Replicating this information would simplify recovery and improve cyber-resiliency.

Idea priority Low