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 Jul 6, 2026

Improve display and reporting for SAN based backups of IBM Flash arrays

The SAN based backup identifies a disk pool to be protected.  The disk pool consists of several disk volumes (18 in our case).  Currently the UI shows the backup of this in a protection group and all 18 volumes are backed up as a part of the protection group.  This is acceptable when the backup of all volumes is successful.  However, when one or more volumes have a problem and the backup is retried, the pulse logs become complicated and confusing and (worse still) if the backup retry is successful the protection group shows the time that the last attempt took, not the time the entire protection group used.  My idea is to show each volume in the group as a separate backup target "below" the protection group.  The entire group would still be scheduled for backups just as it is today, but when the backup starts each volume would be shown and there would be a separate pulse log for that volume.  Thus, any retries for a failed backup would be contained in the pulse log for that volume.  A failure of any one volume would still necessitate that the entire protection group show as being failed, and only a successful backup of all volumes in the disk pool would result in a successful backup of the protection group.  The time shown for the protection group backup would be the time for all volume backups (success or fail).   I believe this would improve transparency/reporting, improve debugging (when something goes wrong), decrease confusion, and potentially provide opportunity for new/better performance tuning.

Idea priority High