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 20, 2015

TSM for Space Management - file expiration

The current release of TSM for Space Management (Unix) has a migfileexpiration option that "Specifies the number of days a copy of a migrated or premigrated file remains in storage after it is modified on your local file system, or deleted from your local file system". Unfortunately, there is only a single global setting for all HSM migrated files. We need to apply different migfileexpiration values for different types of files or different filesystems in a similar way that the retonly parameter can be used for versions of deleted backup files.
For example, we have log files that we want to have a migfileexpiration value of 7, but we also have business critical files that we would like to have a migfileexpiration value of 365.

Idea priority Medium
  • Guest
    Reply
    |
    Dec 14, 2015

    ["You can put the objects which require an increased retention period in a separate file system and run the reconcile on this file system less frequent."]

    Thanks, but I don't believe your suggestion would work in practice.
    Firstly, the files are part of an complex application so we can't simply ['put the objects ... in a separate file system']. The application expects to find certain files in certain directories.
    Secondly, we are dealing with millions of files so finding and moving specific files to separate file systems every day is hardly practical.
    Thirdly, running reconcile ['less frequent'] doesn't solve the underlying problem, because when reconciliation is eventually run it will delete files according to the single, global migfileexpiration setting. Whether you run reconciliation daily, weekly, monthly or yearly you get the same result unless you manually update dsm.sys with a new migfileexpiration setting depending on the file types you are reconciling.

  • Guest
    Reply
    |
    Nov 17, 2015

    IBM has evaluated the request, and has determined that it can not be implemented at this time or does not align with the current multi-year strategy. This request may be resubmitted for consideration after 18 months from the date of submission. The request submitter will automatically be notified by email when the request qualifies for reconsideration and resubmission.

    The migfileexpiration is used from the reconcile process only. An option to prevent unwanted deletions of objects is to prevent running the reconcile on these objects. You can put the objects which require an increased retention period in a separate file system and run the reconcile on this file system less frequent.

  • 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