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.

ADD A NEW IDEA

IBM Storage Deep Archive

Provide the Expedited/Standard/Bulk S3 Retrieval option

Deep Archive should provide an expedited retrieval option equivalent to the expedited retrieval semantics available in Amazon S3 Glacier Flexible Retrieval. For applications requiring occasional urgent access to archived content, users should be a...
4 days ago in IBM Storage Deep Archive Submitted

S3 Object Lock / Immutable Retention

Deep Archive should support Amazon S3 Object Lock semantics, including Governance Mode and Compliance Mode, with configurable object retention periods and legal holds. This is particularly relevant for enterprise archive, regulatory retention, ran...
4 days ago in IBM Storage Deep Archive Submitted

Parallel and Multi-Library Recall Scheduling

For large restore operations, Deep Archive should provide more explicit control and visibility over recall scheduling. For example, when retrieving 256 files of 100 MiB each, the documentation describes a recall workload involving multiple tapes a...
4 days ago in IBM Storage Deep Archive Submitted

Expose object MD5 via S3 API and add standard x-amz-checksum-* support (SHA-256, SHA-1, CRC32/CRC32C)

Current situation IBM Storage Deep Archive computes and stores an MD5 for each object at ingest. It recomputes it and compares it with the stored value when the object is restored from tape. This value cannot be read through the S3 API, and it is ...
4 days ago in IBM Storage Deep Archive Submitted

Reference architecture for resilient S3 access and failover across multiple IBM Storage Deep Archive systems

IBM Storage Deep Archive can be deployed with multiple interconnected tape libraries/systems that synchronize data between sites. In such an architecture, an S3 client may potentially connect to more than one system, providing opportunities for ge...
4 days ago in IBM Storage Deep Archive Submitted

-

Expose IBM Storage Scale (GPFS) filesystem on IBM Storage Deep Archive
4 days ago in IBM Storage Deep Archive Submitted

Full Deep Archive administration via GUI

Current GUI is tech-preview only (no task detail, no performance graphs, no user/bucket creation); everything is CLI-only today
about 1 month ago in IBM Storage Deep Archive Planned for future release

Scale GUI on Deep Archive

Expose the Scale GUI on Deep Archive to support monitoring, administration, and troubleshooting.
about 1 month ago in IBM Storage Deep Archive Submitted

Resynchronization mechanism for Multi-Library configurations

When a node fails on Diamondback deep archive in multlibrary configuration writes continue on the surviving node but within the same library (not across libraries as designed), and once the failed node returns, data isn't automatically resynced to...
about 1 month ago in IBM Storage Deep Archive Submitted

Quorum/Tiebreaker architecture flaw

On Multilibrary configuration the default config places 2 quorum nodes in Rack 1 and only 1 in Rack 2 — if Rack 1 goes down, Rack 2 loses quorum and requires manual intervention during DR. No customer-accessible way to fix this (root required).
about 1 month ago in IBM Storage Deep Archive Submitted