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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Under review
Workspace Storage Defender
Created by Guest
Created on May 22, 2024

Data Protect as part of IBM Storage Defender and improvement for cluster-failover

Assume there are two Data Protect Clusters in metro-distance (<30km). Both clusters are loosely coupled only. Just backup data itself are mirrored asynchronously, but no meta-data. 
What are the issues with that?

  • As a consequence, in case of a failover, the "new" backup starts with a full backup. It doesn't consider CBT (Changed Block Table)
    This is not acceptable for a HA scenario. For software upgrades and other tests we switch between the two main DC. For us it is a HA. 
    To do a full backup for 10.000+VMs would create significant load on the VMs athough the written data to the backup cluster will be very little. 
    For clarification: In a real DR scenario this could be accepted. 
  • The backup jobnames in the other DC (after a failover) are different ones. This creates issues for monitoring (backup completed Y/N), for automation and so forth.

Idea: (1) Do a "clever" metadata replication to have a HA solution which respects CBT.  (2) Find an intelligent way to continue with current backup job-names

Idea priority High