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 Oct 8, 2026

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 and tape drives. However, from an operational perspective, it would be useful to expose how the workload is internally partitioned into recall tasks and how those tasks are assigned to libraries and drives.

In a multi-library configuration, Deep Archive could dynamically distribute independent recall tasks across the available libraries, based on tape location, library workload, drive availability, and expected seek/mount overhead.

The objective would be to maximize aggregate recall throughput while minimizing unnecessary tape mounts and library contention.

A useful enhancement would be to expose this scheduling information through dacli task list, including the library, tape drive, and estimated/actual progress associated with each recall task.

Idea priority Medium