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 Under review
Created by Guest
Created on May 16, 2025

Coordinated snapshot of a single volume

use case: customer uses PBHA but has multiple db's in one volume group (due to limit on number of VG's); CLI would be sufficient (since it's integrated in a script)

Idea priority Urgent
  • Guest
    May 16, 2025

    Some more context for this request; if one wants consistency on a database in a snapshot without the possibility of corruption nor needing to perform a crash recovery...one needs to be able to quiesce the database (DB2 in our use case). It's impossible for an instance owner that manages multiple DB2 DB's to quiesce all of them long enough to be able to snapshot a volume group. Even if it would be possible, we would have to roll back all the databases in that volume group. That's why we have every database on it's own volume and we need to be able to snapshot specific volumes via CLI