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 Not under consideration
Created by Guest
Created on Jan 25, 2016

Protocol replication needs the ability to failover individual filesets for DR testing

Protocol replication has “all-or-nothing” failover/failback process. Cannot test DR for new exports. We need the ability to failover individual filesets for DR testing

With “AFM-based DR” (which the protocols cluster DR is based on), and indeed for all other AFM variants, failover/failback is at the fileset level. With the protocols DR, all filesets and all protocols need to be failed over & failed back as a single entity. This is fine in a genuine DR situation, where you want to failover everything, but does limit one's ability to test one's DR solution. For example, if a new export is created to support a new application/business, the owners will want to do a DR test before going live to ensure they can successfully bring up their application at the DR site. We will not be able to just “DR test” that new application by just failing over their service (i.e. the export associated with their fileset) – we would have to fail everything over, which would impact otherwise healthy services on the same cluster

Idea priority Urgent
  • Guest
    Reply
    |
    Sep 30, 2020

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - IBM Spectrum Scale
    Product - Spectrum Scale (formerly known as GPFS) - Public RFEs
    Component - Product functionality

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - IBM Spectrum Scale
    Product - Spectrum Scale (formerly known as GPFS) - Public RFEs
    Component - V4 Product functionality

  • Guest
    Reply
    |
    Aug 31, 2020

    .Database cleanup of older RFEs not currently in plan.

  • Guest
    Reply
    |
    Jan 26, 2016

    Creating a new RFE based on Community RFE #82929 in product Spectrum Scale (formerly known as GPFS) - Public RFEs.