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 Apr 11, 2025

Ability to rename a snapshot (local or HA)

Use case: currently snapshots are created with automatically generated names that are very random, with a string of numbers that are meaningless to the customer.

Cu will sometimes take individual snapshots via the GUI, as a backup before a major application/db change. Because the name is meaningless, customers cannot search/filter on names when he needs to rollback.

Workaround is applying a name at creation of the snapshot, but this works only in CLI

Idea priority Medium
  • Guest
    Sep 26, 2025

    Hi Philip,

    Most of the time the snapshots are NOT reverted to the initial volume for restore but are converted into a physical copy. We will not be taking snapshots via Volume group but snapshots on an individual disk level in order to have a correct process that allows for a consistent snapshot without database corruption (DB2 ACS functionality)

  • Guest
    Sep 26, 2025

    Hi Philip (and FlashSystem Team),


    We are very strongly name convention driving and as such the volumes we are using are strictly named (e.g. host + purpose of the volume (data, logs, ...) + database name). If we make a snapshot of such a volume, we wish to keep a naming convention that is equally clear. We looking at a list of volumes, we can faster navigate by filtering. That cannot be done with the currently random generated names.

    Do not only keep the fuctionalities of the GUI in mind, but also think CLI. It is way faster the filter to the correct snapshot name when the name is meaningfull.

    Does this explanation makes more sense to you or do you need more?


    KR

  • Admin
    Philip Clark
    Sep 26, 2025

    Can you please provide more detail about the use case for choosing the snapshot name?

    It makes sense to hide the machine generated UUID, since it is meaningless to the customer and is only used by the software. But the GUI already shows the essential information about the snapshot: volumegroup it is associated with and the time it was taken. You can click on the snapshot and restore it directly.



    Thanks,
    FlashSystem Team

    philipclark@ibm.com