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 Sep 22, 2011

Store GPFS metadata blob as in the database, rather than as file data

The GPFS data blob (which contains the file metadata, including the ACL's, storage pool assignment, atime, etc) is currently stored with the data, rather than in the database as metadata. This means that potentially very large amounts of data are backed up when it is not strictly necessary to do so.

We would therefore like the GPFS metadata to be held in the TSM database, rather than as part of the file data. This would allow more accurate "incremental" behaviour.

See also RFE: 13563, regarding the action taken by TSM on various metadata changes.

Idea priority Medium
  • Guest
    Reply
    |
    Jun 12, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Storage
    Product - Tivoli Storage Manager (TSM) Family

    For recording keeping, the previous attributes were:
    Brand - Tivoli
    Product family - Storage
    Product - Tivoli Storage Manager (TSM) Family

  • Guest
    Reply
    |
    Oct 25, 2011

    Thank you for submitting this enhancement request, we do understand the requirement and the rationale behind it but unfortunately we currently do not plan to implement this enhancement request, you might want to consider opening a similar requirement for the GPFS product as we rely heavily on GPFS as to the nature (and quantity) of the data it stores in TSM. I would also like to add that the TSM database is probably not the right holding place for billions of GPFS files' metadata.