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 Aug 26, 2020

Support for RoW on snapshots

Redirect on Write (RoW) is a less space consuming option for snapshots (at potential expense of more workload required for deletions).

Idea priority Low
  • Guest
    Reply
    |
    Oct 26, 2020

    We recognize that there are relative pros and cons for RoW and CoW under different use cases and scenarios. For the use case intended for Scale, i.e. short-term snapshots for backup purposes, we believe that CoW is generally more appropriate. Among other things, it ensures consistent performance while the snapshot exists because the original data remains in place and subsequent changes are also to the same physical place. With RoW, files can become fragmented or, in the worst case, the current-active block can even be on a slower storage tier than the original block.

  • 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 - Technical Foundation

  • Guest
    Reply
    |
    Sep 25, 2020

    Can you explain in more detail how this differs from the existing implementation of snapshots?