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 Jul 2, 2026

Need CSI driver support for use of mirrored volumes in SVC standard stretched cluster

To create a volume with high availability (HA) (HyperSwap or stretched topology) on IBM Storage Virtualize® storage systems, put a colon (:) between the two pools within the pool value. For example:

   pool: demo-pool1:demo-pool2

Important The two pools must be from different sites.

 

We need HA capable volumes, snapshots etc. for use in our customer's OpenShift environment for rapid deployment of new and HA storage devices.

This is implemented by the IBM CSI driver which provides a command interface between Kubernetes environment and our SVC. 

Unfortunately as to be seen above you need two storage pools AND in addition to that two site IDs (each storage pool must be on a different site) to avoid problems.

Problems could be stucked processing of volume deletion or creation of snapshots which are key for our environment. 

We are using a SVC standard cluster with 2 nodes - so there are no site IDs. 

So we need a solution for CSI / Kubernetes / OpenShift deployment in HA and snapshot capabilities for SVC standard stretched clusters. This solution ideally shouldn't be buying new, additional SVC nodes to built an enhanced stretched cluster.

 

Because there are many SVC standard stretched cluster - customers with upcoming OpenShift installations in Germany I'm pretty sure that we can find many customers who can use such an enhancement to the CSI driver.

Idea priority Urgent
  • Guest
    Jul 3, 2026

    To provide some more technical background:

    In systems with "topology:standard", when trying to create a clone from a snapshot (example use case: provisioning a VM in OpenShift, for example from template), we will use the mkvolumegroup command. However the mkvolumegroup command does not support a list of pools as argument, i.e. it is not possible to create a mirrored clone. Thus the command on the storage system would fail with a CMMVC error message ("CMMVC5754E The specified object does not exist").

    However there are some clients with a requirement to have mirrored volume copies on the storage system (regardless of the topology), so in these environments it would be ideal if the CSI driver could work with two vdisk copies similar to enhanced stretched clusters (topology:stretched) or Hyperswap (topology:hyperswap). Usually the two pools used for the Volume Mirroring would be provided by two independent backend storage controllers. It provides redundancy in case one of the backend storage system fails.