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

Granular Restart of Deep Archive Components

Deep Archive currently provides the dacli node start ALL, dacli node stop ALL and dacli node restart ALL commands for restarting the software across the cluster (array of tape libraries). The use of ALL makes the operation inherently cluster-wide.

For operational and maintenance purposes, Deep Archive should additionally provide a granular restart mechanism that allows administrators to restart an individual component without restarting the entire cluster.

The functionality should support, as applicable:

  • a single Deep Archive software component/service;

a single TapeCloud node;

a single TapeCloud node within a specific cluster;

a single Tape Library;

other individually addressable infrastructure components where a restart can be safely performed.

The operation should preserve the existing high-availability behavior and, where supported by the architecture, allow the selected component to be restarted without service interruption or unnecessary impact on the other nodes, TapeCloud instances, or Tape Libraries.

The Web GUI should expose the same granular restart functionality. In particular, administrators should be able to select an individual system/node and initiate its restart from the corresponding management interface.

This capability is important for maintenance, troubleshooting, configuration changes and recovery operations where restarting the entire Deep Archive cluster is unnecessary and introduces avoidable operational impact.

The existing cluster-wide restart functionality (restart ALL) should remain available for cases where a complete cluster restart is required.

Idea priority Medium