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 17, 2026

IBM Storage Virtualize in PBHA+DR deployments

Hello IBM Team,

We would like to submit a Request for Enhancement for IBM Storage Virtualize in PBHA+DR deployments.

In our environment, we have implemented a 3-site replication topology based on  PBHA+DR architecture, where two storage systems form the HA pair and one is in the DR location, as follows:

System 1 - production site and actively serves host I/O.
System 2 - located in a clean-room environment (in synchronous replication distance) and, by design, has no host attachment.
System 3 - disaster recovery location (asynchronous replication distance).
In this topology, the current split-brain handling mechanism can lead to undesirable outcome in certain failure scenarios.

Specifically, if the Active Management System (AMS) role is held by the clean-room system at the moment when communication between the two HA systems is lost, the production system is forced to take the partition volumes offline.
As a result, the production site loses access to data, and the running applications fail, despite the fact that it is the only site actively serving host I/O.
From both operational and business continuity perspective, this behavior is undesired for deployments where one HA member is intentionally hostless and should not take precedence over the production system for I/O continuity decisions.


The current AMS-based model provides a solid and well-structured foundation for high-availability scenarios, particularly in environments where fully automated and uniform failover decisions are appropriate.

However, in our specific deployment model, we believe there would be of significant value to complement this behavior with an optional, customer-selectable policy that allows split-brain authority to be aligned with the operational priorities of the environment.
Such an enhancement would extend the flexibility of the solution for specialized topologies, while fully preserving the existing AMS-based behavior for deployments where it is already the optimal choice.

Examples of possible implementation approaches could include:

Allowing customers to explicitly designate a Preferred Management System to be selected as the split-brain winner.
Allowing customers to define a policy that keeps the system currently serving active host I/O during split-brain conditions.


Implementing this capability would provide the following benefits for our deployment:

Improved continuity of production application services.
More predictable behavior during communication loss scenarios, where a human decision must be taken depending on the sites communications availability.
Better alignment with air-gapped clean-room architectures.
Reduced risk of unnecessary production outages in such a configuration.
We respectfully request that this proposal be considered as a potential product enhancement for future releases of IBM Storage Virtualize.

Kind regards,
Virgil Balan
Storage Administrator
CEC Bank SA
 

Idea priority High
  • Guest
    May 8, 2026

    Thank you for submitting this Idea. Synchronous option for policy-based replication is coming soon, which sounds like it might be a better fit for your requirements.



    Thanks,
    FlashSystem Team

    philipclark@ibm.com

  • Guest
    Apr 17, 2026

    While PBHA provides complex functionality and automation, some environments could still use the "OLD WAY" of Metro mirror/Global mirror combination without the "hyperswap" functionality (with specific user control for the replication).

    Octavian Lascu

    Senior IT Infrastructure Architect